none
Removing Registry Settings on Clients Created by .ADMX Files

    Question

  • Hi

    I'm using .ADMX file locally on one of my admin workstation to push some registry settings on clients. My question is, if I delete the .ADMX file from the admin workstation, will the registry settings be affected on the clients.

    If there's no impact of deleting the .ADMX files, how can I revert the registry settings on the client to default values.

    Thanks

    Taranjeet Singh


    zamn

    Friday, February 26, 2016 11:51 AM

Answers

All replies

  • Hi
     
    Am 26.02.2016 um 12:51 schrieb Taranjeet Singh:
    > if I delete the .ADMX file from the admin workstation, will the registry
    > settings be affected on the clients
     
    No. ADM/ADMx only provide pattern/template with a friendly display name
    and structure to write registry settings into registry.pol file.
     
    If you remove the template, you can no longer edit the settings, and
    probalby you will not "see" them any longer in gpeditot, but they are
    still there.
    -> GPMC -> Report -> Additionale Registry Keys
     
    (Mostly) Everytime you find an entry like that in the report, the GPMC
    is missing appropriate ADM/ADMx Files.
    But the settings exists, thats why they are reported ...
     
    Mark
    --
    Mark Heitbrink - MVP Windows Server - Group Policy
     
    GPO Tool: http://www.reg2xml.com - Registry Export File Converter
     
    Friday, February 26, 2016 12:22 PM
  • Hi Mark

    Thanks for the clarification. I am in a situation where one of the team members deleted the .ADMX template and now when we're importing the template back the old settings that we want to revert are still shown on the client (and are appearing in the GPMC under "Extra Registry Settings" node. Although the new settings are appearing under appropriate node) so effectively we can say that new settings although configured are not overriding the old ones.

    I noticed that the old settings are visible in "Regisrty.pol" file in the SYSVOL folder on domain controllers.

    Not sure how to get rid of them.

    Request people to share their views or any such previous experience.

    Thanks

    Taranjeet Singh 


    zamn


    Friday, February 26, 2016 3:12 PM
  • "Extra Registry Settings" will be displayed in the RSoP (gpresults) report, if the machine where the RSoP/gpresult is *missing* the relevant ADM or ADMX, or, if you have configured a Central Store, if it is missing from the CS.

    if you use GPMC on a DC and are not using a CS, the default place to check is c:\windows\policydefinitions (if it's ADMX+ADML)

    what setting is this? you can see in the Extra Registry Settings, the registry key/value, and you can search for the registry key/path and find which ADMX it should appear in, and then you know which ADMX+ADML you need to replace.
    (or if you already know which file(s) were deleted)

    you need to consider the version of the ADMX+ADML required, if it's a Windows setting.
    Older versions of Windows ADMX+ADML files, might have the same name as newer versions, but the newer version files do contain additional settings compared to older file versions (this is how new Windows features are introduced without losing/confusing older/existing features)


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Saturday, February 27, 2016 11:10 AM
  • Hi
     
    Am 26.02.2016 um 16:12 schrieb Taranjeet Singh:
    > I noticed that the old settings are visible in "Regisrty.pol" file in
    > the SYSVOL folder on domain controllers.
    > Not sure how to get rid of them.
     
    Long way:
    find the right ADM(x) files to set them back to "not configured"
     
    very long way:
    use powershell set-gpregistryvalue
    and set everey single entry to not configured
     
    easy way:
    Use a tool like Registry Workshop
    it can read/write *.pol files aswell
     
    If you are going the easy way, edit the GPO aswell with GPEditor and set
    one policy to "Enabled" and back to "not configured", just to update and
    raise the Version of the GPO.
     
    Mark
     
    --
    Mark Heitbrink - MVP Windows Server - Group Policy
     
    GPO Tool: http://www.reg2xml.com - Registry Export File Converter
     
    Saturday, February 27, 2016 3:42 PM
  • Hi Guys

    Thanks for your support and information. I was able to fix this by creating a new GPO and manually copying the settings from old GPO to new one. Un-linked the old GPO and deleted the link of the GPO from the OU and linked the new GPO to this OU.

    Thanks

    Taranjeet Singh 


    zamn

    Monday, March 7, 2016 8:34 AM