Home > Articles > Operating Systems, Server > Microsoft Servers

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

Installation of Root Domain

This section covers the promotion of the root domain controllers. By promoting root domain controllers, we are, in fact, creating the forest in which all future high-availability systems will be installed (see Chapter 5 for the discussion of the dual domain [root-and-child] model). The prerequisite to this process is installation of the operating system (Windows Server 2003, Standard Edition) to the domain controller computers on a RAID-1 array. See Chapter 4 for instructions on the configuration of RAID-1 on this server. The servers should be configured for second and third RAID-5 arrays as required.

It is critical this process completes and proceeds as described herein. Deviation from the process or shortcuts may render the root domain useless and it will have to be rebuilt. The updating of the domain controller servers with the required software updates and security patches can take place after promotion, QA, and validation. (See Chapter 5 for the overall architecture this implementation supports.)

Process

Name the Root Domain DCs. Upon completion of the server installations, the root domain controllers will be given miscellaneous names, and they will be a member of the workgroup setup on the support server. Change the names of the root domain controllers to the names provided in your Active Directory Architecture (discussed in Chapter 5). For the corporate hub, the server names we use here are HQRDC01 and HQRDC02 (for later implementation).

It is important to remember to rename the servers to their DC names prior to running DC promo. The names cannot be changed after promotion of these servers to domain controllers, and they have to be destroyed if the names are incorrect. Do not change the workgroup when changing the names.

Configure TCP/IP on HQRDC01. Log on as Administrator to the server designated to become the root DC (HQRDC01). Open the TCP/IP properties of the network interface card (NIC), and enter the parameters listed in Table 6.4.

Table 6.4 TCP/IP Configuration on HQRDC01 Support Server

Resources (RDC01)

Configuration

IP

10.10.20.21

Subnet Mask

255.255.252.0

Default Gateway

10.10.20.1

Preferred DNS

10.10.20.21

Alternate

<null>


Configure TCP/IP on HQRDC02. Log on as Administrator to the server designated to become the root DC (RDC02). Open the TCP/IP properties of the NIC, and enter the parameters listed in Table 6.5.

Table 6.5 TCP/IP Configuration on UVRDC02 Support Server

Resources (HQRDC02)

Configuration

IP

10.10.20.24

Subnet Mask

255.255.252.0

Default Gateway

10.10.20.1

Preferred DNS

10.10.20.24

Alternate

<null>


To install DNS, do as follows:

  1. Log on as Administrator to the server designated to become the root DC (HQRDC01) and install DNS on this server. This is achieved by opening Control Panel, Add or Remove Programs, and Add/Remove Windows Components. This launches the Windows Components Wizard.

  2. Select Networking Services in the wizard and click the Details button. In the Networking Services dialog box, check the option to install Domain Name System (DNS).

  3. Complete the procedures and, when prompted by the installation procedure for the Windows Server operating system CD, provide a CD or browse to the I386 folder under the STDINST share (the source for OS installation files) on the installation or support server.

  4. Complete the process to install DNS on the server. Repeat the process for all hub root domain controllers.

Now you can create the Forest Root Zone on HQRDC01. To create the forest root zone, perform the following steps (note: this process is not repeated on HQRDC02 or any other root server destined to become a DC):

  1. Start DNS and right-click on the HQRDC01 icon.

  2. Select New Zone. The New Zone Wizard launches. Click Next.

  3. Select the option to create a Primary zone and click Next.

  4. Select Forward Lookup zone and click Next.

  5. Enter the domain name (such as MCITY.CTY) as the name of the zone and click Next.

  6. Keep the default DNS file name (it should be MCITY.CTY. dns) for the zone file name and click Next.

  7. If prompted for Dynamic Update configuration, choose the option to allow Dynamic Updates. Click Next.

  8. Complete the process by selecting Finish.

Create the Reverse Lookup Zone on HQRDC01. To create the reverse lookup zone for the forest, perform the following steps:

  1. Open the DNS console and expand the HQRDC01 server icon.

  2. Select Reverse Lookup Zones and click on New Zone. The New Zone Wizard launches.

  3. Select options for a Primary non-integrated zone and click Next.

  4. Enter the IP address range for the zone; this is the 10.10.20.X network.

  5. Click Next and select the options to enable dynamic update.

  6. Complete the process by selecting Finish.

Create the Forest Root Domain Controller on HQRDC01. To create the forest root domain, perform the following steps:

  1. Click Start, Run, and type DCPROMO on HQRDC01.

  2. Choose the options for creating a root domain controller in a new forest.

  3. Choose the root domain name as the full DNS name for the new domain (MCITY.CTY).

  4. Accept the default NetBIOS name for the domain.

  5. Choose the default path for the SYSVOL folder on the RAID-5 array. However, the drive letter should point to the RAID-5 array on (D, E, or F) and not C:\ (for example E:\Windows\...). Choose the path options provided for the NTDS Active Directory database and its log files, changing only the drive letters to point to the RAID 5.

  6. Accept permissions compatible with Windows 2000 and Windows Server 2003.

  7. Enter the Directory Services Restore Mode Administrator password (this should be a complex password, choose something like 4NTDS@mcity), ignoring the quotes. (Remember the server's local Administrator password becomes the password required to log on to the DC after promotion.)

Review the settings, and click Finish to begin the process. Restart the server when prompted.

Enable Active Directory Integration of the Forest Root Zone and the Reverse Lookup Zone. To enable AD integration for the root zone, do as follows:

  1. Open the DNS console and expand the root server HQRDC01 icon.

  2. Expand the Forward Lookup Zones folder and select the MCITY.CTY zone. Right-click this zone and select Properties.

  3. The Properties dialog box for MCITY opens. On the General tab, select the Change button on the Type option. The Change Zone Type dialog box launches.

  4. Select the option to change the zone to Active Directory Integrated and click OK.

Perform the same procedure on the Reverse Lookup Zone folder. Verify HQRDC01 Name Registration. To verify name registration, perform the following actions:

  1. Open the DNS console and expand the root server HQRDC01 icon.

  2. Expand the Forward Lookup Zones folder and select the MCITY.CTY zone.

  3. Verify whether _msdcs, _sites, _tcp, and _udp sub-domains are registered under MCITY.CTY.

  4. If these sub-domains are not registered, then start a command prompt and type NET STOP NETLOGON. Wait for the service to stop and then type NET START NETLOGON.

  5. Repeat steps 1 through 3 to verify the registration.

  6. Verify the Reverse Lookup Zone has replicated.

Verify DNS name resolution on HQRDC02. Before HQRDC02 can be promoted as a root DC, DNS first must be verified. This can be achieved as follows:

  1. Log on to HQRDC02 as the Administrator.

  2. Open the command prompt and type NSLOOKUP MCITY. CTY and press Enter. You should see the following result:

    • C:\>nslookup MCITY.CTY

      Server: HQRDC01.MCITY.CTY

      Address: 10.10.20.21

      Name: MCITY.CTY

      Address: 10.10.20.21

If you do not see this, check to see whether the IP settings on HQRDC02 are correct. It should have HQRDC01 (10.10.20.21) as its preferred DNS server. Do not proceed with DCPROMO of HQRDC02 until DNS is working properly.

Perform DCPROMO on the server HQRDC02. To create the second domain controller, perform the following steps:

  1. Click Start, Run, and type DCPROMO on HQRDC02.

  2. Choose the options for creating an additional domain controller for an existing domain and click Next.

  3. You are prompted for access to the root domain. Choose the Administrator account because this account has Enterprise Administrator credentials. See the previous steps for account and password information.

  4. Choose the default path for the SYSVOL folder on the RAID-5 array. However, the drive letter should point to the RAID-5 array on (D, E, or F) and not C:\. Choose the path options provided for the NTDS Active Directory database and its log files, changing only the drive letters to point to the RAID 5 volume as previously mentioned (see Chapter 4).

  5. Enter the Directory Services Restore Mode Administrator password for this server (this should be a complex password; choose 4NTDS@MCITY). DCs can and should have the same Directory Services Restore Mode Administrator password to simplify administration.

Review the settings and then click Finish to begin the process. Restart the server when prompted. Verify HQRDC02 Name Registration. To verify name registration, perform the following actions:

  1. Open the DNS console and expand the root server HQRDC02 icon.

  2. Expand the Forward Lookup Zones folder and select the MCITY.CTY zone.

  3. Verify whether _msdcs, _sites, _tcp, and _udp sub-domains are registered under MCITY.CTY.

  4. If the sub-domains are not registered, then start a command prompt and type NET STOP NETLOGON. Wait for the service to stop and then type NET START NETLOGON.

  5. Repeat steps 1 through 3 to verify the registration.

Verify the Reverse Lookup Zone has replicated. Update the Preferred DNS Parameters on HQRDC01. Log on to HQRDC01 and open the TCP/IP properties for the NIC. Change the preferred DNS server from 10.10.20.21 to 10.10.20.24.

Create Automated System Recovery (ASR) media for the domain controllers. The creation of the root domain and promotion of the first domain controllers is now complete. System recovery using ASR media now must be performed on the domain controllers. After the ASR disks have been created, you can start the QA discussed in the next section.

  • + 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