Question : WSUS Not Yet Reported

I have multiple Windows Server 2003 R2 Enterprise SP2 servers setup with WSUS.  The primary server provides updates for buildings in our organization that do not have a server on site.  The buildings with servers are downstream servers from this main site.  All the buildings are connected with a 100 mb fiber WAN.

Several of the machines will not report back status to the WSUS server.  I found that I needed to manually create the selfupdate virtual directory.  After doing this, allowing anonymous access, I restart the Automatic Update service on a problem machine and get the following result in WindowsUpdate.log.  Any ideas why so many machines are not checking in properly?

Code Snippet:

1: 2: 3: 4: 5: 6: 7: 8: 9: 10: 11: 12: 13: 14: 15: 16: 17: 18: 19: 20: 21: 22: 23: 24: 25: 26: 27: 28: 29: 30: 31: 32: 33: 34: 35: 36: 37: 38: 39: 40: 41: 42: 43:

2008-12-19 14:19:44:775 1112 c40 Agent *********** Agent: Initializing Windows Update Agent *********** 2008-12-19 14:19:44:775 1112 c40 Agent *********** Agent: Initializing global settings cache *********** 2008-12-19 14:19:44:775 1112 c40 Agent * WSUS server: http://adbs01.superior.k12.wi.us 2008-12-19 14:19:44:775 1112 c40 Agent * WSUS status server: http://adbs01.superior.k12.wi.us 2008-12-19 14:19:44:775 1112 c40 Agent * Target group: BR 2008-12-19 14:19:44:775 1112 c40 Agent * Windows Update access disabled: No 2008-12-19 14:19:44:775 1112 c40 DnldMgr Download manager restoring 0 downloads 2008-12-19 14:19:44:775 1112 c40 AU ########### AU: Initializing Automatic Updates ########### 2008-12-19 14:19:44:775 1112 c40 AU # WSUS server: http://adbs01.superior.k12.wi.us 2008-12-19 14:19:44:775 1112 c40 AU # Detection frequency: 20 2008-12-19 14:19:44:775 1112 c40 AU # Target group: BR 2008-12-19 14:19:44:775 1112 c40 AU # Approval type: Scheduled (Policy) 2008-12-19 14:19:44:775 1112 c40 AU # Scheduled install day/time: Every day at 3:00 2008-12-19 14:19:44:775 1112 c40 AU # Auto-install minor updates: Yes (Policy) 2008-12-19 14:19:44:775 1112 c40 AU # Will interact with non-admins (Non-admins are elevated) 2008-12-19 14:19:44:775 1112 c40 AU Setting AU scheduled install time to 2008-12-20 09:00:00 2008-12-19 14:19:44:775 1112 c40 AU AU finished delayed initialization 2008-12-19 14:19:45:103 1112 c40 Report *********** Report: Initializing static reporting data *********** 2008-12-19 14:19:45:103 1112 c40 Report * OS Version = 5.1.2600.3.0.65792 2008-12-19 14:19:45:150 1112 c40 Report * Computer Brand = Hewlett-Packard 2008-12-19 14:19:45:150 1112 c40 Report * Computer Model = HP Compaq dc7800 Small Form Factor 2008-12-19 14:19:45:150 1112 c40 Report * Bios Revision = 786F1 v01.04 2008-12-19 14:19:45:150 1112 c40 Report * Bios Name = Default System BIOS 2008-12-19 14:19:45:150 1112 c40 Report * Bios Release Date = 2007-07-18T00:00:00 2008-12-19 14:19:45:150 1112 c40 Report * Locale ID = 1033 2008-12-19 14:19:45:696 1112 b74 Report Uploading 1 events using cached cookie, reporting URL = http://adbs01.superior.k12.wi.us/ReportingWebService/ReportingWebService.asmx 2008-12-19 14:19:48:037 1112 b74 PT WARNING: ReportEventBatch failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200 2008-12-19 14:19:48:037 1112 b74 PT WARNING: SOAP Fault: 0x00012c 2008-12-19 14:19:48:037 1112 b74 PT WARNING: faultstring:Fault occurred 2008-12-19 14:19:48:037 1112 b74 PT WARNING: ErrorCode:ConfigChanged(2) 2008-12-19 14:19:48:037 1112 b74 PT WARNING: Message:(null) 2008-12-19 14:19:48:037 1112 b74 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/ReportEventBatch" 2008-12-19 14:19:48:037 1112 b74 PT WARNING: ID:42df7efe-5217-49b7-aea5-58eb5d4a3630 2008-12-19 14:19:48:037 1112 b74 Report WARNING: Reporter failed to upload events with hr = 8024400d. 2008-12-19 14:19:48:068 1112 b74 Report Uploading 1 events using cached cookie, reporting URL = http://adbs01.superior.k12.wi.us/ReportingWebService/ReportingWebService.asmx 2008-12-19 14:19:48:084 1112 b74 PT WARNING: ReportEventBatch failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200 2008-12-19 14:19:48:084 1112 b74 PT WARNING: SOAP Fault: 0x00012c 2008-12-19 14:19:48:084 1112 b74 PT WARNING: faultstring:Fault occurred 2008-12-19 14:19:48:084 1112 b74 PT WARNING: ErrorCode:ConfigChanged(2) 2008-12-19 14:19:48:084 1112 b74 PT WARNING: Message:(null) 2008-12-19 14:19:48:084 1112 b74 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/ReportEventBatch" 2008-12-19 14:19:48:084 1112 b74 PT WARNING: ID:bafd5705-418c-4bdc-92e5-12365ddc5537 2008-12-19 14:19:48:084 1112 b74 Report WARNING: Reporter failed to upload events with hr = 8024400d.

Open in New Window Select All

Answer : WSUS Not Yet Reported

1.Take a look at the WSUS Client Diagnostics Tool:
http://download.microsoft.com/download/9/7/6/976d1084-d2fd-45a1-8c27-a467c768d8ef/WSUS%20Client%20Diagnostic%20Tool.EXE

Instructions on use are here:
http://download.microsoft.com/download/e/4/b/e4bc4153-be1f-460f-800e-69c6a1857d68/readme.htm

2.First place to check on client: C:\Windows\WindowsUpdate.log

Check your client and server using the tools provided by MS: http://www.microsoft.com/windowsserversystem/updateservices/downloads/default.mspx (Server Diagnostic Tool and Client Diagnostic Tool).

Check your IIS is healthy: http://www.microsoft.com/downloads/details.aspx?FamilyID=9bfa49bc-376b-4a54-95aa-73c9156706e7&DisplayLang=en
Also check your C:\WINNT\WindowsUpdate.log file on your client stations, it should provide you with some helpful info

3.Try this if this doesn't help you then post the event errors and update log.

. At the client, shutdown Automatic Updates service.
. At the client, use bitsadmin to check the BITS queue, and flush it if there's anything there.
. At the client, make a backup of the %windir%\SoftwareDistribution folder and all subfolders and the %windir%\WindowsUpdate.log file.
. At the client, purge the following folders of all content:
       %windir%\SoftwareDistribution\Datastore\Logs\edb*.*
        %windir%\SoftwareDistribution\Datastore\DataStore.edb
        %windir%\SoftwareDistribution\Download
        %windir%\SoftwareDistribution\EventCache
and delete the following files:
        %windir%\SoftwareDistribution\ReportingEvents.log
        %windir%\WindowsUpdate.log

. At the client, delete the three values in the registry key at:
    HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate
This is necessary to force the creation of a new SusClientId, which will force the creation of an all new database record (thus avoiding any potential issues with corruption or bad data in the original record, that may or may not actually be physically present in the database).
. At the server, delete pc176.moxy.no from the WSUS server, completely.
. At the client, restart the Automatic Updates service, and monitor the WindowsUpdate.log and/or ReportingEvents.log for detection/download activity for updates. Following the detection and the uploading of events to the ReportingWebService, review the status as reported by the WSUS server, to determine if the new instance of this client appears and is reported correctly with regard to installed and needed updates

4.Troubleshooting Client Targeting
http://wsus.editme.com/TroubleshootingClientTargeting