none
GPOs are sometimes not applied: AD/SYSVOL version mismatch

    Question

  • Hello Everyone,

    we have two domain controllers with Windows Server 2012 R2 in our network.

    Sometimes applying GPOs to some clients is not working correctly.

    After rebooting the client computer there is a chance that some GPOs can not be applied due to AD/SYSVOL version mismatch.
    This is not always the case. Sometimes after a reboot all GPOs can be applied correctly and sometimes not. I did not recognize any pattern yet.

    Noticeable is when the AD/SYSVOL version mismatch occurs, in the gpresult it is always displayed with the same old version for one specific GPO:
    In our example it is: AD (289), SYSVOL (108)

    Why is it always SYSVOL 108? Even after a succesful apply of that particular GPO and another version mismatch afterwards it is always SYSVOL 108.
    Is there some kind of GPO caching on the client?

    If there is no mismatch error, then the version is displayed as "AD (289), SYSVOL (289)" and the GPO was applyed successfully.

    What we already tried:

    • Leave the Domain, reboot and join again.
    • Do some dummy changes in the GPOs which can not be applied
    • gpupdate /force /boot /sync
    • Checked with gpresult whether there is a version mismatch or not
    • pushing GPO Update from a DC

    Best regards
    Marcel

    Friday, March 24, 2017 12:11 PM

All replies

  • > Noticeable is when the AD/SYSVOL version mismatch occurs, in the gpresult it is always displayed with the same old version for one specific GPO:
    > In our example it is: AD (289), SYSVOL (108)
     
    Repair sysvol replication on the broken DC:
     
     
    Friday, March 24, 2017 1:30 PM
  • Hi Marcel,

    Was your issue resolved? If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    If you resolve it using your own solution, please share your experience and solution here. It will be very beneficial for other community members who have similar questions. If no, please reply and tell us the current situation in order to provide further help.

    Best Regards,

    Wendy


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

    Friday, March 31, 2017 9:22 AM
    Moderator