Replace an old domain controller by introducing a clean Windows Server 2025 controller, proving replication and client services, then demoting the old controller. This preserves redundancy during the transition and separates operating-system replacement from directory recovery. Do not treat it as a simple hostname or IP swap: Active Directory, DNS, SYSVOL, time service and any cohosted roles all need explicit checks.
This procedure describes adding a writable replica to an existing healthy domain. It does not cover recovering the last domain controller, creating a new forest or forcibly removing an inaccessible controller. Those scenarios have different safety requirements. Microsoft's current guidance favours clean installation and replacement rather than an in-place OS upgrade of an existing domain controller.
Confirm that the directory is ready for Windows Server 2025
Windows Server 2025 requires an existing domain and forest at Windows Server 2016 functional level or later. Verify both levels; the operating-system versions of two visible controllers do not prove the functional levels have been raised. Older environments may require intermediate controller replacement and a separate reviewed level change before a 2025 controller can be added.
Get-ADDomain | Select-Object DNSRoot,DomainMode,PDCEmulator,RIDMaster,InfrastructureMaster
Get-ADForest | Select-Object RootDomain,ForestMode,SchemaMaster,DomainNamingMaster
Get-ADDomainController -Filter * |
Select-Object HostName,Site,IPv4Address,IsGlobalCatalog,OperatingSystem
Confirm SYSVOL uses DFS Replication and that the domain is not carrying an incomplete legacy FRS-to-DFSR migration. Check directory replication, DNS health and recent relevant events. Do not promote a replacement to hide existing replication failures; identify and resolve them first so the new controller receives a trustworthy directory.
repadmin /replsummary
repadmin /showrepl
dcdiag /test:DNS /v
Save the output with timestamps. A clean summary is useful evidence, but review individual failures and the topology rather than assuming a single command proves the entire forest is healthy.
Protect recovery and identify hidden dependencies
Confirm current, recoverable system-state backups and the forest recovery plan. Know the Directory Services Restore Mode credential handling process and who can authorize recovery. A hypervisor snapshot is not a replacement for AD-aware backup and recovery procedures.
Inventory services on the old controller: DNS, DHCP, certificate services, file shares, NPS, application agents, scripts and static client configurations. Demoting AD DS does not migrate those workloads. Certificate authorities and DHCP require separate migration plans; leaving them behind can make a technically successful DC replacement a business outage.
Identify devices, applications and firewall rules that explicitly reference the old controller's name or IP. Include LDAP integrations, DNS client settings, monitoring, backup jobs and scripts. An application that is supposed to discover domain controllers may still contain a hardcoded endpoint.
Build the new controller with its own identity
Install and patch Windows Server 2025 on supported hardware or a supported virtualization platform. Give it a unique name and static IP address, assign the correct AD site through subnet configuration and point its DNS client at existing healthy internal AD DNS servers during introduction. Do not configure a public resolver as an alternate domain DNS server.
Verify domain connectivity, name resolution and time, then join the domain. Use the organization's security baseline and compatible endpoint protection. Make sure remote console access is available independently of RDP so promotion or networking problems can be diagnosed safely.
Install the AD DS role and management tools:
Install-WindowsFeature AD-Domain-Services -IncludeManagementTools
Installing the role does not promote the server. The next step requires appropriately authorized directory credentials and connectivity to the relevant FSMO role holders. The first controller of a newer release can require schema and domain preparation; use the documented permissions and allow replication instead of treating an administrative-rights error as a reason to bypass checks.
Promote as an additional controller
Use Server Manager's promotion workflow or the ADDSDeployment module to add a domain controller to the existing domain. Confirm the domain, site, DNS-server role and Global Catalog choices. Set the DSRM password through the approved secure process and retain it in the authorized vault.
A shortened illustrative PowerShell workflow is:
$cred = Get-Credential
Install-ADDSDomainController -DomainName 'example.internal' `
-Credential $cred -InstallDns -SiteName 'Main-Site'
Replace the domain and site with real validated values. Review the prerequisite check results and prompts; do not add options that suppress checks simply to automate past warnings. Allow the required restart and wait for initial directory and SYSVOL replication to complete.
Prove replication, DNS and SYSVOL on the new server
Run replication diagnostics again and inspect Directory Service, DNS Server and DFS Replication events on the new controller. Confirm the SYSVOL and NETLOGON shares exist and that expected Group Policy content is present. A server visible in Active Directory Users and Computers is not necessarily ready to serve every domain function.
repadmin /showrepl DC2025-01
dcdiag /s:DC2025-01 /test:Advertising /test:SysVolCheck /test:NetLogons
Invoke-Command -ComputerName DC2025-01 { Get-SmbShare -Name SYSVOL,NETLOGON }
Check that AD-integrated DNS zones and service records have replicated. Resolve representative domain and application records through the new DNS service, and verify required forwarders or server-specific DNS settings separately. Some DNS configuration is not simply inherited because the zones are integrated with AD.
Use a controlled client to test domain sign-in, Group Policy processing and application authentication through the normal site topology. Inspect the client's selected controller and DNS configuration. An administrator connecting directly to the new server proves less than a representative client completing its ordinary workflow.
Transfer roles and service dependencies deliberately
If the old controller holds FSMO roles, transfer them while it is healthy. Verify the target controller is suitable and fully replicated. A normal replacement calls for transfer, not seizure. Record role ownership afterward and verify that relevant administrative operations continue to work.
When moving the PDC emulator role in the forest root domain, review the authoritative time-source configuration and monitoring. Time affects Kerberos and many applications; do not assume the new role holder automatically inherits a manually configured external time source from the old machine.
Update DHCP DNS-server options and static clients in controlled stages, keeping at least two appropriate internal resolvers available where the design requires redundancy. Migrate hardcoded LDAP and other dependencies, then observe the old server's activity for evidence of missed clients.
Demote only after acceptance
Keep the old controller available through an agreed observation period. Confirm no essential cohosted role or dependency remains, all relevant replicas are healthy and backups of the new environment succeed. Schedule normal demotion using Server Manager or the supported ADDSDeployment workflow.
Do not delete the computer account or VM as a substitute for graceful demotion. After demotion, verify removal from the domain-controller inventory, Sites and Services and relevant DNS records. Clean up only records that are actually stale, and confirm replication carries the change throughout the domain.
Understand rollback boundaries
Before demoting the old controller, a failed new-server introduction may be reversible through supported demotion of the new controller while the established environment remains healthy. After role transfers or client DNS changes, reverse those dependencies explicitly if needed. After demotion, do not restore an old VM image and reconnect it as though nothing changed.
Raising the domain or forest functional level to 2025 is a separate change with compatibility and rollback implications. It is not required merely because one 2025 controller has joined a domain operating at supported 2016 levels. Defer that decision until every controller and dependent requirement has been reviewed.
Refer to Microsoft's controller replacement guidance and functional-level requirements for the release-specific boundaries.
Related procedures
How to Transfer and Seize Active Directory FSMO Roles Safely; How to Configure DNS Aging and Scavenging; How to Configure DNS Client Settings with PowerShell.
How to Plan an In-Place Upgrade to Windows Server 2025
An in-place upgrade to Windows Server 2025 keeps an existing server installation while replacing its operating system. It can reduce…
How to Migrate a Windows File Server with Storage Migration Service
Storage Migration Service can inventory a Windows file server, copy its files and share configuration, then optionally transfer the…
How to Migrate DHCP Scopes to a New Windows Server
Migrating DHCP scopes safely requires more than importing address ranges. Clients depend on leases, reservations, options, policies, relay…
How to Migrate IIS Websites to a New Windows Server
Migrating an IIS website means moving its application, hosting configuration, dependencies and access paths to a new server. Copying the…