No matter what we set in local and domain group policy, on our R1 and only these servers the "Check for updates" option is greyed out. I can change all other WU settings, though. As noted in the marked answer -- almost certainly this is being caused by a policy setting being applied to the machine that is blocking access to the WUApp.
There are three different policy settings that can be used to restrict functionality. Merely removing an active GPO and replacing it with another with values set to Not Configured, may not necessary revert certain registry settings imposed by the previous policy. Hi Lawrence, I have tried probably every single combination of disabled, not configured, etc, etc.
If I reapply policy, I can see the registry updates and I can see different values changed, deleted or created as I try different policy settings. I can also see various options and features in the GUI being disabled, set or enabled. However, I can see absolutely nothing that should disable the "check for updates" option.
Also, this only happens on our R1 systems. It is not happening on Windows or R2. A logical approach to the issue will usually identify the source very quickly. There are only three policies, three registry settings, and howevermany GPOs you actually have applied. So, first, check these three registry values and make sure they do not exist, or if they do, they are disabled set to False :.
If all three registry values are absent, then your problem is not policy-based; skip to the last paragraph. If one of those values does exist then you've not identified the correct policy object, or have looked in the wrong places of the policy object for the settings to disable.
If not, then add one policy back, at a time, which can help to identify the policy that may be causing the issue. If the registry values are not present, then as noted this is not a policy-based issue. In Change Settings observe whether the option Allow all users to install updates on this computer option is checked or unchecked.
If it unchecked, then you've likely identified your cause. Hi Lawrence, thanks for trying to help me with this. I actually believe something is broken on these servers, it's not a major problem for us to not have them patched as they are not in production.
Anyhow, none of the registry entries you mentioned exist. It's been available on every system since Windows Vista was released. I had the same problem and managed to inadvertently resolve it. None of Lawrence's scenarios applied from the post on July 07, PM and checking the Allow all users to install updates on this computer option didn't seem to make any difference , so b ecause I couldn't change it in the Windows Update dialog, I decided to tweak the registry settings.
So I renamed a couple of keys:. Then when I went back into the Windows Update dialog, it was displaying the current setting for updates as disabled i. Don't know if it was just a fluke amongst the many other things I've tried but it might be worth looking at.
Most interesting, considering that what Dave did should have had ZERO impact on the actual functioning of that client. Changing the two specified registry values will have minimal functional impact on the client anyway. Dave was correct about that assumption; however, there's no logical reason why changing those two registry values would have had any impact on the ability to use the WUApp to configure Windows Updates.
Whatever else was blocking access to the ability to run an update scan from the WUApp had nothing to do with the two registry values changed. Lawrence Garvin, M.
To answer the OP, the GP change must be made on the sbs machine. Expand domains and double click your local domain listed under the tree. Click "Default Domain Policy" then choose the settings tab at the top. Right click and edit "Configure Automatic Updates" select setting 5. Please note: Do not post advertisements, offensive material, profanity, or personal attacks.
Please remember to be considerate of other members. All submitted content is subject to our Terms Of Use. General discussion. We would like to turn off Automatic Updates from all of our workstations but the buttons are all greyed out. We have some legacy aps that do not work with sp2 and we are not installing it. The problem is that the we do not want the users to know that "updates are ready to install" especially since they do not have admin rights.
We can not change the settings and we are not running SUS. Any help will be appreciated. Share Flag. All Comments. Collapse -. Automatic updates greyed out. No matter which updates I select to download or install, it just says downloading and the progress bar seems to split in two and just sit there. To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Hi All I went to check for updates on one of our Windows Server R2 servers and was told that this couldnt be done due to the service not running.
I went to the services and found that it was disabled, the option to enable is greyed out. Anyone know how to correct this? Any advice would be appreciated. Popular Topics in Windows Server. Which of the following retains the information it's storing when the system power is turned off?
0コメント