Active Directory

How to Install Active Directory on Windows 2000 (for Lamers)

I’m a Lamer! How do I install Active Directory on my Windows 2000 Server?

You can configure your server as a Domain Controller manually (as covered in How to Install Active Directory on W2K), but if you don’t have the time, skill, brains or will to do it manually, it can still be done with just a few mouse clicks.

Dynamic Host Configuration Protocol (DHCP), Domain Name Service (DNS), and DCPROMO (the command-line tool that creates DNS and Active Directory) can be by using the Windows 2000 Configure Your Server Wizard.

Sponsored Content

Maximize Value from Microsoft Defender

In this ebook, you’ll learn why Red Canary’s platform and expertise bring you the highest possible value from your Microsoft Defender for Endpoint investment, deployment, or migration.

Even though it’s all done automatically, you still need the following:

  • A NIC
  • The TCP/IP protocol
  • An NTFS partition with enough free space
  • A network connection (to a hub or to another computer via a crossover cable).
  • An Administrator’s username and password
  • The Windows 2000 Server (or Advanced Server) CD media (or at least the i386 folder)

This article assumes that all of the above requirements are fulfilled. See my Active Directory Installation Requirements page for more info.

Note: This article does NOT assume you have a working brain, or that you can use it correctly. If you think you really want to know how this thing works, please read the How to Install Active Directory on W2K page instead…

To configure your server as a Domain Controller

  1. Press Ctrl-Alt-Del and log on to the server as administrator. Leave the password blank.
  2. When the Windows 2000 Configure Your Server page appears, select This is the only server in my network and click Next.
  3. Click Next to configure the server as a domain controller and set up Active Directory, DHCP, and DNS.

  4. On the What do you want to name your domain page, type dpetri (this is only an example, duh, type in YOUR domain name, not the example…)
  5. In the Domain name box, type com (again, this is only an example). Click on the screen outside of the textbox to see the Preview of the Active Directory domain name. Click Next.

    Note: The combined name appears as in the Preview of Active Directory domain name box. The wizard puts the dot (.) into the name.

    Note: is the Active Directory domain and DNS name, and dpetri is the down-level NetBIOS domain name.

  6. Click Next to run the wizard.

    When prompted, insert the Windows 2000 Server CD-ROM. When the wizard is finished, the machine reboots.

  7. The Configure Your Server Wizard installs DNS and DHCP and configures DNS, DHCP, and Active Directory. The default values set by the wizard are:

            • DHCP Scope:
            • Preferred DNS Server:
            • IP address:
            • Subnet mask:

            That’s it.


            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

            Related Topics:


            Don't have a login but want to join the conversation? Sign up for a Petri Account

            Comments (0)

            Leave a Reply

            External Sharing and Guest User Access in Microsoft 365 and Teams

            This eBook will dive into policy considerations you need to make when creating and managing guest user access to your Teams network, as well as the different layers of guest access and the common challenges that accompany a more complicated Microsoft 365 infrastructure.

            You will learn:

            • Who should be allowed to be invited as a guest?
            • What type of guests should be able to access files in SharePoint and OneDrive?
            • How should guests be offboarded?
            • How should you determine who has access to sensitive information in your environment?

            Sponsored by: