WSUS issue.. Not yet reported stauts

albanga

Hi All,

I seem to be having ANOTHER issue with WSUS. I was on here recently asking abot getting ghosted machines into the WSUS console. After several failed attempts i was finally able to make them appear by the use of the following script;

net stop wuauserv
reg delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /f
ren c:\windows\SoftwareDistribution SoftwareDistribution.old
wuauclt /resetauthorization /detectnow /runhandlercomserver

Once i ran this script the ghosted machines finally appeared in the WSUS console. The problem now lies in that all the XP machines have appeared but there status is Not yet reported. Im guessing by tempaering with the software distribution folder in thw windows directory that i have somehow broken it.

Does anyone have any suggestions on what i could try?

Below is also from the end of my windowsupdate.log on one of the clients not reporting status. I triggered this by running a wuauclt /detectnow /reauthorization

2008-12-24 10:37:10+1100 1120 440 Triggering AU detection through DetectNow api
2008-12-24 10:37:10+1100 1120 b58 AU received event of 1
2008-12-24 10:37:10+1100 1120 b58 WU client succeeds CClientCallRecorder::BeginFindUpdates from AutomaticUpdates with call id {3466A94B-1FD2-4549-AC7B-B194887AA889}
2008-12-24 10:37:10+1100 1120 964 WU client executing call {3466A94B-1FD2-4549-AC7B-B194887AA889} of type Search Call
2008-12-24 10:37:10+1100 1948 3ac Trying to make out of proc datastore active
2008-12-24 10:37:11+1100 1948 3ac Out of proc datastore is now active
2008-12-24 10:37:11+1100 1120 964 Send failed with hr = 80072efd.
2008-12-24 10:37:11+1100 1120 964 SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)>
2008-12-24 10:37:13+1100 1120 964 Send failed with hr = 80072efd.
2008-12-24 10:37:13+1100 1120 964 SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)>
2008-12-24 10:37:14+1100 1120 964 Send failed with hr = 80072efd.
2008-12-24 10:37:14+1100 1120 964 SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)>
2008-12-24 10:37:15+1100 1120 964 Send failed with hr = 80072efd.
2008-12-24 10:37:15+1100 1120 964 SendRequest failed with hr = 80072efd. Proxy List used: <(null)> Bypass List used : <(null)>
2008-12-24 10:37:15+1100 1120 964 DownloadFileInternal failed for http://TST01:8530/SelfUpdate/wuident.cab: error 0x80072efd
2008-12-24 10:37:15+1100 1120 964 IsUpdateRequired failed with error 0x80072efd
2008-12-24 10:37:15+1100 1120 964 PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2008-12-24 10:37:15+1100 1120 964 WU client failed Searching for update with error 0x80248008
2008-12-24 10:37:15+1100 1120 964 Search Callback Failed, hr is 0x80248008
2008-12-24 10:37:15+1100 1120 964 Setting next AU detection timeout to 2008-12-24 00:28:33
2008-12-24 10:37:15+1100 1120 964 Setting AU scheduled install time to 2008-12-30 17:00:00
2008-12-24 10:37:15+1100 1120 964 WU client calls back to search call AutomaticUpdates with code Call failed and error 0x80248008
2008-12-24 10:37:15+1100 1120 964 WU client completed and deleted call {3466A94B-1FD2-4549-AC7B-B194887AA889}

blargoe

Does Windows Update website work? Usually one of the first things to check if you can't get WSUS client to get updates after restarting the service.

Is there a proxy server in your environment?

Client firewall?

Claymoore

Have you tried using the FQDN of your WSUS server in the GPO setting? Instead of http://server:8530 , try http://server.domain.com:8530. This may just be a name resolution problem.

Another tool that might help you troubleshoot this faster is SpecOps GPupdate. It adds some extensions to ADUC that allow you to right-click and force a GPupdate and Windows Update. It's free and I've been using it for a couple of weeks after reading about it in the 2008 Group Policy Resource kit. You can get more information and download here:
http://www.specopssoft.com/products/specopsgpupdate/

hypnotoad

My favorite WSUS hint is to always run WSUS in a virtual machine so it can be wiped out and re-built easily.

Might be a DNS thing. I'd try the FQDN and also make sure the firewalls are not interferring.

Can you post output from the clientdiag tool (downloadable here http://technet.microsoft.com/en-us/wsus/bb466192.aspx)?