Forum Discussion
Server 2019 to 2019 DC migration, sysvol dfsr stuck in initial sync
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)
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
- I've got the files, but should I obfuscate the server names? they're generic enough that I don't feel a need to, but I'm not sure what best practice here is. I plan on obfuscating the mac addresses though.
Honestly I wouldn't worry about any of it. It's all on a private network that no one knows how to get to.
- In that case, here's the link
https://1drv.ms/u/s!ApG0VT0-goMMkxrsByHqjSmfxelK?e=e2uw1j
as I was reading through the logs, I noticed that a DC that no longer exists, stoneridgedc.stoneridge.local is referenced.
DC1 etc are for the temp server, DC2 etc are for the new DC server