Clients not getting updates from WSUS Server

I have a Windows 2003 Server running WSUS 3.2.7600.226. The clients are
showing up in the WSUS console and reporting what updates are needed but they
are not downloading/installing the updates. I have approved the updates, I
have ran wuauclt /detectnow /resetauthorization, I have uninstalled and
reinstalled WSUS but the clients still will not get the updates.

Here the WindowsUpdate.log from client:
2009-12-16 08:56:38:421 1716 b9c Misc =========== Logging initialized
(build: 7.4.7600.226, tz: -0500) ===========
2009-12-16 08:56:38:453 1716 b9c Misc = Process:
C:\WINDOWS\System32\svchost.exe
2009-12-16 08:56:39:765 1716 b9c Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2009-12-16 08:56:38:421 1716 b9c Service *************
2009-12-16 08:56:39:765 1716 b9c Service ** START ** Service: Service startup
2009-12-16 08:56:39:765 1716 b9c Service *********
2009-12-16 08:56:39:906 1716 b9c Agent * WU client version 7.4.7600.226
2009-12-16 08:56:39:953 1716 b9c Agent * Base directory:
C:\WINDOWS\SoftwareDistribution
2009-12-16 08:56:39:968 1716 b9c Agent * Access type: No proxy
2009-12-16 08:56:39:968 1716 b9c Agent * Network state: Connected
2009-12-16 08:57:40:926 1716 b9c Agent *********** Agent: Initializing
Windows Update Agent ***********
2009-12-16 08:57:41:004 1716 b9c Agent *********** Agent: Initializing
global settings cache ***********
2009-12-16 08:57:41:004 1716 b9c Agent * WSUS server: http://139.126.249.30
2009-12-16 08:57:41:004 1716 b9c Agent * WSUS status server:
http://139.126.249.30
2009-12-16 08:57:41:004 1716 b9c Agent * Target group: (Unassigned
Computers)
2009-12-16 08:57:41:004 1716 b9c Agent * Windows Update access disabled: No
2009-12-16 08:57:41:052 1716 b9c DnldMgr Download manager restoring 0
downloads

One semantical note... the order of parameters is significant in the
wuauclt.exe command,
the correct command is wuauclt /resetauthorization /detectnow

Are you using client-side targeting (via GP) or server-side targeting?

One concern is that your client is detecting zero updates because it's
scanning "Unassigned Computers" and you have no updates approved for that
group. The answer to this question depends on whether you're using
client-side or server-side targeting.

But, more signifcantly, it would appear you have an incorrect IP Address
configured for your WSUS server, since the WUAgent is reporting an HTTP 404
error trying to find the WSUS server at http://139.126.249.30

Here we see the v7.4 WUAgent has generated a *new* SusClientID . . .

Which is resulting in this well-known 0x8024400D / SOAP 0x12c / 0x80244015
error, which, ironically, is typically traced back to duplicate SusClientID
issues, but is also known to happen in improperly configured database
environments:

http://blogs.technet.com/sus/archive...0d-errors.aspx

Note that the calls to the ReportingWebService are working perfectly, which
tells me that the earlier HTTP 404 errors may be misleading, or else the
/ClientWebService folder is actually missing from the WSUS server.

Here's that ugly HTTP 404 error again -- obviously the URL is correct, or
the Reporting would fail -- so I'd suggest inspecting the installation of
WSUS and verifying that it's properly installed and configured.

I have uninstalled WSUS and IIS and reinstalled both. Now I am having a
different issue. WSUS can Synchronize, but it is failing on the downloading
the updates. We have to go thru a proxy server, which I have put the
information in correctly, but still cannot get updates downloaded.

What is being logged to the Application Event Log on the WSUS Server in
regards to these failed downloads?

It is saying the Content file download failed: Reason: The supplied proxy
server or bypass list is invalid.

I have set the proxy settings up the same as they have been. It is able to
synchronize, but not download the files.

Server name: abc.de.fgh.com/accelerated_pac_base.pac
Port number: 8080

and then it is set to use my credentials.

Then perhaps they are no longer sufficient. Perhaps your proxy administrator
has inappropriately blocked the download of content at the proxy server? All
of this, of course, is assuming that the proxy name and credentials that you
have configured are, in fact, correct.

Also, proxy servers must be able to support simultaneous communications from
a proxy client on both HTTP and HTTPS (SSL) connections. The
synchronization occurs via SSL, but the download occurs using standard
unencrypted HTTP (because all content is digitally signed, so encryption is
unnecessary overhead). I suspect what you'll find is that the proxy server
may be rejecting your non-SSL sessions. If the proxy server can accept both
HTTP and HTTPS requests on port 8080, maintain simultaneous session tracks
for both protocols to the same client, then no additional configuration
outside of the console's Options | Update Source and Proxy Server | Proxy
Server settings dialog.

However, if you need to maintain two separate channels of data flow because
the proxy server needs to manage SSL connections on a port other than 8080,
then you'll need to use the proxycfg.exe utility (on Windows Server 2003) or
netsh winhttp set proxy (on Windows Server 2008) to configure the WinHTTP
proxy to use separate channels for HTTP and HTTPS.

Thank you for your help Lawrence. My WSUS server is now download updates.
Instead of having it go to Microsoft, my WSUS server is downloading them from
another WSUS server. But now it looks like I am back to square one. My pc's
are still not getting updates from the WSUS server. Actually, it looks like
new pc's I have added to the domain are getting updates, just not the
majority of the pc's that were reporting to the WSUS server before we started
having problems.

Here is a client log:

2010-02-02 14:01:26:823 1932 e44 AU ########### AU: Uninitializing
Automatic Updates ###########
2010-02-02 14:01:27:838 1932 e44 Service *********
2010-02-02 14:01:27:838 1932 e44 Service ** END ** Service: Service exit
[Exit code = 0x240001]
2010-02-02 14:01:27:838 1932 e44 Service *************



2010-02-02 14:02:12:933 1932 14f4 Misc =========== Logging initialized
(build: 7.4.7600.226, tz: -0500) ===========
2010-02-02 14:02:12:933 1932 14f4 Misc = Process:
C:\WINDOWS\System32\svchost.exe
2010-02-02 14:02:12:933 1932 14f4 Misc = Module:
C:\WINDOWS\system32\wuaueng.dll
2010-02-02 14:02:12:933 1932 14f4 Service *************
2010-02-02 14:02:12:933 1932 14f4 Service ** START ** Service: Service
startup

There's not much I can tell from this log . . .

Either the client is seriously broken, or there are log entries missing . ..

I see no activity in this log between service startup at 2:03pm local and
system shutdown at 4:07pm local.