Ever seen extra registry settings in your group policy manager console?
This most likely came when you updated your ADMX templates with new Windows 10 templates, but no worries your settings are not lost!
The settings will still apply on the supported operating system, but if you want to change the setting? Do I have to delete the group policy and create a new? No, no!
The reason for “Extra Registry Settings” are simply that the ADMX files cannot translate the setting into a “clickable” settings.
Very, very short explanation of ADMX/ADML
When you update the group policy templates they consist of two file types ADMX and ADML.
ADMX these files are translator files from a registry setting to a graphic interface, this is also where all the options for the settings are stored
ADML are located in a language folder, i.e. en-us. And this is where all the settings are translated into your language.
These pictures may help you to understand what the files are used for
The ADMX file, hold information like where the setting are located and what type of setting Machine/User, Setting value and more
In the below picture I try to describe how the ADML are used to translate the variables in ADMX to a more user friendly text
So what actually happens when Extra registry settings is showing up for you is that a setting you have set long time ago is not found in any ADMX file anymore.
All settings are matched to the a key and valueName in the ADMX file, and if the setting isn’t found “Extra registry setting” will show up.
Ok, so I understand, but how do I solve this? – There are a couple of ways
- Delete the group policy and re-create it. May not be the most time efficient solution
The other two options requires that you either have the old ADMX/ADML files (you can copy them from an other computer: %WinDir%\PolicyDefinitions) or just have an old computer installed with the target operating system you need to view the setting
- You can locate the central SYSVOL store. Backup the existing \\domain\Sysvol\domain\Policies\PolicyDefinitions folder and replace the ADMX/ADML files with the old once. When you are done don’t forget to restore. I would recommend this solution in a lab environment or very, very small environment.
- My favorite, logon to an old computer, or a management computer. Start my installing appropriate version of RSAT (Remote Server Administration Tools) and add the feature of Group Policy Management Console. Place your old ADMX/ADML files in the local PolicyDefinitions folder (%WinDir%\PolicyDefinitions), NOT on the central store. Now to the nice part, create/change this registry key HKLM\SOFTWARE\Policies\Microsoft\Windows\Group Policy\EnableLocalStoreOverride [REG_DWORD] = 1. Restart the group policy mangement console, locate your group policy object and now you can manage the setting. When you are done, just change back the registry value to 0 or delete it.
The best part with the last option is that you may have multiple PolicyDefinitions folders, like the illustration below, and depending what you want just rename the folder to PolicyDefinitions and restart GPMC – done.
You can use this command to change the registry value
REG.exe ADD “HKLM\SOFTWARE\Policies\Microsoft\Windows\Group Policy” /v EnableLocalStoreOverride /t REG_DWORD /d 1 /f
REG.exe ADD “HKLM\SOFTWARE\Policies\Microsoft\Windows\Group Policy” /v EnableLocalStoreOverride /t REG_DWORD /d 0 /f
Are you running Windows 7/8.x/2008R2/2012/2012R2 then you need a KB, this KB also describes this registry change
Did I miss anything or did you notice something wrong? I’d be happy to hear from you, you can reach me directly from contact page or twitter