Said It Here

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.

  1. 1
    Performing live migrations or shared-nothing live migrations
  2. 2
    Demoting the old domain controller and standing up an entirely new server
  3. 3
    Using replication features to generate an inactive copy
  4. 4
    Keeping 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

“Getting all kinds of conflicting information from different places about moving Hyper-V guest DCs to new hardware.”source ↗

“Is demote and rebuild the only option?”source ↗

4zc0b42 · r/sysadmin · 1 upvotes

Where this came up

People with this problem also raised