Forum Discussion
Server 2019 to 2019 DC migration, sysvol dfsr stuck in initial sync
I'm trying to migrate a domain controller from one Server 2019 system to another.
It's been promoted as a domain controller, but the DFSR replication of sysvol is stuck in state 2 (Initial Sync).
This is a single server environment and the current DC is a temporary machine that was being used while the main server was being repaired. the main server (that I'm trying to migrate to) is a clean install of windows server 2019, fully up to date.
DNS is active on both DCs still, and both read as online, but when I run DCdiag, I get this message about the original server:
SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
I have not yet transferred FSMO roles to the new DC, but when I transferred to the temporary server a month ago, sysvol replication was almost instant.
I have no idea why this is stuck.
The event logs could not be read so its a little difficult to follow but looks like STONESERVER has tombstoned. I'd check the system and DFS Replication event logs on both to confirm this. If this is the case then STONESERVER will need to be rebuilt from scratch. Roles are already on SRTTEMP so all that's needed is to perform some cleanup to remove the STONESERVER remnants from active directory.
https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/ad-ds-metadata-cleanup
Once the cleanup is done run the above again (plus check the system and DFS Replication event logs are clean) to verify domain health is 100% before trying to add the domain controller again. (put up a new set of files up and I'll be happy to look)
12 Replies
Please run;
Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log
repadmin /showrepl >C:\repl.txt
ipconfig /all > C:\dc1.txtipconfig /all > C:\dc2.txt
then put `unzipped` text files up on OneDrive and share a link.- it'll be a few hours before I'm in front of the server again, I can upload those files later today.
I checked one last thing before I left, but before I posted this. It seems that the temporary server DC has sysvol replication in an error state (5), though its functioning normally as a domain controller. I've since looked around for a guide on how to fix this, but can't find anything.
it'll be a few hours before I'm in front of the server again, I can upload those files later today.Ok, sounds good
