SYSVOL Not REplicating between Domain Controller

Homer Sibayan 361 Reputation points
2021-03-16T09:33:08.357+00:00

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 Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,593 questions
Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,429 questions
Windows Server 2012
Windows Server 2012
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
1,565 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,575 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
6,205 questions
{count} vote

3 answers

Sort by: Most helpful
  1. Fan Fan 15,321 Reputation points Microsoft Vendor
    2021-03-17T00:18:59.083+00:00

    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://learn.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,

    1 person found this answer helpful.
    0 comments No comments

  2. Anonymous
    2021-03-16T12:53:50.18+00:00

    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--

    0 comments No comments

  3. Falcon IT Services 226 Reputation points
    2021-07-04T00:29:19.23+00:00

    Hello,

    Since you are getting rid of the 2K12 you can always orphan it but if you or others else have created any policies on it they will be lost. Better to get replication working then gracefully remove it from the domain as mentioned previously by FafFan and DSPatrick.

    regards,

    Miguel
    https://www.falconitservices.com

    0 comments No comments