How to Replace an Old Domain Controller with Windows Server 2025
Applies to: migrations involving Windows Server 2019, 2022 and 2025.
Side-by-side domain-controller replacement is safer than attempting to preserve the old operating-system instance.
Migration requires a tested rollback and application-owner acceptance. Visit networkmanager.info for managed Windows VPS services.
Prerequisites
- Verify forest health and supported functional levels.
- Prepare new patched domain member.
- Back up AD system state.
- Document FSMO, DNS and site roles.
Procedure
Step 1: Check health
Resolve diagnostics first.
repadmin /replsummary
dcdiag /e /v
netdom query fsmoStep 2: Promote new server
Install AD DS and DNS then use Install-ADDSDomainController.
Step 3: Validate replication
Check SYSVOL, DNS and client discovery.
Step 4: Transfer FSMO roles
Move planned roles to the new controller.
Step 5: Update dependencies
Change DNS client lists, monitoring, backup and time design.
Step 6: Demote old server
Use Uninstall-ADDSDomainController after dependencies are removed.
Verification
Confirm new role owners and healthy replication without the old controller.
Get-ADDomainController -Filter *
netdom query fsmo
repadmin /replsummary
dcdiag /eRollback
Before demotion, transfer roles back and remove the new controller cleanly if acceptance fails. After demotion, use documented recovery rather than reconnecting stale AD data.
Operational notes
Do not reuse the old controller name or address until DNS and replication metadata are clean.
Official references
Explore Netcloud24 Canada.
