Moving a virtual domain controller without a USN rollback
Official guides offer conflicting advice on how to move a virtual machine domain controller to new hardware safely. This leaves administrators stuck guessing whether they have to completely demote and rebuild the DC from scratch.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
- 1Performing live migrations or shared-nothing live migrations
- 2Demoting the old domain controller and standing up an entirely new server
- 3Using replication features to generate an inactive copy
- 4Keeping the new server's native IP address and manually updating network device IP helper configurations.
In their words
Unedited, grouped by where they were said, most upvoted first within each place, each linked to the thread it came from.
r/sysadmin2 people · September 2026
“I'm planning to move our DHCP role from an old [Windows Server 20XX] server to a new Windows Server 2025 server (member server, not a DC) and would appreciate a sanity check before the maintenance window.”source ↗
maxcoder88 · r/sysadmin · 8 upvotes
Where this came up
People with this problem also raised
- 2How to move a website from a subdomain to the main domain
- 7How to migrate company email from Google Workspace to Microsoft 365
- 2What to do when your cloud service suddenly shuts down
- 2Why did DNS break after promoting a domain controller?
- 4How to migrate remote management platforms without rebuilding everything
- 2Why do DNS changes take up to 48 hours to propagate?