after migration ADC 2012 server to 2022 server , sysvol folder is not updating and error showing sysvol version mismatched

Question

After migration ADC 2012 server to 2022 server , sysvol folder is not updating and error showing sysvol version mismatched, i am unable to create any policy in new 2022 server

Answer 1

Hello mohammed_737,

Thank you for posting in Microsoft Community forum.

1.Did you have only one 2012 Domain Controller and then you migrate it from 2012 to 2022?

2.How did you migrate 2012 DC to 2022? Did you add one 2022 Windows server to the existing domain and then promote this 2022 Windows server to 2022 DC？

3.Is your SYSVOL replication engine DFSR? Check as below:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DFSR\Parameters\SysVols\Migrating Sysvols\LocalState registry subkey. If this registry subkey exists and its value is set to 3 (ELIMINATED), DFSR is being used. If the subkey does not exist, or if it has a different value, FRS is being used.

4.What is the forest functional level and domain functional level? Should be 2008 or higher.

Please check if AD replication between the two DCs are OK. Please run commands below on the PDC.

repadmin /showrepl >C:\rep1.txt

repadmin /replsum >C:\rep2.txt

repadmin /showrepl * /csv >c:\repsum.csv

If the result of all the commands is OK without error, it seems the AD replication works fine.

Then please check whether the error "sysvol version mismatched" occurs on only one GPO or on more than one GPO?

If the error occurs only on one GPO, you can try to edit this GPO, that is:

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.

Here is a similar thread for your reference.

Windows 2019 gpresult /h AD / SYSVOL Version Mismatch - Microsoft Q&A

I hope the information above is helpful.

If you have any question or concern, please feel free to let us know.

Best Regards,

Daisy Zhou

Answer 2

Actually, there was one adc which is 2012 r2 server we wanted to migrate 2012 r2 to 2022, we just add 2022 in domain and did promote as a adc 

And changed the ip of both server and after migration we have shut down the old 2012 r2 server after 6 to 7 hoursToday we checked sysvol folder not updating and not able to create policy and error sysvol version mismatched Please let us know

Answer 3

Hello mohammed_737,

Good day!

Please start the old 2012 r2 domain controller.
Please check the point 3 and point 4 I mentioned above.
Please check AD replication status.

If the AD replication works fine. Then please check whether the error "sysvol version mismatched" occurs on only one GPO or on more than one GPO?

If the error occurs only on one GPO, you can try to edit this GPO, that is:

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.

Here is a similar thread for your reference.

Windows 2019 gpresult /h AD / SYSVOL Version Mismatch - Microsoft Q&A

If you have any question or concern, please feel free to let us know.

Best Regards,

Daisy Zhou

Answer 4

Actually, there was one adc which is 2012 r2 server we wanted to migrate 2012 r2 to 2022, we just add 2022 in domain and did promote as a adc 

And changed the ip of both server and after migration we have shut down the old 2012 r2 server after 6 to 7 hoursToday we checked sysvol folder not updating and not able to create policy and error sysvol version mismatched

Answer 5

Hello mohammed_737,

Good day!

Would you please check the information I mentioned above, so that we can help you better?

Best Regards,
Daisy Zhou