How to Set Up a Domain Controller on Windows Server 2025
To set up a Windows Server 2025 domain controller, give the server a static IP and a permanent name, install the Active Directory Domain Services (AD DS) role, then promote it with the configuration wizard or Install-ADDSForest. The promotion creates your domain, installs DNS and restarts the server as the first domain controller.
Key takeaways
- Set a static IP address and final computer name before installing AD DS.
- Install the role with Server Manager or
Install-WindowsFeature AD-Domain-Services -IncludeManagementTools. - Promote with
Install-ADDSForestfor a new forest; DNS is installed by default. - Windows Server 2025 adds a new functional level and an optional 32k database page size.
- New forests need at least the Windows Server 2016 functional level, and users need CALs.
In this guide
- What do you need before promoting a domain controller?
- How to prepare Windows Server 2025 for AD DS
- How to install Active Directory on Windows Server 2025
- How to promote the server to a domain controller
- Set up a Windows Server 2025 domain controller with PowerShell
- What to check after promotion
- Frequently asked questions
- The bottom line
- Useful links
What do you need before promoting a domain controller?
You need a licensed, fully updated Windows Server 2025 installation, a static IP address, a final computer name, a planned domain name, local administrator rights and a Directory Services Restore Mode (DSRM) password. For a production network, plan for at least two domain controllers so sign-in keeps working if one fails.
| Item | Recommendation | Why it matters |
|---|---|---|
| Edition | Standard or Datacenter | Both include AD DS; Datacenter mainly adds unlimited VM rights |
| Hardware | 64-bit CPU, 32 GB+ disk, 2 GB RAM minimum (4 GB recommended with Desktop Experience) | Below Microsoft’s minimums setup can fail; DCs benefit from SSD storage |
| IP address | Static IPv4 | Clients find the DC through DNS records pointing to this address |
| Computer name | Final name, e.g. DC01 |
Renaming a DC later is possible but fiddly |
| Domain name | Subdomain of a domain you own, e.g. corp.example.co.uk |
Avoids DNS conflicts with public names |
| NetBIOS name | 15 characters or fewer, e.g. CORP |
Used in CORP\username sign-ins |
| DSRM password | Strong and stored securely | Needed for directory recovery |
| Licences | Server core licences plus CALs | Every user or device accessing the domain needs a CAL |
If you have not installed the operating system yet, follow our Windows Server 2025 Standard install and activation guide first. Unsure which edition you need? Our Standard vs Datacenter comparison covers it.
Choosing a domain name
Microsoft’s long-standing advice is to register a public domain and use a subdomain such as corp.example.co.uk or ad.example.com internally. Avoid single-label names like CORP and made-up suffixes like .local, which cause trouble with certificates, Macs and cloud services later. Changing a domain name after deployment is a major project, so decide carefully.
How to prepare Windows Server 2025 for AD DS
Before installing the role, patch the server, set a static IP address with DNS pointing to itself (or to 127.0.0.1 after promotion), rename it, set the correct time zone and restart. These four changes prevent most failed promotions and the DNS errors that appear on new domains.
- Install all updates through
Settings > Windows Updateand restart. - Open Server Manager > Local Server, click the Ethernet entry, open the adapter’s Internet Protocol Version 4 properties and set a static IP, subnet mask and gateway.
- Set the preferred DNS server to the server’s own IP address. Leave external DNS servers out; you will add forwarders later.
- Rename the server: run
Rename-Computer -NewName DC01 -Restartin PowerShell, or use Computer name in Local Server. - Confirm the time zone and clock are correct, because Kerberos authentication depends on accurate time.
A common issue we see is a server that still has its router listed as DNS. Promotion succeeds, but workstations then fail to join the domain because they cannot find the DC’s service records.

How to install Active Directory on Windows Server 2025
To install Active Directory on Windows Server 2025, open Server Manager, choose Manage > Add Roles and Features, select Active Directory Domain Services, accept the extra management tools and click Install. No restart is needed at this stage; the server only becomes a domain controller once you promote it.
- In Server Manager, select Manage > Add Roles and Features.
- Choose Role-based or feature-based installation and select your server from the pool.
- Tick Active Directory Domain Services and select Add Features when prompted for the management tools.
- Click Next through the Features and AD DS pages, then select Install.
- When installation finishes, do not close the wizard; select Promote this server to a domain controller.
The PowerShell equivalent, from Microsoft’s AD DS installation guide, is:
Install-WindowsFeature -Name AD-Domain-Services -IncludeManagementTools
How to promote the server to a domain controller
Promotion is done in the Active Directory Domain Services Configuration Wizard. For a brand-new network, choose Add a new forest, enter the root domain name, pick the functional level, keep DNS server and Global Catalog ticked, set the DSRM password and let the prerequisite check run before you install.
- Select Promote this server to a domain controller from the Server Manager notification flag.
- On Deployment Configuration, choose Add a new forest and type the root domain name, for example
corp.example.co.uk. - On Domain Controller Options, choose the forest and domain functional levels. Pick Windows Server 2025 only if every DC will run Server 2025; otherwise choose Windows Server 2016.
- Keep Domain Name System (DNS) server and Global Catalog (GC) selected, then enter and confirm the DSRM password.
- Ignore the DNS delegation warning if this is a private internal zone, and confirm the NetBIOS name.
- Accept the default paths for the database, logs and SYSVOL unless you have a reason to change them.
- Review the options, let Prerequisites Check finish, then select Install. The server restarts automatically.
Which functional level should you pick?
Windows Server 2025 introduces a new forest and domain functional level, the first since 2016. It is required for the optional 32k database page feature, but only Windows Server 2025 DCs can run at that level. Microsoft’s functional levels reference confirms Server 2019 and 2022 DCs stay on the 2016 level, and new forests must be at 2016 or later.
Adding a DC to an existing domain
If a domain already exists, choose Add a domain controller to an existing domain and supply Domain Admin credentials. The existing domain must already run at the Windows Server 2016 functional level or higher before a Server 2025 DC can join it. Our guide to upgrading from Windows Server 2022 to 2025 covers mixed environments.
Set up a Windows Server 2025 domain controller with PowerShell
PowerShell does the whole job in two commands: install the role, then run Install-ADDSForest with your domain name. It prompts for the DSRM password and installs DNS by default. Running the matching test cmdlet first checks prerequisites without changing anything.
| Task | Command |
|---|---|
| Install AD DS role and tools | Install-WindowsFeature -Name AD-Domain-Services -IncludeManagementTools |
| Check prerequisites for a new forest | Test-ADDSForestInstallation -DomainName "corp.example.co.uk" |
| Create a new forest (2016 level) | Install-ADDSForest -DomainName "corp.example.co.uk" -DomainNetbiosName "CORP" -ForestMode WinThreshold -DomainMode WinThreshold |
| Create a new forest (2025 level) | Install-ADDSForest -DomainName "corp.example.co.uk" -ForestMode Win2025 -DomainMode Win2025 |
| Add a DC to an existing domain | Install-ADDSDomainController -DomainName "corp.example.co.uk" -Credential (Get-Credential) |
| List deployment cmdlets | Get-Command -Module ADDSDeployment |
Leave out -SafeModeAdministratorPassword so PowerShell prompts you securely. Never put the DSRM password in plain text in a script.
Licensing the server and your users
A domain controller needs a licensed server and a CAL for each user or device that signs in. Windows Server 2025 Standard covers most small and mid-sized domains, and Windows Server 2025 User CALs cover staff who use several devices. Our Server 2025 licensing guide explains core counts.
What to check after promotion
After the restart, sign in as DOMAIN\Administrator and confirm AD DS and DNS are healthy. Run dcdiag, check that the DNS zone and SRV records exist, add DNS forwarders for internet lookups, and set the DC’s preferred DNS to itself. Then create organisational units, users and groups.
- Run
dcdiag /vin an elevated prompt and fix any failed tests. - Open DNS Manager and confirm the forward lookup zone and the
_msdcszone exist. - Add forwarders (for example your ISP’s or a public resolver) under the server’s DNS properties.
- Create OUs and accounts in Active Directory Users and Computers (
dsa.msc). - Join a test workstation: on Windows 11 Pro go to
Settings > System > About > Domain or workgroup. - Promote a second DC and back up the system state.
Security defaults in Server 2025
New Server 2025 deployments require LDAP signing by default and only allow operations on confidential attributes over encrypted connections, according to Microsoft’s What’s new in Windows Server 2025. Older printers, scanners or apps that use simple LDAP binds may need updating or reconfiguring.
Remember that Windows 11 Home cannot join a domain. Client PCs need Pro or higher, and a Home to Pro upgrade is the usual fix for small offices.
Frequently asked questions
How many domain controllers do I need?
At least two for any production domain. With one DC, a hardware fault or failed update stops users signing in and can lose your directory if backups fail. A second DC replicates AD and DNS automatically. Very small labs or test networks can run on one, but keep regular system-state backups.
Can Windows Server 2025 Standard be a domain controller?
Yes. Both Standard and Datacenter include the Active Directory Domain Services role with no feature difference for domain controllers. Datacenter mainly adds unlimited Windows Server virtual machines on a licensed host. Most organisations run DCs as virtual machines on Standard or Datacenter hosts.
Do I need CALs for a domain controller?
Yes. Each user or device that authenticates to a Windows Server domain needs a Windows Server Client Access Licence, in addition to the server’s core licences. Choose User CALs when people use several devices, or Device CALs when several people share one PC. RDS needs separate RDS CALs.
Can I install Active Directory on Server Core?
Yes, and Microsoft encourages it for domain controllers because Server Core has a smaller attack surface and needs fewer updates. Use the same PowerShell commands, Install-WindowsFeature and Install-ADDSForest, then manage AD remotely with RSAT tools or Windows Admin Center from another machine.
Should I use the Windows Server 2025 functional level?
Only if every domain controller in the forest runs Windows Server 2025. The new level enables the optional 32k database page feature, but it blocks older DCs from joining. In mixed environments with Server 2019 or 2022 DCs, stay at the Windows Server 2016 level and raise it later.
What is the DSRM password used for?
The Directory Services Restore Mode password lets you sign in to a domain controller in a special recovery mode when Active Directory is offline. You need it for authoritative restores and some repairs. Store it in a password manager or vault, because anyone with it could take control of that DC.
The bottom line
A Windows Server 2025 domain controller takes under an hour once the groundwork is right: static IP, final name, sensible domain name, then install and promote. Get DNS correct, add a second DC, and see our Windows Server 2025 features guide for what else the release brings.
Useful links
| Resource | Why it helps |
|---|---|
| Windows Server 2025 install guide | Install and activate the OS first |
| Standard vs Datacenter | Pick the right edition for your DCs |
| Server 2025 licensing explained | Cores, CALs and RDS CALs |
| Upgrade from Server 2022 | Planning mixed-version domains |
| Upgrade Windows 11 Home to Pro | Client PCs must be Pro to join a domain |
| Windows Server 2025 Standard | Licence for your domain controller |
| Windows Server 2025 User CAL | Access licences for domain users |
| Install AD DS (Microsoft Learn) | Official cmdlet reference and options |
| AD functional levels (Microsoft Learn) | Which DCs run at each level |