Saturday, December 1, 2007


Installing; Windows 2000

Installing Microsoft Windows 2000

To prepare for creating your domain controllers, you must first install Microsoft Windows 2000 onto the computers that will be promoted to be domain controllers. In the Microsoft CRM architecture, the domain controllers are named AD01 and AD02.

Installing Windows 2000 Server for the First Domain Controller

The first step is to install Windows 2000 Server in a workgroup, including the components in the following list:

Prepare the AD01 server

  1. Perform a default installation of Windows 2000 Server by using the CD boot or floppy boot method. Include Terminal Services in remote administration mode. Also install the Support Tools from the Windows 2000 Server CD. Use appropriate naming conventions for your environment; however, for the purposes of this guide, the first domain controller should be named AD01. Enable only an internal facing, or private interface, which will be on the same Ethernet segment as the private interface of your front-end Microsoft Exchange servers.

  2. Apply Windows 2000 Server SP4 (or later version) and any post-service pack updates.

  3. Install Microsoft Internet Explorer version 6.0 (or later).

  4. Change the event log size for the Application, Security, and System event logs to 80000 kilobytes (KB).

Deploy AD01 as the first domain controller

  1. Log on to AD01 using an account that is a member of the local administrators group.

  2. On the Start menu, click Run, type DCPROMO, and then click OK to start the Active Directory® Installation Wizard.

  3. On the Welcome to the Active Directory Installation Wizard page, click Next, select Domain Controller for a New Domain, and then click Next.

  4. On the Create Tree or Child Domain page, select Create a New Domain Tree, and then click Next.

  5. On the Create or Join Forest page, select Create a New Forest of Domain Trees, and then click Next.

  6. On the New Domain Name page, type the full DNS name for the new domain, and then click Next. (For example, in this architecture, the full DNS name is adventureworks.com.)

  7. On the NetBIOS Domain Name page, click Next to accept the network basic input/output system (NetBIOS) domain name.

    Note If you have additional disks in your domain controllers, the recommended configuration is to keep the Active Directory database on a hard disk drive different from the log file.

  8. On the Database and Log Locations page, click Next to accept the default database and log locations.

  9. On the Shared System Volume page, click Next to accept the shared system volume location.

    Note If the following message appears, click OK: "Wizard cannot locate the DNS server that handles the name adventureworks to determine whether it supports dynamic update. Confirm your DNS configuration or install and configure a DNS server on this computer."

  10. On the Configure DNS page, select Yes, install and configure DNS on this computer [recommended], and then click Next.

  11. On the Permissions page, select Permissions compatible only with Windows 2000 servers, and then click Next.

    Note For more information about this option, see the Microsoft Knowledge Base - 257988 at support.microsoft.com/?kbid=257988.

  12. On the Directory Services Restore Mode Administrator Password page, type a strong password (for example, "DS#Restore%1"), and then click Next.

  13. On the Summary page, click Next to accept the settings shown in the summary. This starts the creation of the Windows 2000 domain and installs the DNS server. (Unless you installed DNS components when installing the server, you will be prompted for the location of the files. Insert your installation CD or type the location on your local disk.)

  14. When the process is complete, click Finish, and then select Restart Now to restart the server.

After the server restarts, check the DNS zone for adventureworks.com and ensure that you have four new folders in your zone (msdcs, sites, tcp, and udp). These new folders reflect the proper registration of your new domain controller in DNS. Without these four folders, your domain controller will not function correctly.

Check the DNS zone for your new domain controller

  1. On the Start menu, point to Programs, point to Administrative Tools, and click DNS.

  2. Expand AD01, expand Forward Lookup Zones, and expand adventureworks.com.

  3. Confirm that the folders exist.

If you do not see all four folders, your domain controller is not functioning properly. However, you can fix this problem by forcing the registration of the domain controller in DNS by using the NETDIAG support tool. Go to the command prompt and type NETDIAG /FIX. After this command is complete, you should see all four folders in your DNS zone. You can also force registration by stopping and restarting the Net Logon service. However, the NETDIAG tool provides a great deal of additional useful information.

To validate that your domain controller is working as specified, run DCDIAG from a command prompt. DCDIAG was installed as part of the Windows 2000 Support Tools. The most important test you will see is the first one: connectivity. This test will tell you whether your domain controller is properly registered in DNS. If your tests are successful, you have a healthy domain controller and can go on to the next section.

Setting Active Directory to Native Mode

Active Directory must be in native mode before you can install Microsoft CRM.

Note You must perform this procedure on an Active Directory domain controller.

Set Active Directory to native mode

  1. Log on to AD01 using an account that is a member of the Domain Administrators group.

  2. On the Start menu, point to Programs, point to Administrative Tools, and then click Active Directory Domains and Trusts.

  3. In the console tree, right-click the domain name for the domain that you want to administer, and then click Properties.

  4. On the General tab, if Mixed Mode is displayed, click Change Mode, and then click Yes.

  5. Click OK to close the Properties dialog box, and then click OK on the replication message.

No comments: