none
SYSVOL Folder not replicate between two domain controller

    Question

  • Hii

          I have two DC running windows server 2008 r2, in DC1 SYSVOL folder is not updating, the folder is empty and getting error of group policy replication event id 1058 in DC2. I did repadmin /syncall in DC1 but no success. Any other way to solve this error. 

    Thank You. 

    Monday, February 01, 2016 11:37 AM

Answers

  • Hi,

    Regarding the FRS issue - even 13508 without trailing 13509, please refer to the following steps to narrow down the issue:

    1. You could follow the below KB to verify that Sysvol is valid in the registry and the file system. Go through and verify that the registry items, file objects, permissions, junction points, etc are all correct on the DC, if they are not then fix them

    315457 How to rebuild the SYSVOL tree and its content in a domain

    http://support.microsoft.com/kb/315457/EN-US

    2. Please try to increase the severity and number of debug logs for FRS to get more information if needed

    221111 Description of FRS entries in the registry

    http://support.microsoft.com/kb/221111/EN-US

    3. Make sure there are no missing subscriber objects for the DC in AD

    312862 Recovering missing FRS objects and FRS attributes in Active Directory

    http://support.microsoft.com/kb/312862/EN-US

    4. Disable or preferably remove AV software to eliminate it from being the culprit, at least make sure sysvol is not being scanned.

    5. Collect simultaneous network traces from the problem DC and its partner that it cannot communicate with while restarting the service on the problem DC and waiting for the 13508 to see if they are getting blocked on the network.

    Hope the above troubleshooting steps are helpful to you.

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by Shil Patel Thursday, February 11, 2016 6:47 AM
    Monday, February 08, 2016 4:10 AM
    Moderator

All replies

  • > SYSVOL folder is not updating, the folder is empty and getting error of
     
    Check FRS/DFSR eventlogs and fix your journal wrap error :)
     
    > repadmin /syncall
     
    This only affects active directory, not sysvol.
     
    Monday, February 01, 2016 11:55 AM
  • The error is

    The processing of Group Policy failed. Windows attempted to read the file \\abc.local\sysvol\abc.local\Policies\{6AC1786C-016F-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following:

    a) Name Resolution/Network Connectivity to the current domain controller.

    b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller).

    c) The Distributed File System (DFS) client has been disabled

    Monday, February 01, 2016 12:10 PM
  • > The error is
     
    I know what error you receive... See above: Check FRS/DFSR eventlogs and
    fix your journal wrap error.
     
    Monday, February 01, 2016 3:01 PM
  • Hi,

    I agree with @Martin Binder, we can check FRS or DFS Replication log under Applications and Services Logs in Event Viewer to see if some related events were logged.

    Besides, on server 2008,  we can do a non-authoritative restore for SYSVOL to tackle the issue.

    To do a non-authoritative restore, if we are using FRS to replicate SYSVOL, the following article can be referred to as reference.

    Using the Burflags registry key to reinitialize File Replication Service replica sets

    http://support.microsoft.com/kb/290762

    If we are using DFSR to replicate SYSVOL, the following article can be referred to as reference.

    How to force an authoritative and non-authoritative synchronization for DFSR-replicated SYSVOL (like "D4/D2" for FRS)

    http://support.microsoft.com/kb/2218556

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, February 02, 2016 3:23 AM
    Moderator
  • Hii

      I am using frs replication and in event viewer event id 13508 logged The File Replication Service is having trouble enabling replication from dc1 to dc2. on both dc1 and dc2 got same error.  

    ntfrsutl version command fails on both DC

    Ping is working, AD also sync on both DC

    FRS event 13509 never appear in event viewer


    Net share not shared on dc1
    • Edited by Shil Patel Saturday, February 06, 2016 6:48 AM
    Friday, February 05, 2016 11:35 AM
  • Hi,

    Regarding the FRS issue - even 13508 without trailing 13509, please refer to the following steps to narrow down the issue:

    1. You could follow the below KB to verify that Sysvol is valid in the registry and the file system. Go through and verify that the registry items, file objects, permissions, junction points, etc are all correct on the DC, if they are not then fix them

    315457 How to rebuild the SYSVOL tree and its content in a domain

    http://support.microsoft.com/kb/315457/EN-US

    2. Please try to increase the severity and number of debug logs for FRS to get more information if needed

    221111 Description of FRS entries in the registry

    http://support.microsoft.com/kb/221111/EN-US

    3. Make sure there are no missing subscriber objects for the DC in AD

    312862 Recovering missing FRS objects and FRS attributes in Active Directory

    http://support.microsoft.com/kb/312862/EN-US

    4. Disable or preferably remove AV software to eliminate it from being the culprit, at least make sure sysvol is not being scanned.

    5. Collect simultaneous network traces from the problem DC and its partner that it cannot communicate with while restarting the service on the problem DC and waiting for the 13508 to see if they are getting blocked on the network.

    Hope the above troubleshooting steps are helpful to you.

    Best Regards,

    Alvin Wang


    Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by Shil Patel Thursday, February 11, 2016 6:47 AM
    Monday, February 08, 2016 4:10 AM
    Moderator
  • Thank you Alvin for reply I will try all those steps and let you know about the result.
    • Edited by Shil Patel Monday, February 08, 2016 5:42 AM
    Monday, February 08, 2016 5:23 AM
  • Hii Alvin

         Problem solved by rebuild the sysvol tree

    315457 How to rebuild the SYSVOL tree and its content in a domain

    http://support.microsoft.com/kb/315457/EN-US

    Thank you All for help.

    Thursday, February 11, 2016 6:48 AM