Windows 2019 gpresult /h AD / SYSVOL Version Mismatch

Lorenzo Fongaro 6 Reputation points
2021-11-02T15:46:36.07+00:00

Hello.

I'm trying to understand how to solve this issue: some GPO are not applied to some server due to a AD / SYSVOL Version Mismatch.

I'm looking for a solution for Windows 2019.
The only solution I found is about Windows 8.1 or Windows 2012: it's about a fix to install, but I use Windows 2019, not 2012.

145854-clipboard01.jpg

Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
3,624 questions
Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
2,196 questions
No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Gary Reynolds 8,811 Reputation points
    2021-11-02T20:09:26.303+00:00

    Hi @Lorenzo Fongaro

    The error/warning is caused because the versions numbers of the GPT and GPC components of the GPO don't match. The GPT version number is stored in the AD against the GPO object and the GPC version number is stored in the gpt.ini in the sysvol share.

    Normally as you edit the policy these numbers are incremented and is used to confirm that the GPT and GPC are in sync. For some reason the version number on this policy don't match, hence the warning.

    The easy way to fix this is, is to edit the policy again, by adding and removing a setting, this will cause the version numbers to be updated and should sync the GPT and GPC version numbers.

    Gary.


  2. Dave Patrick 329.8K Reputation points Microsoft MVP
    2021-11-02T15:54:05.907+00:00

    Not a lot to go on but you could try a non authoritative synchronization for
    https://support.microsoft.com/en-us/help/2218556/how-to-force-an-authoritative-and-non-authoritative-synchronization-fo

    Also note the two prerequisites to introducing the first 2019 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR
    https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405

    --please don't forget to upvote and 145510-image.png if the reply is helpful--

    No comments