Step-by-step guide to set up Active Directory Domain Services (AD DS) on Windows Server 2025 machine (or any recent Windows Server version)
Setting up Active Directory Domain Services (AD DS) is one of the most essential tasks for any IT administrator who wants to create and manage a centralized network environment. Whether you’re configuring your first domain controller or upgrading your existing infrastructure, understanding each step in the process is key to a stable and secure setup.
In this guide, we’ll walk you through the complete step-by-step process of installing and configuring AD DS on a Windows Server 2025 machine. The same process applies to most recent Windows Server versions, such as 2022 and 2019, with only minor interface or naming differences.
By the end of this tutorial, you’ll have a fully functional domain controller, ready to manage users, computers, and network policies within your organization.
✅ Prerequisites
Before starting:
- Static IP Address – Set a static IP address for the server.
- Correct Time Zone and NTP settings – Time synchronization is important in domain environments.
- Strong Administrator password – This account becomes the Domain Admin.
- Hostname set – Rename the server if needed before promotion (avoid generic names like WIN-XXXXXXX).
- Sufficient resources – 2+ GB RAM, 2+ vCPU, disk space for NTDS.dit.
🛠 Step 1: Install the AD DS Role
Using Server Manager (GUI):
- Open Server Manager → Click “Manage” → “Add Roles and Features”
- Installation Type: Choose Role-based or feature-based installation
- Server Selection: Choose your local server
- Server Roles: Check Active Directory Domain Services
- Confirm dependencies and click Next
- Complete the wizard and click Install
- After install completes, do not close the wizard – click “Promote this server to a domain controller”
OR via PowerShell:
Install-WindowsFeature AD-Domain-Services -IncludeManagementTools
🧭 Step 2: Promote to Domain Controller
Depending on your needs:
A. Create a New Forest (first domain controller in a new domain)
- Deployment Operation: Select “Add a new forest”
- Root domain name: e.g., corp.example.com
- Domain Controller Options:
- Choose Forest functional level and Domain functional level (usually Windows Server 2022 or 2025)
- Ensure DNS Server is checked
- Set Directory Services Restore Mode (DSRM) password
- DNS Options: Ignore the warning about delegation if it’s not needed
- Additional Options: NetBIOS name is generated automatically (can be changed)
- Paths: Accept defaults for database, log files, and SYSVOL
- Review and Install: Review settings → Validate prerequisites → Click Install
The server will reboot automatically after promotion.
🔄 Step 3: Post-Deployment Configuration
After reboot, log in as:
DOMAIN\Administrator
Then:
- Open Active Directory Users and Computers to verify domain setup
- Open DNS Manager to ensure DNS zones were created
- Test domain functionality:
- nltest /dsgetdc:yourdomain.com
- dcdiag /v
🧰 Optional: Configure Organizational Units (OUs), Users, and Groups
Example PowerShell commands:
# Create an OU
New-ADOrganizationalUnit -Name “HR” -Path “DC=corp,DC=example,DC=com”
# Create a new user
New-ADUser -Name “John Doe” -SamAccountName “jdoe” -AccountPassword (Read-Host -AsSecureString “Enter password”) -Enabled $true -Path “OU=HR,DC=corp,DC=example,DC=com”
# Create a new group
New-ADGroup -Name “HR Group” -GroupScope Global -Path “OU=HR,DC=corp,DC=example,DC=com”
🧩 Common Gotchas
| Issue | Fix |
| DNS not working | Ensure AD server is using itself as primary DNS |
| Time sync errors | Configure NTP correctly (especially on Hyper-V or VM) |
| Clients can’t join domain | Verify firewall allows LDAP, DNS, Kerberos |
| Cannot promote due to NetBIOS or duplicate names | Use unique names and check for old records |
Your Ultimate Hub for Technology Guides, Tutorials, and Insight


Pingback: Install and configure Windows Server 2025