I recently downloaded the ADMX files for Windows 11 and I'm trying to figure out whether I should copy and replace the existing files on my Windows Server 2012 (located at C:WindowsPolicyDefinitions). I'm concerned about any potential issues that might arise from doing this. I compared the GroupPolicy.admx file on my Server 2012 with the one I downloaded and didn't find anything that looks destructive. The reason for this upgrade is that we have existing GPOs for Windows 10, but I want to update some devices to Windows 11. Management is hesitant to upgrade the server itself due to fears of things breaking, so I thought I could first add the Windows 11 ADMX files and then see if the existing GPOs still work for both operating systems. If they don't, I'll create new GPOs accordingly. If all goes well, I plan to upgrade the Windows 10 devices to Windows 11, and eventually the server to a newer version. It's a detailed process, but it feels like the right path forward with management's approval.
1 Answer
It's best not to replace the files directly on the server. Instead, you should use a central store located at SYSVOLPoliciesPolicyDefinitions and drop the new ADMX files there. Doing it this way is safer and won't disrupt existing GPOs. Adding newer ADMX files is generally okay, and it maintains backward compatibility. If there’s a mismatch, you may see some extra registry settings in the console, but everything should remain intact. So just remember: avoid overwriting system folders, stick with the central store, and test everything on a few machines first.
Just make sure you test out the GPOs on a smaller scale before pushing it out organization-wide.
I created a PolicyDefinitions folder under SYSVOLmyDomain.localPolicies and moved the old policy files from C:WindowsPolicyDefinitions there before pasting the new downloaded ones. Is that a good process?