Printable View
I have 6 WSUS servers, 5 downstream 1 upstream, all run on Win2k Server.
One server has no clients reporting to it, and I cannot figure it out, it is on a site with around 40 pc's and is the only server not to have any clients reporting to it. I have checked the Group Policy and it's identical to the ones for the other WSUS servers but with a different server name e.g http://servername:8530
Any ideas why this server would have no clients reporting to it?
Nope.... but the answer most likely can be found by using the Client Diagnostic Tool and/or reviewing the WindowsUpdate.log.
Output from client diagnostics tool:
WSUS Client Diagnostics Tool
Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is not running. PASS
Wuaueng.dll version 5.8.0.2469. . . . . . . . . . . . . PASS
This version is WSUS 2.0
Checking AU Settings
AU Option is 4: Scheduled Install . . . . . . . . . . . PASS
Option is from Policy settings
Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . NONE
Winhttp local machine ProxyBypass. . . . . . . NONE
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . NONE
User IE ProxyByPass. . . . . . . . . . . . . . NONE
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use
Checking Connection to WSUS/SUS Server
WUServer = http://wsusserver:8530
WUStatusServer = http://wsusserver:8530
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
VerifyWUServerURL() failed with hr=0x80190193
No Error description could be found
I've googled the error, and there is no firewall or ISA server. This server did have SUS and was upgraded, I know when I did this on the SUS servers I had a few problems.
First thing you need to do is update your WSUS servers to =WSUS SP1= if you have not already !!!
This is an HTTP '403' error and is caused because something between the client and IIS is denying access to the WSUS server.
However, since there is no firewall, proxy, or ISA server, then it could be a flaw in the WSUS server. Does the WSUS server (being Windows 2000) have IISLockdown installed/configured? URLScan installed/configured?
Describe your "problems" migrating SUS to WSUS... and how does that fit in with your characterization of these servers as "downstream"? What kind of downstream server is this (replica or autonomous)?
I had numerous issues when migrating my SUS servers to WSUS, one of which I recall involved permissions on a directory (can't remember which one as was a while ago) and also a script I had to run due to replication errors, again I can't recall the details I'm afriad.
The downstream servers are all replica's. Is WSUS SP1 the latest version? I have no probs updating them - WSUS SP1 was just coming out as I finished updating all the SUS servers to WSUS, so was reluctant to do this then, as I had just done around 6 migrations.
If this helps, some output from the windowsupdate.log on one of the clients.
2007-03-13 16:56:01 1484 5d8 Service ** END ** Service: Service exit
[Exit code = 0x240001]
2007-03-13 16:56:01 1484 5d8 Service *************
2007-03-14 08:53:43 1480 5d4 Misc =========== Logging initialized (build:
5.8.0.2469, tz: -0000) ===========
2007-03-14 08:53:43 1480 5d4 Misc = Process: C:\WINNT\system32\svchost.exe
2007-03-14 08:53:43 1480 5d4 Misc = Module: C:\WINNT\system32\wuaueng.dll
2007-03-14 08:53:43 1480 5d4 Service *************
2007-03-14 08:53:43 1480 5d4 Service ** START ** Service: Service startup
2007-03-14 08:53:43 1480 5d4 Service *********
2007-03-14 08:53:43 1480 5d4 Agent * WU client version 5.8.0.2469
2007-03-14 08:53:43 1480 5d4 Agent * SusClientId =
'284016d3-fd4d-468f-a174-a07b067a98c3'
2007-03-14 08:53:43 1480 5d4 Agent * Base directory:
C:\WINNT\SoftwareDistribution
2007-03-14 08:53:43 1480 5d4 Agent * Access type: No proxy
2007-03-14 08:53:43 1480 5d4 Agent * Network state: Connected
2007-03-14 08:54:35 1480 5d4 Agent *********** Agent: Initializing Windows
Update Agent ***********
2007-03-14 08:54:35 1480 5d4 Agent *********** Agent: Initializing global
settings cache ***********
2007-03-14 08:54:35 1480 5d4 Agent * WSUS server: http://wsusserver:8530
2007-03-14 08:54:35 1480 5d4 Agent * WSUS status server:
http://wsusserver:8530
2007-03-14 08:54:35 1480 5d4 Agent * Target group: LIVE
2007-03-14 08:54:35 1480 5d4 Agent * Windows Update access disabled: No
2007-03-14 08:54:35 1480 5d4 DnldMgr Download manager restoring 0 downloads
2007-03-14 08:54:35 1480 5d4 AU ########### AU: Initializing Automatic
Updates ###########
2007-03-14 08:54:35 1480 5d4 AU AU setting next detection timeout to
2007-03-14 08:54:35
2007-03-14 08:54:35 1480 5d4 AU # WSUS server: http://wsusserver:8530
2007-03-14 08:54:35 1480 5d4 AU # Detection frequency: 22
2007-03-14 08:54:35 1480 5d4 AU # Target group: LIVE
2007-03-14 08:54:35 1480 5d4 AU # Approval type: Scheduled (Policy)
2007-03-14 08:54:35 1480 5d4 AU # Scheduled install day/time: Every day at
4:00
I understand. But now... it would be a good thing to expedite deployment of.
Make note, however, that deploying WSUS SP1 in a replica environment does require special considerations. Read the README thoroughly before deploying.
0x80070006 Handle not valid error
0x8024000B call has been cancelled
0x80244008 SOAPCLIENT PARSEFAULT ERROR failed in parsing SOAP fault
Followed by the '403' errors trying to test for the selfupdate:
I rarely recommend this, because ever so rarely is this the =correct= fix. However, in this case, you could have corrupted WUA and/or a corrupted datastore. Try the following:
[a] Disable the Automatic Updates service.
[b] Rename the %windir%\SoftwareDistribution folder to SoftwareDistribution.old
[c] Rerun the installation of WindowsUpdateAgent20-x86.exe using the /wuforce switch.
[d] Reboot the machine.
And see if that clears up this issue. If it doesn't we'll try something new and different. :-)
I ended up removing WSUS and IIS yesterday from the problem box, and reinstalled them all again from the beginging. Low and behold all is working fine now. Can only assume that the migration from SUS to WSUS did not go aswell as I thought :-)
I have 2 WSUS servers 1 normal and 1 downstream server.
I have 2 different group policies and 2 groups related to those policies. Still are the machines from the branch office not attaching to the right WSUS server.
policy wsus1 for group wsus1 most get there updates from the WSUS1 server. policy wsus2 for group wsus2 mostget there updates from the WSUS2 server. but PC still connect to the WSUS1 server. What did I forget ??
The most likely cause is that you've misapplied the policy, or the computer(s) are in the wrong OUs. Please describe exactly how you linked your GPOs to Active Directory.
Are you experiencing this problem only with branch office systems connecting to the upstream server? Is the downstream server a replica server? Do you have reporting rollup enabled on the upstream server?
Let's take a look at the log entries for one of those systems connecting to the wrong server, and see exactly what's happening at the client.