This guide walks through a complete active directory installation on Windows Server, from preparing the machine through promoting it to a domain controller and verifying the result. Ravenswood Technology designs and deploys Active Directory environments for organizations of every size, and this walkthrough reflects the same sequence our engineers follow in production deployments. By the end, you’ll have a working domain controller ready to manage users, devices, and policies across your network.
What AD DS Does for Managing Users in Your Organization
Before diving into the installation, it’s worth being clear on what you’re building. Active Directory Domain Services is the backbone of identity management for most Windows-based organizations — it’s the directory that stores every user account, group, device, and permission in one place, and the mechanism that authenticates a person the moment they log in anywhere on the network. Rather than managing credentials and access separately on every machine, AD DS lets administrators create a user account once and control what that person can reach across the entire active directory environment from a single console.
That centralization is what makes the rest of identity management possible: Organizational Units (OUs) to group users and devices logically, Group Policy to enforce password and login rules consistently, and a single active directory database that every domain-joined system trusts. Getting the installation right the first time saves significant rework later — which is exactly what the steps below are designed to help you do. If you’d rather have that design work handled for you, Ravenswood’s Active Directory Domain Services team can architect and deploy this for your organization end to end.
Step 1: Prepare the Windows Server for Installation
Before you open Server Manager, get the underlying machine ready. AD DS is supported on Windows Server 2019, 2022, and 2025, and each requires a reasonable baseline:
- A modern multi-core CPU and at least 2 GB of RAM — 4 GB or more is a safer real-world target for anything beyond a lab environment.
- At least 32 GB of available storage for the operating system, the AD DS database, and log files, with room to grow as your user base does, more if you’re not installing on Server Core.
- A fully fully patched operating system before you begin — installing role updates on top of a stale OS is a common source of avoidable errors.
- Administrative privilege on the server, since every step from role installation through domain promotion requires it.
Two configuration steps matter more than people expect. First, rename the server before promoting it to a domain controller; renaming afterward is possible but disruptive and best avoided once the server is live. Second, assign the server a static IP address rather than relying on DHCP. A domain controller that changes its IP address after clients and DNS records have been configured against it will cause replication and authentication failures that are painful to trace back to their source. If you’re deploying into a virtual environment, confirm the static IP survives host reboots and migrations — a surprisingly common gap in virtualized AD deployments.
Step 2: Install the Active Directory Domain Services (AD DS) Role
With the server prepared, open Server Manager and launch the “Add Roles and Features Wizard” from the dashboard. Select the destination server from your server pool, then choose the “Active Directory Domain Services” role from the role list — the wizard will prompt you to add the required management tools and features automatically; accept those defaults unless you have a specific reason not to.
If DNS Server isn’t already installed in your environment, add that role at the same time — AD DS depends on DNS to function, and installing both together simplifies the rest of the setup. Before clicking “Install,” review the confirmation screen carefully. It’s a small step that catches misconfigured feature selections before they become part of your active directory installation.
Step 3: Promote the Server to a Domain Controller
Once the role installation finishes, Server Manager will show a notification flag prompting you to complete post-deployment configuration — select “Promote this server to a domain controller” to launch the Active Directory Domain Services Configuration Wizard.
Here you’ll make one of the more consequential decisions in the process: whether this server joins an existing forest or creates a new one. For a brand-new active directory environment, you’ll select “Add a new forest” and specify your root domain name. For an organization extending an existing directory, you’ll add the server as an additional domain controller instead.
The wizard will also ask you to set forest and domain functional levels, which determine which Windows Server features are available and which older domain controllers, if any, remain compatible with this active directory domain. As a rule of thumb, choose the highest level your environment can actually support — a lower functional level held over from years-old domain controllers that have since been retired is one of the more common configuration debts we find during an Active Directory Health Check. You’ll also be prompted to set a Directory Services Restore Mode (DSRM) password — store this somewhere secure, since it’s required for disaster recovery scenarios and is easy to forget once the domain is running smoothly.
Step 4: Configure DNS and NetBIOS Settings
Partner with Microsoft experts you can trust
If it’s time to take that first step toward leveling up your organization’s security, get in touch with Ravenswood to start the conversation.
The wizard’s DNS options screen typically presents a delegation warning if it can’t create a delegation for the new DNS zone in a parent zone — this is expected and safe to skip in most new-forest deployments. What matters more is confirming that name resolution is configured correctly and that the DNS options you’ve selected match how your network actually operates.
You’ll also be asked to confirm a NetBIOS domain name — the short, pre-Windows-2000-style name still used by some legacy applications and authentication contexts. Keep it concise and consistent with your intended domain branding; it’s inconvenient to change after the fact, and plenty of internal tools still reference it even in modern environments. Many environments will opt for a NetBIOS name of three characters.
Step 5: Finalize and Review AD Installation Settings
Next, the wizard will ask where to store the SYSVOL folder, the NTDS database, and the associated log files. Unless your organization has a specific policy dictating otherwise — separate storage volumes for performance or backup reasons, for example — the default paths are appropriate for most deployments. If running on an Azure VM, you should use a secondary data drive and never the OS drive. SYSVOL holds Group Policy objects and scripts replicated across all domain controllers; NTDS is the active directory database itself; and the log files track transactional changes for recovery purposes.
Before installation begins, the wizard runs a prerequisites check and presents a full summary of every setting you’ve selected. Review it carefully — this is your last chance to catch a misconfiguration before it’s written to the directory. Once you proceed, the installation completes and the server reboots automatically to finish promoting itself to a domain controller.
Step 6: Verify AD DS Installation and Domain Controller Health
After the reboot, confirm the domain controller is functioning correctly before building anything on top of it. Open “Active Directory Users and Computers” to confirm the directory structure loaded as expected, and check Event Viewer’s Directory Service and DNS Server logs for errors or warnings generated during promotion. It’s also worth confirming that core services — DNS, the Netlogon service, and replication (if you have more than one domain controller) — are running cleanly.
The most reliable verification is a real-world test: create a test user account, join a workstation to the domain, and log in with that account’s credentials. If the login succeeds and a Group Policy you’ve configured applies correctly on that workstation, your active directory installation is functioning end to end, not just installed. If you have the Remote Server Administration Tools (RSAT) installed on an admin workstation, running the Active Directory module for Windows PowerShell against the new domain controller is a quick way to confirm the directory is responding to queries the way downstream applications and scripts will expect.
Step 7: Configure Initial Users, OUs, and Policies
With a healthy domain controller in place, start building the structure that will make ongoing administration manageable. Use Active Directory Users and Computers (ADUC) to create Organizational Units that group users, devices, and administrative accounts logically — by department, location, or function, depending on how your organization operates. Keeping standard user accounts, workstation objects, and privileged admin accounts in separate OUs from the start makes it dramatically easier to apply targeted policy and access control later.
From there, apply Group Policy to enforce baseline security. A reasonable starting set of Group Policy Objects (GPOs) for nearly any environment includes:
- Password complexity and expiration rules, applied at the domain level so every user account inherits them by default.
- Account lockout thresholds, to slow down credential-guessing attempts without locking out legitimate users too aggressively.
- Login restrictions, limiting which workstations sensitive accounts — particularly domain admin accounts — are permitted to log into.
The Group Policy Management Console (GPMC) gives you a clearer view of how policies are linked and inherited across OUs than working through ADUC alone, and it’s worth using from day one rather than retrofitting policy oversight after your OU structure has already grown complex. Regular active directory auditing of who belongs to privileged groups and how GPOs are applied is what keeps this structure trustworthy as the organization — and the number of admins touching it — grows.
Step 8 - Build a second Domain Controller for Redundancy
A single domain controller works fine until the day it doesn’t. If it goes offline, users can’t authenticate, Group Policy stops applying, and anything that depends on directory lookups starts failing. Adding a second domain controller removes that single point of failure, and it’s far easier to do now than during an outage.
Start by preparing the second server the same way you did in Step 1: patched, renamed, and given a static IP address. Point its DNS client settings at your first domain controller so it can find the domain, then join it to the domain. Install the AD DS role as in Step 2, then launch the Configuration Wizard and choose “Add a domain controller to an existing domain” instead of creating a new forest.
During promotion, keep the DNS Server and Global Catalog options selected so the new server can answer queries and authenticate users on its own. Confirm the correct Active Directory site, set a DSRM password (it can differ from the first server’s), and let the wizard replicate from an existing domain controller. The server will reboot when promotion completes.
Before you consider the job done, verify that the two domain controllers are healthy together:
- Run `repadmin /replsummary` to confirm replication between the two servers is succeeding without errors.
- Run `dcdiag` on each server to check DNS, Netlogon, and general directory health.
- Confirm that the SYSVOL share and its Group Policy contents appear on both servers.
Finally, update your DHCP scopes and server DNS settings so clients and member servers list both domain controllers. In a virtual environment, place the two on separate physical hosts. In Azure, use separate availability zones or an availability set so a single host or zone failure can’t take out both.
Building on a Solid Foundation
A correctly executed active directory installation is the foundation everything else in your identity environment is built on — from day-to-day user account management to Group Policy enforcement to the security of your domain admin accounts. Getting the sequence right the first time, from server preparation through DNS configuration to OU design, prevents the kind of structural rework that becomes far more disruptive once an organization has grown into its directory.
If you’re deploying Active Directory for the first time or want a second set of eyes on an existing environment, Ravenswood’s Active Directory Domain Services team can help you design and implement it correctly from the start. And if AD DS is already running in your organization, an Active Directory Health Check is a straightforward way to confirm your existing installation and configuration are as sound as they should be.