Networks

Ask something
Question Locked

WSUS Client Updates

0 helpful
10 replies

by dboyce

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have re-installed Windows Update Service 3.1 on our servers. My sychronization has been successful, but I am unable to get any of the machines (2000, xp, vista) to respond to the client. I do see all machines on my domain and have added them to 2 computer groups. Is there a new client that I need to push down to my machines? Also, My GPO is very simple and only tells Windows Update to point to my WSUS server, so I am assuming something is out of sync with my client and server.

10 replies

by Member 30634329

1) The WSUS Server responds to the Automatic Updates client on each PC. Make sure the service is running.

2) Take a look at the C:\WINDOWS\WindowsUpdate.log file on a PC and see if it is in fact trying to communicate with the WSUS server, see if there are any errors.

3) Your PC's need to be able to communicate with the WSUS server over HTTP port 80. Make sure this port isn't being blocked by a firewall (including Windows Firewall).

by dboyce

Our GPO has Windows FW turned off as its defaults so I think I am good there. This product was working up until Feb 14, which I believe was when the SP1 was applied. The old IT person here has left and it wasn't working at all and reinstalled it. I noticed that after the reinstall and doing some reading that the selfupdate virtual directory wasn't created at all so I created that and pointed it to the local directory. I just think I have a problem with the client trying to re-connect to a different installation of update services 3.1. Any thoughts? It appears from my local logs that the windows update service (is running) is trying to connect.

2008-04-30 15:01:00:094 1008 e5c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190193
2008-04-30 15:01:00:094 1008 e5c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190193
2008-04-30 15:01:00:136 1008 e5c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190193
2008-04-30 15:01:00:136 1008 e5c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190193
2008-04-30 15:01:00:179 1008 e5c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190193
2008-04-30 15:01:00:179 1008 e5c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190193
2008-04-30 15:01:00:223 1008 e5c Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80190193
2008-04-30 15:01:00:223 1008 e5c Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80190193
2008-04-30 15:01:00:223 1008 e5c Misc WARNING: DownloadFileInternal failed for http://SMSSERVER/selfupdate/wuident.cab: error 0x80190193
2008-04-30 15:01:00:223 1008 e5c Setup WARNING: SelfUpdate check failed to download package information, error = 0x80244018
2008-04-30 15:01:00:223 1008 e5c Setup FATAL: SelfUpdate check failed, err = 0x80244018
2008-04-30 15:01:00:223 1008 e5c Agent * WARNING: Skipping scan, self-update check returned 0x80244018
2008-04-30 15:01:00:402 1008 e5c Agent * WARNING: Exit code = 0x80244018
2008-04-30 15:01:00:402 1008 e5c Agent *********
2008-04-30 15:01:00:402 1008 e5c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2008-04-30 15:01:00:402 1008 e5c Agent *************
2008-04-30 15:01:00:402 1008 e5c Agent WARNING: WU client failed Searching for update with error 0x80244018
2008-04-30 15:01:00:403 1008 ea8 AU >>## RESUMED ## AU: Search for updates [CallId = {956491FB-67E1-4F84-903B-678D2D917530}]
2008-04-30 15:01:00:403 1008 ea8 AU # WARNING: Search callback failed, result = 0x80244018
2008-04-30 15:01:00:403 1008 ea8 AU # WARNING: Failed to find updates with error code 80244018
2008-04-30 15:01:00:403 1008 ea8 AU #########
2008-04-30 15:01:00:403 1008 ea8 AU ## END ## AU: Search for updates [CallId = {956491FB-67E1-4F84-903B-678D2D917530}]
2008-04-30 15:01:00:403 1008 ea8 AU #############
2008-04-30 15:01:00:403 1008 ea8 AU Need to show Unable to Detect notification
2008-04-30 15:01:00:403 1008 ea8 AU AU setting next detection timeout to 2008-05-01 00:01:00
2008-04-30 15:01:00:403 1008 ea8 AU Setting AU scheduled install time to 2008-05-01 07:00:00
2008-04-30 15:01:05:223 1008 e5c Report REPORT EVENT: {0BAA1CF5-D733-4B82-BE31-07C1F95B26EE} 2008-04-30 15:01:00:223-0400 1 148 101 {D67661EB-2423-451D-BF5D-13199E37DF28} 1 80244018 SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x80244018.

by Member 30634329

A quick Google search shows that the errors in your log correspond to HTTP error 403 (access denied).
Since you had to recreate the virtual directory, I would check all IIS permissions on your WSUS server to make sure they are correct. Here is a link to how they are supposed to be configured:

http://wsusinfo.onsitechsolutions.com/articles/016.htm

Also do your clients access web sites using a proxy server? If so you will need to make sure that local sites (such as your WSUS server) are whitelisted.

by dboyce

It appears that you were correct on the IIS issue as some machines are checked in now. Of the 886+ machines within the 2 containers I have created, Only about 5-10 have checked in with a status. Is there something wrong with the clients now? I manually tried to do the wuauclt.exe /detectnow on a couple of them close to me, but none have reported a status. Not sure what in the logs i should be looking at. Any help is appreciated.

by Member 30634329

The only logs on the client is C:\WINDOWS\WindowsUpdate.log, which should show why the client couldn't report status.

What you can do is this:

1) Stop the Automatic Updates service on the client.
2) Delete the C:\WINDOWS\WindowsUpdate.log file and the C:\WINDOWS\SoftwareDistribution\ directory.
3) Start the Automatic Updates service.

by churdoo

Run this on some test clients and see if they report in. I think they will. I believe that sine WSUS was re-installed, you need to run the /resetauthorization switch to re-sync the authorization with the new install.

by nic

Hi I have exactly the same problem, I'm runing WSUS 3.1 on a Windows 2008 64 bit machine, any sugestions / ideas wll GREATLY appreciated.

by churdoo

What troubleshooting steps have you taken? Have you followed the steps identified in the year+ old article to which you responded? You should start a new post and include some of the troubleshooting steps you've taken.

by cg it

I've seem more than a few year old questions all of a sudden showing up on the forums.

This discussion is closed to new replies.