 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / General Topics / September 2005UseWuServer is disabled
I have 2 systems that won't connect correctly, both give me this same failure in the Client Diagnostic: Checking Connection to WSUS/SUS Server AU does not have Policy Set AU does not have Policy Set UseWuServer is disabled . . . . . . . . . . . . . . . . FAIL I looked at the policy, it's fine, even went digging around in the Registry, and I can see my server listed twice there, just like the ones that are working. What else can I look for? The other 10 systems came up immediately. Well.. obviously the policy is not fine, or the Client Diagnostic Tool would not have complained as such. Or, perhaps, the policy is simply not being applied correctly on these two systems. Please export the following registry key and subkeys and post it here, and we'll see what the issue is: HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate >I have 2 systems that won't connect correctly, both give me this same > failure in the Client Diagnostic: [quoted text clipped - 10 lines] > > What else can I look for? The other 10 systems came up immediately. That key isn't there at all... The one place I found it was (this is a Windows 200 Server): HKEY_USERS\...\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\LocalMachine\Software\Policies\Microsoft\Windows\WindowsUpdate "WUServer"="http://...." "WUStatusServer"="http://...." It does exist on one that I checked that is working correctly. > Well.. obviously the policy is not fine, or the Client Diagnostic Tool would > not have complained as such. [quoted text clipped - 19 lines] > > > > What else can I look for? The other 10 systems came up immediately. If the policy has been applied to the system correctly, the key will exist. If the key does not exist, the policy has not been applied to the system correctly. The registry pathname that you quote is quite intriguing, but I'll have to pass on commenting on it specifically, as I know very little about what might be written into the HKEY_USERS key... however, I will venture a guess as to this: You may have configured the WSUS policy as a /USER/ policy... rather than a /COMPUTER/ policy. If the wuau.adm was imported into the Computer Configuration tree, you'll have WSUS policy settings located at: \Computer Configuration\Administrative Templates\Windows Components\Windows Update If you imported the template incorrectly, that would also account for the absence of the key in HKLM. Of course.. since you have 10 other systems working correctly, and only 2 misbehaving, I'm really confused, because that doesn't sound like an issue of the template being improperly imported. > That key isn't there at all... > [quoted text clipped - 34 lines] >> > >> > What else can I look for? The other 10 systems came up immediately. I thought about that too, and checked it about 3 times to make sure. The policy under the User Configuration, Windows Update only shows one policy "Remove access to use all Windows Update features" just like the others.. > If the policy has been applied to the system correctly, the key will exist. > If the key does not exist, the policy has not been applied to the system [quoted text clipped - 58 lines] > >> > > >> > What else can I look for? The other 10 systems came up immediately. Yes... /THAT/ policy is a User-based policy. What do you have under Computer Configuration\Administrative Templates\Windows Components\Windows Update ??? >I thought about that too, and checked it about 3 times to make sure. The > policy under the User Configuration, Windows Update only shows one policy [quoted text clipped - 71 lines] >> >> > >> >> > What else can I look for? The other 10 systems came up immediately. maybe you can use group policy management console to see incompatible settings in diffeerent gpo's. Experienced it myself when 1 setting of my wsus gpo was overruled by another gpo. > Yes... /THAT/ policy is a User-based policy. > [quoted text clipped - 85 lines] >>> >> > What else can I look for? The other 10 systems came up >>> >> > immediately. What I endded up doing, was exporting my keys: [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate] and importing them into the total of 4 systems that didn't take (so far, out of 21) - worked fine. > Yes... /THAT/ policy is a User-based policy. > [quoted text clipped - 42 lines] > >> > > >> > HKEY_USERS\...\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\LocalMachine\Software\Policies\Microsoft\Windows\WindowsUpdate > >> > "WUServer"="http://...." > >> > "WUStatusServer"="http://...." [quoted text clipped - 28 lines] > >> >> > > >> >> > What else can I look for? The other 10 systems came up immediately. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2010 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.