WSUS 3.0 - Client not reporting status

ntossiou
ntossiou used Ask the Experts™
on
Hello,

I have a problem with WSUS 3.0. I am running a Windows Server 2003 (SP2) infrastructure with AD and GP. I recently upgraded to WSUS 3.0 and everything was working fine (all clients appeared in the console and were reporting status).
Yesterday I had to format and reinstall Windows XP Pro (with SP2) on a client computer, add it to the domain etc.
Initially it would not show up in the console, so I stopped Automatic Updates service, deleted the C:\WINDOWS\SoftwareDistribution folder, started AUtomatic Updates service and ran following commands:

wuauclt.exe /resetauthorization
wuauclt.exe /detectnow

After this, the client appeared in the WSUS console, but it would not report status.
I tried several things, but I couldn't make it to report status to WSUS server.
Here's the log of WsusCltDiag.exe:

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.4.3790.2180 . . . . . . . . . . . PASS
                This version is SUS 1.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://leonidas:8530
                WUStatusServer = http://leonidas:8530
        UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
        Connection to server. . . . . . . . . . . . . . . . . . PASS

WinHttpDownloadFileToMemory(szURLDest, NULL, 0, NULL, NULL, NULL, &downloadBuffe
r) failed with hr=0x80190194

No Error description could be found

Press Enter to Complete

And here's the excerpt from the WindowsUpdate.log (note that I've included everything since last logon, not just after running WsusCltDiag):

2007-05-31      14:19:00+0200      1980      4e4      Service Main starts
2007-05-31      14:19:00+0200      1980      4e4      Using BatchFlushAge = 33455.
2007-05-31      14:19:00+0200      1980      4e4      Using SamplingValue = 471.
2007-05-31      14:19:00+0200      1980      4e4      Successfully loaded event namespace dictionary.
2007-05-31      14:19:00+0200      1980      4e4      Successfully loaded client event namespace descriptor.
2007-05-31      14:19:13+0200      1980      4e4      Successfully initialized local event logger. Events will be logged at C:\WINDOWS\SoftwareDistribution\ReportingEvents.log.
2007-05-31      14:19:13+0200      1980      4e4      Successfully initialized NT event logger.
2007-05-31      14:19:13+0200      1980      4e4      Successfully initialized event uploader 0.
2007-05-31      14:19:13+0200      1980      4e4      Successfully initialized event uploader 1.
2007-05-31      14:19:13+0200      1980      4e4      WU client with version 5.4.3790.2180 successfully initialized
2007-05-31      14:19:13+0200      1980      4e4      Service status is now SERVICE_RUNNING
2007-05-31      14:19:13+0200      1980      248      Successfully opened event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{785B2FF9-BB35-4351-B443-17E4C2981EE5}.bin for reading.
2007-05-31      14:19:13+0200      1920      778      Trying to make out of proc datastore active
2007-05-31      14:19:14+0200      1920      778      Out of proc datastore is now active
2007-05-31      14:19:14+0200      1980      248      PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2007-05-31      14:19:14+0200      1980      248      Failed to obtain cached cookie with hr = 80248008.
2007-05-31      14:19:14+0200      1980      248      Failed to upload events with hr = 80248008.
2007-05-31      14:19:26+0200      1980      7c0      Service received logon notification
2007-05-31      14:19:29+0200      1980      7c0      Service received connect notification
2007-05-31      14:19:58+0200      1980      4e4      start delayed initialization of WU client
2007-05-31      14:19:58+0200      1980      4e4      Client Call Recorder finished delayed initialization
2007-05-31      14:19:59+0200      1980      4e4      Setting AU scheduled install time to 2007-06-01 08:00:00
2007-05-31      14:19:59+0200      1980      4e4      AU finished delayed initialization
2007-05-31      14:24:58+0200      1920      778      Out of proc datastore is shutting down
2007-05-31      14:25:00+0200      1920      778      Out of proc datastore is now inactive
2007-05-31      14:29:13+0200      1980      558      Successfully opened event cache file at C:\WINDOWS\SoftwareDistribution\EventCache\{785B2FF9-BB35-4351-B443-17E4C2981EE5}.bin for reading.
2007-05-31      14:29:14+0200      3512       c0      Trying to make out of proc datastore active
2007-05-31      14:29:14+0200      3512       c0      Out of proc datastore is now active
2007-05-31      14:29:14+0200      1980      558      PT: Using serverID {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
2007-05-31      14:29:14+0200      1980      558      Failed to obtain cached cookie with hr = 80248008.
2007-05-31      14:29:14+0200      1980      558      Failed to upload events with hr = 80248008.

Any ideas?

Thanks in advance,

NT
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Commented:
Do you have WSUS settings on defoult Domain Policy or on some OU? If you add PC to domena again, it is in AD\Computers container... You should move him to OU where you apply WSUS settings.

Author

Commented:
Cro0707,

I moved the computer from the default 'Computers' folder to the appropriate OU where the GP is effective. Besides, all other computers in that OU work properly.

and235100,

The method mentioned in your link refers to an older version of WSUS and not 3.0, because I have different CAB-files in the mentioned directory.

Thank you anyway.
Fundamentals of JavaScript

Learn the fundamentals of the popular programming language JavaScript so that you can explore the realm of web development.

Sorry.

Are you sure that the proxy settings on that workstation are correct? (if you are using a proxy server)

Can you also verify that removing the station from AD, and putting it back doesn't help.

Author

Commented:
and235100,

The proxy settings are correct, I can access the Intranet as well as the Internet. I also tried disabling the proxy server in Internet Options just in case, but nothing. Additionally, if I try to download http://leonidas:8530/SelfUpdate/wuident.cab using IE 7.0, it works (with or without proxy).
Removing the machine from AD and adding it again didn't help, either.
Okay - of the cases I have seen - the diagnostics tool doesn't output the port number.

Checking Connection to WSUS/SUS Server
                WUServer = http://leonidas:8530
                WUStatusServer = http://leonidas:8530
        UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
        Connection to server. . . . . . . . . . . . . . . . . . PASS

I would normally expect

WUServer = http://leonidas
                WUStatusServer = http://leonidas

Can you confirm this is how you have your other XP stations reporting?

Author

Commented:
and235100,

The server is intentionally running on port 8530. All other machines on the network are configured to access WSUS on port 8530.
I was not aware that the tool does not support port 8530, I remember running it previously and it worked fine. I ran it now on a machine that works fine (reported status 5 minutes ago) and it gives me the same error, although there are no errors in WindowsUpdate.log. Maybe WSUS 3.0 handles such requests differently than previous versions?
In any case, the machine in question still does not report status.

Can you possibly setup another computer and assign it to use WSUS - and see if the same issues occur with that? I want to try and isolate this to a problem with this particualr install - or a system-wide problem when adding new stations using WSUS...

Author

Commented:
and235100,

It obviously was a matter of time (and I was a bit impatient). I removed the computer from the WSUS console and after a while, it appeared and reported status (although the diagnostic tool still does not work).
I will award you the points for your effort.
Thanks again.
Sorry that I couldn't help more - possibly version 3.0 has some bugs in it...

Thank you.
I am not sure if this will help at all but I have noticed that if you want to have ALL Clients reporting to the WSUS as well as retrieving the updates you will need the following settings in IIS ver6

In the Default website you will find the following folders.
ClientWebService
Content
ReportingWebService
SelfUpdate
SimpleAuthWebService

In the Properties/ Directory security/ Authentication and Access Control - Click Edit Button
make sure that you have "Integrated Windows Authentication" box ticked under Authentication Access Section.
By doing this I has status being passed back to WSUS IMEDIATELY I typed the wuauclt.exe /detectnow command on the clients that were showing as not having reported in to WSUS.

I hope this helps perhaps people can now comment on what the grey area on the WSUS PIE charts mean when they say "UPDATES WITH NO STATUS" just what does that mean?
Regards
miff

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial