none
Win7 clients reporting "AD / SYSVOL Version Mismatch " (while Win10 are not)

    Question

  • Starting to see a lot of clients reporting:

    AD / SYSVOL Version Mismatch

    We are running a mixed Win7 and win10 environment, and it seems that all Win7 are logging this error while no Win10 are.

    Any idea where to look for issues on this?

    Regards, Lars.

    Wednesday, January 04, 2017 1:47 PM

All replies

  • > AD / SYSVOL Version Mismatch
     
    Where do they report this? If in the RSoP results report: Bug in the report creation :-)
     
    Wednesday, January 04, 2017 2:24 PM
  • Yes, in the Group Policy Result "folder" in Group Policy Management.

    How old is this bug? Havn't noticed it earlier.

    Regards, Lars.

    Wednesday, January 04, 2017 8:35 PM
  • Hi,
    You could track down the offending policy ("Policy {GUID}") and under the sysvol folder on your DCs, navigate to its folder (\DC\sysvol\policies{GUID}) and check the GPT.INI file on all the DCs. It will have a version number in it, and the version number will be different on the different DCs - this is the version mismatch it's complaining about. By doing that, you could check if the version is really mismatched or not or just a “bug” information as Martin said.
    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

    Thursday, January 05, 2017 7:49 AM
    Moderator
  • > How old is this bug? Havn't noticed it earlier.
     
    Saw it first about 3 years ago or so... Opened a bug with MSFT, but it was not fixed - too much effort for a cosmetical thing that would require heavy code changes.
     
    Basically AFAIR the reason is:
     
    The GP evaluation process checks a number of criteria whether to apply a GPO or not. If it is not to be applied due to security filtering, it sets the Sysvol version number to 65535 which will regularly result in differing version numbers. GPOs with differing version numbers never get applied, so the GPO is skipped. The RSoP data that is written to WMI afterwards incorrectly uses the manipulated version number instead of the real one.
     
    Or something like that :-)
     
    Anyway: Since I cannot reproduce this in my testing environment anymore - do you have missing hotfixes or rollup packages?
     
    Thursday, January 05, 2017 11:26 AM
  • Hi,

    I am checking how the issue going, if you still have any questions, please feel free to contact us.

    And if the replies as above are helpful, we would appreciate you to mark them as answers, and if you resolve it using your own solution, please share your experience and solution here. It will be greatly helpful to others who have the same question.

    Appreciate for your feedback.

    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

    Tuesday, January 10, 2017 7:35 AM
    Moderator