question

HomerSibayan-0286 avatar image
0 Votes"
HomerSibayan-0286 asked ·

SYSVOL Not REplicating between Domain Controller

Hi Experts!!

We have 3 Domain Controllers and one of them which is the old DC 2k12 will be subject for decommission. The 2 is DC 2k16 which the new one and currently thr FSMO holder. Now we have some issue with sysvol replication, something that any of created changes from DC 2k16 is not replicating on the sysvol policies of DC 2k12 .

My question now is :

  1. What will be the impact in the production of sysvol not replicated or not syncing in the old DC 2k12 ?

  2. Since we will be decommission the DC2k12 is it okay to ignore the issue with sysvol replication ?

  3. Is there an impact to DC2k12 decommission if we ignore the issue is sysvol ? or we should need to fix the issue to avoid any disruption during DC demotion?

  4. Sysvol Policies is not up to date in DC 2k12 but sysvol in 2 new DC 2k16 is same and up to date. is there any methods of procedure we can follow?




windows-serverwindows-active-directorywindows-server-2019windows-server-2016windows-server-2012
· 2
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,
I am checking to see if the problem has been resolved.
If there's anything you'd like to know, don't hesitate to ask.
Best Regards,

0 Votes 0 ·

Hi,
 
Just checking in to see if the information provided was helpful.
If the reply helped you, please remember to accept it as an answer.
If no, please reply and tell us the current situation in order to provide further help

Best Regards,

0 Votes 0 ·
DSPatrick avatar image
0 Votes"
DSPatrick answered ·

Yes, it must be fixed. If you're using older FRS you can follow along here.
https://support.microsoft.com/en-us/help/290762/using-the-burflags-registry-key-to-reinitialize-file-replication-servi
or for DFSR follow along here.
https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo

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





·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

FanFan-MSFT avatar image
1 Vote"
FanFan-MSFT answered ·

Hi,
For your questions:
As you mentioned above, sysvol not not syncing will cause the group policy issue .And the sysvol sync may caused by the ad replication or other issues.
So before any more changes in the domain, it is suggested to fix the issue firstly.

You can confirm if there are any ad replication problems or DC issues on each DC by command :
Dcdiag /v >c:\dcdiag1.log
Repadmin /showrepl >C:\repl.txt
repadmin /showrepl * /csv (It will report the replication situation for all the DCs)

If there are no issues for the ad replication ,you can try to fix the sysvol sync:
For FRS : you may try to do "D2"on the 2012 DC.(Before this,remember to backup the sysvol folder for the 2016DC and 2012DC.) https://docs.microsoft.com/en-US/troubleshoot/windows-server/networking/use-burflags-to-reinitialize-frs
For DFSR: You can try the non-authoritative synchronization on 2012 DC.((Before this, remember to backup the sysvol folder for the 2016DC and 2012DC.))
https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo

Best Regards,

·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.