Home > Articles > Software Development & Management

  • Print
  • + Share This
This chapter is from the book

Evaluating Different Design Options

As previously discussed, the Active Directory and the Exchange 2000 design topology may differ depending on the functional design requirements set by the organization. The infrastructure on which the installation resides will also dictate the design decisions.

Before developing the Exchange 2000 design, the functional requirements of the organization need to be determined. More often than not, these requirements directly reflect the organization's business requirements. In general, the functional requirements are the technical specifications outlined to satisfy the stated business objectives.

DNS Implementation

It is important to have a comprehensive DNS and Active Directory implementation in place prior to deploying Exchange 2000. In many cases, organizations need to make decisions regarding how they will integrate existing DNS implementations with Windows 2000 and the Active Directory. Because Windows 2000 and Exchange 2000 are so heavily reliant on DNS, it is important that the organization coordinates at the highest level to ensure that these installations are properly designed and implemented.

The following sections discuss three scenarios: Active Directory-integrated DNS, coexistence, and third-party DNS implementation.

Active Directory-Integrated

Unlike previous versionsof the Windows operating system, which used the proprietary Windows Internet Naming System (WINS), Windows 2000 Active Directory integrates the industry standard domain name system (DNS) into the naming resolution process of the directory system. Windows 2000 uses DNS for name resolution and for locating Domain Controllers and/or other related Active Directory components such as printers or shared resources.

The basic concept behind the role of DNS is to maintain resource records (RR) contained within a database called a zone file. The zone file includes all the DNS information about one or more defined namespaces. This database contains records that map IP addresses to hostnames (A Records), Mail Exchange (MX), and Canonical Names (CNAME). Users query DNS servers to resolve hostnames to IP addressees. In summary, this is the basic principle behind the role of DNS.

If you elect to install Windows 2000 DNS and enable it for Active Directory integration, the following features are provided:

  • Dynamic registration of hostnames and IP addresses to the database.

  • Active Directory-integrated zones. Active Directory-integrated zones operate as multimaster databases and are replicated through the robust Active Directory replication process, removing the need for a separate DNS replication mechanism for zones transfers and allowing updates to be made by all servers.

The Active Directory-integrated strategy is relatively simple and straightforward. You not only reap the benefits and features of traditional DNS implementations, but you also gain the ability of directly integrating it into the Active Directory.

Coexistence

Many organizations that have established DNS implementations prefer to maintain their existing installation rather than replace it with a different solution. In most cases, these organizations are heavily reliant on the current installation and choose not to migrate to a different installation due to the inherent risks associated with that task. However, it is not uncommon for them to have it coexist with Windows 2000 DNS. Following is a short checklist that can be used to qualify all Unix BIND DNS servers when considering this option:

  • The installations must be BIND 8.1.2 or later. This version supports Dynamic DNS and Service Records (SRV).

  • Optionally, if you want to take advantage of the incremental zone transfer feature, upgrade all BIND servers to version 8.2.1 or later.

  • It is recommended that the Windows DNS installation be configured as primary and non-Windows DNS as secondary.

Third-Party DNS Implementation

There are third-party vendors that offer alternatives to the DNS choices just listed. These products can be leveraged to manage the implementation(s) that will be deployed. They can also be used in place of Unix BIND, Windows 2000, or other existing DNS installations. Another option is to use the product to manage the implemented solution.

This option works best when deployed in a complex environment. For example, in an enterprise environment with a multiplatform DNS installation, the capability to centralize the management of all the different installations may be a requirement.

AD Domain Design Model Used

When making decisions regarding which domain model to deploy, there are a number of key elements that need to be considered. The organization business requirements, the business model, and the current environment are key components when deciding which Active Directory domain model to use. The delegation of administrative responsibilities and the enforcement of security policies also play an integral part in the process.

Single Domain Model

When planning the Active Directory domain model, it is generally recommended that you start simple. Begin with the single domain model as shown in Figure 3.1, and from there determine whether the design will satisfy all of the established business and functional requirements.

Figure 3.1 Single domain model.

The single domain model design is the least difficult to implement and manage. To manage users and resources, Organizational Units (OUs) can be created to organize and control the way resources are managed. Group Policies can easily be defined and applied to all users, computers, printers, and other related objects throughout the domain.

There are specific scenarios in which the single domain model would best fit. However, there are limitations with this design model that should be taken into consideration before choosing it. For example, the limitations include that security policies will apply domain-wide and SMTP cannot be used as the transport for site-to-site replication. The single domain model will be discussed within the context of each company design scenario.

Placeholder Root Domain Model

The placeholder root domain model, shown in Figure 3.2, includes the creation of a placeholder root domain that is the root of the tree for the subordinate domains. The objects that would exist in this domain would be the enterprise and schema admin groups. It would also maintain copies of the Global Catalog. Subordinate or child domains would be created to include users, servers, printers, and other related objects. Administrative groups can be created to delegate administration to the child domains.

Additional domains might be necessary depending on the organization's administrative and policy requirements. For example, the design team may want to have a set of users on the network abide by a domain user security policy that is different from the security policy applied to the rest of the organization.

Figure 3.2 Placeholder root domain model.

Peer Root/Peer Resource Domain Model

The peer root/peer resource domain model shown in Figure 3.3 is similar to the previously described placeholder root domain model with the exception that the first established root domain in the forest would not host any subordinate or child domains. Multiple domains can be created at the forest level, resulting in a "peer" root configuration of different trees. Since the domains are contained within the same forest, a two-way transitive trust connects the domains no matter what tree they reside in. Access between the domains is available providing the administrator has been assigned permissions in both domains.

Figure 3.3 Peer root/peer resource domain model.

The peer root domain contains the Schema Operations Master and also holds copies of the Global Catalog. The creation of a peer root domain allows for a higher degree of security and control on the schema. In order to perform forest-wide operations, such as adding domains to the forest or modifying the schema, administrators must authenticate to the root domain. The peer root domain model provides the following services:

  • Reduces the likelihood of accidental or unauthorized schema changes that could destroy the Active Directory forest.

  • Allows for future changes to be made to the forest. Since the first domain in a forest can never be removed, company acquisitions and/or name changes could prove problematic without a peer root domain.

Comparable permission(s) assignments can be made within a single domain to protect the schema but it should be noted that in a single domain model, the impact of reorganization would be much larger.

This design provides the most flexibility within the forest. This design also allows an organization to add future domains or reconfigure the namespace to support business or network needs.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020