How to Install Active Directory on Windows 2000

by Daniel Petri - January 8, 2009

How do I install Active Directory on my Windows 2000 Server?

First make sure you read and understand Active Directory Installation Requirements. If you don't comply with all the requirements of that article you will not be able to set up your AD (for example: you don't have a NIC or you're using a computer that's not connected to a LAN).

Note: This article is only good for understanding how to install the FIRST DC in a NEW AD Domain, in a NEW TREE, in a NEW FOREST. Meaning - don't do it for any other scenario, such as a new replica DC in an existing domain (How to Install a Replica DC in an Existing AD Domain on Windows 2000).

Here is a quick list of what you must have:

  • An NTFS partition with enough free space
  • An Administrator's username and password
  • The correct operating system version
  • A NIC
  • Properly configured TCP/IP (IP address, subnet mask and - optional - default gateway)
  • A network connection (to a hub or to another computer via a crossover cable)
  • An operational DNS server (which can be installed on the DC itself)
  • A Domain name that you want to use
  • The Windows 2000 CD media (or at least the i386 folder)
  • Brains (recommended, not required...)

This article assumes that all of the above requirements are fulfilled.

Step 1: Configure the computer's suffix

(Not mandatory, can be done via the Dcpromo process).

  1. Right click My Computer and choose Properties.
  2. Click the Network Identification tab, then Properties.

  1. Set the computer's NetBIOS name. On a W2K server this cannot be changed after the computer has been promoted to Domain Controller.
  2. Click More.

  1. In the Primary DNS suffix of this computer box enter the would-be domain name. We will use dpetri.net for this example, you should use your own domain name. Make sure you got it right. No spelling mistakes, no "oh, I thought I did it right..." because on W2K this cannot be changed after the computer has been promoted to Domain Controller and if you got it wrong the Dcpromo process might fail.

  1. Click Ok.
  2. You'll get a warning window.

  1. Click Ok.
  2. Check your settings. See if they're correct.

  1. Click Ok.
  2. You'll get a warning window.

  1. Click Ok to restart.

Step 2: Configuring the computer's TCP/IP settings

You must configure the would-be Domain Controller to use it's own IP address as the address of the DNS server, so it will point to itself when registering SRV records and when querying the DNS database.

Configure TCP/IP

  1. Click Start, point to Settings and then click Control Panel.
  2. Double-click Network and Dial-up Connections.
  3. Right-click Local Area Connection, and then click Properties.

  1. Click Internet Protocol (TCP/IP), and then click Properties.

  1. Assign this server a static IP address, subnet mask, and gateway address. Enter the server's IP address in the Preferred DNS server box.

  1. Click Advanced.
  2. Click the DNS Tab.
  3. Select "Append primary and connection specific DNS suffixes"
  4. Check "Append parent suffixes of the primary DNS suffix"
  5. Check "Register this connection's addresses in DNS". If this Windows 2000-based DNS server is on an intranet, it should only point to its own IP address for DNS; do not enter IP addresses for other DNS servers here. If this server needs to resolve names on the Internet, it should have a forwarder configured.

  1. Click OK to close the Advanced TCP/IP Settings properties.
  2. Click OK to accept the changes to your TCP/IP configuration.
  3. Click OK to close the Local Area Connections properties.

Step 3: Install and configure the DNS Service

Now you need to install Microsoft DNS Service:

Step 4: Running DCPROMO

After completing all the previous steps (remember you didn't have to do them) and after double checking your requirements you should now run Dcpromo.exe from the Run command.

  1. Click Start, point to Run and type "dcpromo".
  1. The wizard windows will appear. Click Next.

  1. Choose Domain Controller for a new domain and click Next.

  1. Choose Create a new domain tree and click Next.

  1. Choose Create a new forest of domain trees and click Next.

  1. Enter the full DNS name of the new domain, for example - dpetri.net - this must be the same as the DNS zone you've created in step 3, and the same as the computer name suffix you've created in step 1. Click Next.

This step might take some time because the computer is searching for the DNS server and checking to see if any naming conflicts exist.

  1. Accept the the down-level NetBIOS domain name, in this case it's DPETRI. Click Next

  1. Accept the Database and Log file location dialog box (unless you want to change them of course). The location of the files is by default %systemroot%\NTDS, and you should not change it unless you have performance issues in mind. Click Next.

  1. Accept the Sysvol folder location dialog box (unless you want to change it of course). The location of the files is by default %systemroot%\SYSVOL, and you should not change it unless you have performance issues in mind. This folder must be on an NTFS v5.0 partition. This folder will hold all the GPO and scripts you'll create, and will be replicated to all other Domain Controllers. Click Next.

  1. If your DNS server, zone and/or computer name suffix were not configured correctly you will get the following warning:

This means the Dcpromo wizard could not contact the DNS server, or it did contact it but could not find a zone with the name of the future domain. You should check your settings. Go back to steps 1, 2 and 3. Click Ok.

  1. You do have an option to let Dcpromo do the configuration for you. If you want, Dcpromo can install the DNS service, create the appropriate zone, configure it to accept dynamic updates, and configure the TCP/IP settings for the DNS server IP address. Click Next.

Accept the default choice or, if you want, quit Dcpromo and check steps 1-3.

  1. Accept the Pre-Windows 2000 compatible permissions.

  1. Enter the Restore Mode administrator's password. You can leave it blank (in Windows Server 2003 you must enter a password) but whatever you do - remember it! Without it you'll have a hard time restoring the AD if you ever need to do so. Click Next.

  1. Review your settings and if you like what you see - Click Next.

  1. See the wizard going through the various stages of installing AD. Whatever you do - NEVER click Cancel!!! You'll wreck your computer if you do. If you see you made a mistake and want to undo it, you'd better let the wizard finish and then run it again to undo the AD.

  1. If all went well you'll see the final confirmation window. Click Finish.

  1. You must reboot in order for the AD to function properly. Click Restart now.

Step 5: Checking the AD installation

You should now check to see if the AD installation went well.

  1. First, see that the Administrative Tools folder has all the AD management tools installed.

  1. Run Active Directory Users and Computers (or type "dsa.msc" from the Run command). See that all OUs and Containers are there.

  1. Run Active Directory Sites and Services. See that you have a site named Default-First-Site-Name, and that in it your server is listed.

  1. Open the DNS console. See that you have a zone with the same name as your AD domain (the one you've just created, remember? Duh...). See that within it you have the 4 SRV record folders. They must exist.

= Good

If they don't (like in the following screenshot), your AD functions will be broken (a good sign of that is the long time it took you to log on. The "Preparing Network Connections" windows will sit on the screen for many moments, and even when you do log on many AD operations will give you errors when trying to perform them).

= Bad

This might happen if you did not manually configure your DNS server and let the DCPROMO process do it for you.

Another reason for the lack of SRV records (and of all other records for that matter) is the fact that you DID configure the DNS server manually, but you made a mistake, either with the computer suffix name or with the IP address of the DNS server (see steps 1 through 3).

To try and fix the problems first see if the zone is configured to accept dynamic updates.

  1. In DNS Manager, expand the DNS Server object.
  2. Expand the Forward Lookup Zones folder.
  3. Right-click the zone you created, and then click Properties.
  4. On the General tab, click to select the Allow Dynamic Update check box, and then click OK to accept the change.

  1. Do the same for the Reverse Lookup Zone.

You should now restart the NETLOGON service to force the SRV registration.

From the command prompt type "net stop netlogon", and after it finishes, type "net start netlogon".

Let it finish, go back to the DNS console, click your zone and refresh it (F5). If all is ok you'll now see the 4 SRV record folders.

If the 4 SRV records are still not present double check the spelling of the zone in the DNS server. It should be exactly the same as the AD Domain name. Also check the computer's suffix (see step 1). You won't be able to change the computer's suffix after the AD is installed, but if you have a spelling mistake you'd be better off by removing the AD now, before you have any users, groups and other objects in place, and then after repairing the mistake - re-running DCPROMO.

  1. Check the NTDS folder for the presence of the required files.

  1. Check the SYSVOL folder for the presence of the required subfolders.

  1. Check to see if you have the SYSVOL and NETLOGON shares, and their location.

If all of the above is ok, I think it's safe to say that your AD is properly installed.

If not, read Troubleshooting Dcpromo Errors and re-read steps 1-4 in this article.

Links

Windows 2000 Deployment Planning Guide

Download the Deployment Planning Guide (Complete, 3.91mb)

Troubleshooting Common Active Directory Setup Issues in Windows 2000 - 260371

Setting Up the Domain Name System for Active Directory - 237675

Information About Configuring Windows 2000 for Domains with Single-Label DNS Names - 300684



Join The Petri Insider - Weekly IT Tutorial and Tips, Whitepaper and Webinars