DFS Replication Stuck at Initial Sync

Question

We are having problems getting the SysVol share to replicate to our 2 new DCs. We didn't realize until it was to late, but our already existing domain controller was in error state 5 during the setup of both DCs. I have since cleared the error state, but now it is stuck at initial sync state 2. Neither of the other 2 DCs have a good SysVol folder.

Below is all 3 of our DCs. The red server is the one with the good SysVol folder. The green and blue are waiting for the ability to synchronize with the red server for the first time. I confirmed in event viewer the red server is both of the other servers partner. I am not sure why the red server is waiting on the initial sync, but I have been unable to find a way to reset that to normal so an actual synchronization can take place. Event viewer does not show the red server as having a partner server. Event viewer on both the green and blue servers says they are waiting for the red server to complete its sync before theirs will start.

I have gone through all of the steps in this article: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/troubleshoot-missing-sysvol-and-netlogon-shares

and this article: https://learn.microsoft.com/en-US/troubleshoot/windows-server/group-policy/force-authoritative-non-authoritative-synchronization

Does anyone have any suggestions on getting the state to change from waiting initial sync for the red server?

Answer 1

What operating systems? I'd check the domain controller System and *Replication (DFS or FRS) event logs for errors since last boot. Post the Event Source and Event IDs of any found.

Answer 2

Thank you for your response.

The red server is 2022 Standard 21H2.

The other 2 are 2022 Datacenter Azure Edition 21H2.

After reboot on the red server, I have 1 warning and 2 errors for DFSR.

The warning is 5014. It mentions not being able to replicate with the green server and gave a second error 9033 (The request was cancelled by a shutdown).

The first error is 5002 and that also references the green server.

The second error is 4612 and again, references the green server.

Answer 3

Ok, it may depend on how this happened. Something here could help.

https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/distributed-file-system-replication-not-replicate-files

--please don't forget to upvote and Accept as answer if the reply is helpful--