Gpo not updating registry
In such a situation one should suspect an issue with the Network Location Service that is deployed on the network.
I have about 100 of these puppies to manage via GPO. After much testing and trial and error, I have learned the following: Sometimes, it is the case that a registry key that is normally created in HKCU can also be created in HKLM.The reason name resolution and thereby all other domain related tasks are failing is the fact that the Direct Access name resolution policies are in place and force all DNS requests for the domain zone to be resolved by the Direct Access DNS service.That one is not reachable as we don’t have a valid Direct Access Connection… They can be found below HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\DNSClient\Dns Policy Config. In my case I could see connectivity (and name resolution) was now working again.But using this script in the Group Policy Shutdown script, it fails.Grasping at straws, I changed the hive in the scripted GPO command to HKLM and voila.. I don't know exactly why, perhaps a "super user" could explain it for us, but I have never found this documented this way, and I hope it helps someone else avoid a few days of hair pulling.Due to my lack of experience, I do not know most of the quirks of the environment that Group Policy scripts must run in.
Here is one set of commands that works in the console but fails in GPO: set o Registry = Get Object("winmgmts:!
Whatever the reason is, a Group Policy is the best way to deploy a Registry Key in an Active Domain Directory Services.
Is it possible to enable Microsoft Updates via a registry key, group policy or by downloading & installing a separate package to 'flip the switch'?
All examples that I found with google point to modifying the HKCU key for this key.
This works in the current session, in regedit or via scripts, and following a reboot, the change is effected.
To clarify, I'm not talking about enabling 'Automatic Updates'.