Hi,
Welcome to share your current situation if there are any updates.
Please feel free to let us know if you need further assistance.
Best Regards,
Vicky
domain SYSVOL folder replication issue
Hi
We have 3 DC as below details:
- Microsoft windows server2012 standard as root domain controller (DC01)
- Server 2012 R2 secondary domain controller (DC02)
- Server 2012 R2 secondary domain controller (DC03)
we found that gpupdate command is giving error and some gpo are not replicating to DC02 and DC03 from DC01.
Kindly assist us to fix this issue.
Windows for business | Windows Server | User experience | Other
Windows for business | Windows Client for IT Pros | User experience | Other
7 answers
Sort by: Most helpful
-
Vicky Wang 2,741 Reputation points
2021-06-15T08:26:35.517+00:00 -
Vicky Wang 2,741 Reputation points
2021-06-11T09:22:46.163+00:00 Hi,
Just checking in to see if the information provided was helpful.
Please let us know if you would like further assistance.
Best Regards,
Vicky -
Vicky Wang 2,741 Reputation points
2021-06-08T09:37:13.7+00:00 Hi,
Repadmin.exe examines AD replication status instead of file replication status, and file replication service is used for replicating SYSVOL on Domain Controllers and Distributed File System (DFS) shared folders.
I suggest you refer to this troubleshooting link below to troubleshoot event 13568:
Troubleshooting File Replication Service
http://technet.microsoft.com/en-us/library/bb727056.aspx#EBAA
If the issue still persists after you have gone through all troubleshooting steps, you can perform a non-authoritative store on the problematic Domain Controller to fix the issue:
How to force an authoritative and non-authoritative synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS)
http://support.microsoft.com/kb/2218556
How to rebuild the SYSVOL tree and its content in a domain
http://support.microsoft.com/kb/315457
Best Regards,
Vicky -
Mohammed Nadeem 161 Reputation points
2021-06-08T05:23:40.433+00:00 Hi
Do I have to stop FRS service on all DCs or only for DC01.
-
Anonymous
2021-06-07T11:45:12.827+00:00 Looks like the Fortinet is badly broken so you may need to deal with that error. As to FRS you could try a nonauthoritative restore
https://support.microsoft.com/en-us/help/290762/using-the-burflags-registry-key-to-reinitialize-file-replication-servi--please don't forget to
upvoteandAccept as answerif the reply is helpful--