revert settings from GPO

%3CLINGO-SUB%20id%3D%22lingo-sub-2297906%22%20slang%3D%22de-DE%22%3Erevert%20settings%20from%20GPO%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2297906%22%20slang%3D%22de-DE%22%3E%3CP%3EHello%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20to%20disable%20the%20ability%20for%20our%20RDS%20terminalserver%20users%20to%20install%20windows%20updates%20respectively%20I%20wanted%20to%20disable%20the%20message%20about%20new%20updates.%3C%2FP%3E%3CP%3ESo%20I%20changed%20our%20windows%20updates%20GPO%20for%20the%20RDS%20servers%20and%20added%20the%20option%20to%20%22remove%20access%20to%20use%20all%20windows%20update%20features%22%2C%20because%20misleading%20i%20thougt%20this%20setting%20would%20only%20affect%20default%20users%20and%20NOT%20the%20administrators.%20Sadly%20the%20setting%20also%20affects%20the%20admin%20users.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20I%20tried%20to%20change%20the%20set%20GPO%20setting%20from%20%22enabled%22%20to%20%22not%20configured%22%2C%20which%20did%20not%20work.%3C%2FP%3E%3CP%3EThen%20I%20change%20the%20setting%20to%20%22disabled%22%2C%20which%20so%20did%20not%20work.%3C%2FP%3E%3CP%3EThen%20I%20made%20a%20completely%20new%20GPO%20and%20configured%20the%20setting%20in%20this%20GPO%20to%20%22disabled%22.%3C%2FP%3E%3CP%3ERSOP.msc%20shows%2C%20that%20the%20new%20GPO%20respectively%20the%20disabled%20settings%20is%20correctly%20applied.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegardless%20the%20windows%20update%20settings%20are%20still%20greyed%20out%20with%20the%20hint%20%22the%20option%20is%20managed%20by%20your%20organization%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20can%20I%20reset%20the%20access%20to%20the%20windows%20update%20functionality%20on%20the%20server%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20You%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EChild%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2297906%22%20slang%3D%22de-DE%22%3E%3CLINGO-LABEL%3Erevert%20GPO%20setting%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2298514%22%20slang%3D%22en-US%22%3ERe%3A%20revert%20settings%20from%20GPO%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2298514%22%20slang%3D%22en-US%22%3EAll%20GPOs%20settings%20are%20hard-coded%20with%20registry%20%2C%20according%20to%20your%20policy%20settings%20For%20users%2C%20to%20Remove%20access%20to%20use%20all%20Windows%20Update%20features%20we%20could%20edit%20below%20registry%20key%3A%3CBR%20%2F%3E%3CBR%20%2F%3EHKEY_CURRENT_USER%5CSoftware%5CMicrosoft%5CWindows%5CCurrentVersion%5CPolicies%5CWindowsUpdate%3CBR%20%2F%3EDisableWindowsUpdateAccess%3CBR%20%2F%3E%3CBR%20%2F%3EPrevents%20users%20from%20connecting%20to%20the%20Windows%20Update%20website.%3CBR%20%2F%3E%3CBR%20%2F%3ERange%20%3D%201%7C0%3CBR%20%2F%3E%3CBR%20%2F%3E1%20%3D%20Enabled.%20All%20Windows%20Update%20features%20are%20removed.%3CBR%20%2F%3E0%20%3D%20Disabled%20or%20not%20configured.%20All%20Windows%20Update%20features%20are%20available%3CBR%20%2F%3E%3CBR%20%2F%3EI%20would%20suggest%20with%20creating%20a%20new%20policy%20with%20register%20hive%20gpo%20settings%20referred%20to%20above%20path%20by%20deleting%20the%20key%20for%20one%20or%20two%20server%20and%20place%20it%20to%20all%20servers%20based%20on%20OU%20%2F%20Domain%20level%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2300891%22%20slang%3D%22de-DE%22%3ERe%3A%20revert%20settings%20from%20GPO%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2300891%22%20slang%3D%22de-DE%22%3EThank%20you%20for%20the%20reply.%3CBR%20%2F%3EI%20tried%20the%20folowing%20settings%3A%20%3CBR%20%2F%3E%3CBR%20%2F%3E%20%5BHKEY_LOCAL_MACHINE-SOFTWARE-Microsoft-Windows-CurrentVersion-Policies-WindowsUpdate%5D%20%3CBR%20%2F%3E%20%22DisableWindowsUpdateAccess%22%3Ddword%3A00000000%20%3CBR%20%2F%3E%3CBR%20%2F%3E%20%5BHKEY_CURRENT_USER-SOFTWARE-Microsoft-Microsoft-Windows-CurrentVersion-Policies-WindowsUpdate%5D%20%3CBR%20%2F%3E%20%22DisableWindowsUpdate%22%3Ddword%3A00000000%20%3CBR%20%2F%3E%3CBR%20%2F%3E%20sadly%20non%20of%20them%20worked%3B%20the%20server%20still%20shows%20the%20message%20%22This%20option%20is%20managed%20by%20your%20organization.%22%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2302006%22%20slang%3D%22en-US%22%3ERe%3A%20revert%20settings%20from%20GPO%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2302006%22%20slang%3D%22en-US%22%3EPlease%20check%20any%20of%20the%20concerned%20device%20as%20still%20pointing%20the%20backed%20link%20using%20Gplink%20and%20GPoption%20attribute%20from%20ADSI%20edit%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2317369%22%20slang%3D%22de-DE%22%3ERe%3A%20revert%20settings%20from%20GPO%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2317369%22%20slang%3D%22de-DE%22%3Esorry%2C%20I%20don't%20what%20you%20exactly%20mean%3F%20what%20do%20you%20want%20from%20the%20ADSI%20edit%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2317484%22%20slang%3D%22en-US%22%3ERe%3A%20revert%20settings%20from%20GPO%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2317484%22%20slang%3D%22en-US%22%3EPossibilities%20-I%3CBR%20%2F%3E%3CBR%20%2F%3EWhen%20any%20group%20policies%20using%20Group%20Policy%20Editor%20(gpedit.msc)%2C%20all%20policies%20are%20stored%20in%20the%20following%20folders%3A%3CBR%20%2F%3E%3CBR%20%2F%3EC%3A%5CWindows%5CSystem32%5CGroupPolicy%3CBR%20%2F%3EC%3A%5CWindows%5CSystem32%5CGroupPolicyUsers.%3CBR%20%2F%3E%3CBR%20%2F%3ETo%20reset%20or%20remove%20all%20applied%20group%20policies%2C%20you%20just%20need%20to%20delete%20these%202%20folders%3A%20GroupPolicy%20and%20GroupPolicyUsers.%3CBR%20%2F%3EForce%20the%20policy%3CBR%20%2F%3E%3CBR%20%2F%3EPossibilities-II%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20gPLink%20attribute%20holds%20a%20list%20of%20all%20Group%20Policy%20containers%20linked%20to%20the%20container%20and%20a%20number%20for%20each%20listed%20Group%20Policy%20container%2C%20that%20represents%20the%20Enforced%20(previously%20known%20as%20No%20Override)%20and%20Disabled%20option%20settings.%20The%20list%20appears%20in%20priority%20order%20from%20lowest%20to%20highest%20priority%20GPO.%3CBR%20%2F%3EThe%20gPOptions%20attribute%20holds%20an%20integer%20value%20that%20indicates%20whether%20the%20Block%20Policy%20Inheritance%20option%20of%20a%20domain%20or%20OU%20is%20enabled%20(0)%20or%20disabled%20(1).%3CBR%20%2F%3E%3CBR%20%2F%3ENavigate%20to%20mentioned%20OU%2C%20where%20the%20servers%20reside%2C%20and%20ensure%20the%20GPlink%20option%20based%20GUID%20is%20still%20available%20even%20after%20removing%20the%20GPO%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2329845%22%20slang%3D%22en-US%22%3ERe%3A%20revert%20settings%20from%20GPO%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2329845%22%20slang%3D%22en-US%22%3Ethank%20you%20for%20the%20reply!%3CBR%20%2F%3EI%20tried%20option%201%20and%20deleted%20the%20GroupPolicy%20and%20GroupPolicy-User%20folder%20in%20system32.%3CBR%20%2F%3Eafter%20gpupdate%20%2Fforce%20and%20some%20additional%20reboots%20the%20folders%20still%20don%60t%20get%20generated%20automatically%20again.%3CBR%20%2F%3EIn%20my%20oppinion%20the%20server%20does%20not%20pull%20any%20new%20GPOs%20%2F%20GPO%20sesstings%20from%20the%20AD.%3C%2FLINGO-BODY%3E
Occasional Contributor

Hello,

 

I tried to disable the ability for our RDS terminalserver users to install windows updates respectively I wanted to disable the message about new updates.

So I changed our windows updates GPO for the RDS servers and added the option to "remove access to use all windows update features", because misleading i thougt this setting would only affect default users and NOT the administrators. Sadly the setting also affects the admin users.

 

Then I tryed to change the set GPO setting from "enabled" to "not configured", which did not work.

Then I change the setting to "disabled", which also did not work.

Then I made a completely new GPO and configured the setting in this GPO to "disabled".

RSOP.msc shows, that the new GPO respectively the disabled settings is correctly applied.

 

Regardless the windows update settings are still greyed out with the hint "the option is managed by your organization".

 

 

How can I reset the access to the windows update functionality on the server?

 

 

Thank you

 

Kind regards

 

 

7 Replies
All GPOs settings are hard-coded with registry , according to your policy settings For users, to Remove access to use all Windows Update features we could edit below registry key:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\WindowsUpdate
DisableWindowsUpdateAccess

Prevents users from connecting to the Windows Update website.

Range = 1|0

1 = Enabled. All Windows Update features are removed.
0 = Disabled or not configured. All Windows Update features are available

I would suggest with creating a new policy with register hive gpo settings referred to above path by deleting the key for one or two server and place it to all servers based on OU / Domain level
Thank you for the reply.
I tryed the folowing settings:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\WindowsUpdate]
"DisableWindowsUpdateAccess"=dword:00000000

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\WindowsUpdate]
"DisableWindowsUpdateAccess"=dword:00000000

sadly non of them worked; the server still shows the message "This option is managed by your organization."
Please check any of the concerned device as still pointing the backed link using Gplink and GPoption attribute from ADSI edit
sorry, I don´t what you exactly mean? what do you want from the ADSI edit?
Possibilities -I

When any group policies using Group Policy Editor (gpedit.msc), all policies are stored in the following folders:

C:\Windows\System32\GroupPolicy
C:\Windows\System32\GroupPolicyUsers.

To reset or remove all applied group policies, you just need to delete these 2 folders: GroupPolicy and GroupPolicyUsers.
Force the policy

Possibilities-II

The gPLink attribute holds a list of all Group Policy containers linked to the container and a number for each listed Group Policy container, that represents the Enforced (previously known as No Override) and Disabled option settings. The list appears in priority order from lowest to highest priority GPO.
The gPOptions attribute holds an integer value that indicates whether the Block Policy Inheritance option of a domain or OU is enabled (0) or disabled (1).

Navigate to mentioned OU, where the servers reside, and ensure the GPlink option based GUID is still available even after removing the GPO
thank you for the reply!
I tried option 1 and deleted the GroupPolicy and GroupPolicy-User folder in system32.
after gpupdate /force and some additional reboots the folders still don`t get generated automatically again.
In my oppinion the server does not pull any new GPOs / GPO sesstings from the AD.
Check any events %SystemRoot%\System32\Winevt\Logs\Microsoft-Windows-GroupPolicy%4Operational.evtx

I have tested this by deleting all the subfolders from the root folder and event says

Next policy processing for domain\user will be attempted in 102 minutes.