Convert Registry files (.reg) into ADMX/ADML files for GPO

This script will read a v4 or v5 registry file and generate a Vista/W7 Policy file (ADMX) and it's corresponding interface file (ADML).

 
 
 
 
 
4.4 Star
(11)
Add to favorites
Group Policy
3/1/2010
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • dword value
    2 Posts | Last post December 04, 2015
    • Hi,
      
      I have this simple reg file to convert to ADMX.
      -------------------------------------------------------------
      Windows Registry Editor Version 5.00
      
      [HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\3]
      "2701"=dword:00000000
      --------------------------------------------------------------
      Use your conversion tool and it can be seen in Group Policy Editor but after applied the gpo...it shows in gpresult.html that the gpo is applied but the registry key is not created. Please help!
      -Sonny
      
    • Hi Sonny,
               It's a Strange situation the one you are describing.
               This can be due to two different things, either the Tool Failed and the registry is NOT included in the policy, OR there is some issue with the system applying the setting.
               Let's try to figure it out together
               You stated that the policy is listed in GPRESULT.HTML, could you check to make sure that the registry setting is listed as well (gpresult should clearly show the setting to be applied to the computer's registry). Could you further check that the setting is applied at the correct place (for example "user settings" and not "computer settings", etc)
      
                 Best Regards, Marianok
  • HKEY_USERS
    4 Posts | Last post March 09, 2011
    • I have created a .REG file which add a value to HKEY_USERS\.DEFAULT\Keyboard Layout\Preload.
      
      When i use the script the ADMX/ADML file is created succesfully. But when I apply it in a GPO a folder will be created in HKEY_CURRENT_USER like HKEY_CURRENT_USER\HKEY_USERS\.DEFAULT... instead of creating the value in HKEY_USERS\.DEFAULT\Keyboard Layout\Preload.
      
      Does somebody know what i am doing wrong or is this not possible with the script?
    • Dear Jimmy,
      You actually ran into 2 different issues, a mistake on my part and a ADMX limitation.
      The limitation: Will only allow you to configure settings under HKLM and HKCU (as far as I have been able to find). This also means that it will not allow you to set the properties for a user other than the one logged in.
      
      The mistake: I forgot to cover those cases :-(. 
      
      I have updated the post with the corrected version.
      Now the script will process any "HKU\<guid>\" as a "HKCU"
      
      i.e. if you have a setting being applied to for HKEY_USERS\S-1-5-21-9999999999-9999999999-9999999-9999\Software the setting will be applied to for HKEY_CURRENT_USER\Software
      
      So, If you happen to have a .reg file exported from a user you can use that .reg file (without any modification) to create the ADMX file.
      
      I hope this helps !!! 
      Thanks a lot for trying my script and for letting me know about this issue!
      
    • Regarding the use of HKEY_USERS\.DEFAULT, let me clarify one thing so we are all in the same page.  
      
      Unlike common belief, the .DEFAULT subkey is not the “default settings for all users without a profile”; the .DEFAULT key is actually the key for the “Local System” Account. 
      
      In other words, HKEY_USERS \.DEFAULT is just an alias for HKEY_USERS\S-1-5-18.
      (see http://blogs.msdn.com/oldnewthing/archive/2007/03/02/1786493.aspx, http://www.msfn.org/board/topic/122382-hkey-usersdefault-help/ and http://social.msdn.microsoft.com/Forums/en-US/windowscompatibility/thread/f5125b7a-d5e4-4a7b-a9b6-513c5c2e430d )
      
      So, I have good news and bad news.
      
      The GOOD news: If you are actually trying to make some settings for all users, then the tool should work perfectly for you (as explained before, the tool will convert the HKU\.DEFAULT into HKCU)
      
      i.e. if you have a setting being applied to for HKEY_USERS\.DEFAULT\Software the setting will be applied to for HKEY_CURRENT_USER\Software
      
      
      The Bad news: If you are really trying to settings for the “Local system” account, and only that account, then I do not believe that you can do that thru GPO.
      
      I hope this helps !!! 
      Thanks a lot for trying my script and for letting me know about this issue!
      
    • Hi Mariano,
      
      Your problem : ADM to ADMX Migration - Empty Valuenames
      
      may be, I found the anser for you ?? !!
      
      valueName=""
      
      I found this here :
      
      http://social.technet.microsoft.com/Forums/en/winserverGP/thread/e671c301-e312-4e08-aadf-1e058e401d8b
      
      Please read till the end !!!
      
      If the link does not work, google   "ADM to ADMX Migration - Empty Valuenames"