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.EXEInstructions on use are here:
http://download.microsoft.com/download/e/4/b/e4bc4153-be1f-460f-800e-69c6a1857d68/readme.htm2.First place to check on client: C:\Windows\WindowsUpdate.l
og
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=enAlso 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%\SoftwareDistribut
ion folder and all subfolders and the %windir%\WindowsUpdate.log
file.
. At the client, purge the following folders of all content:
%windir%\SoftwareDistribut
ion\Datast
ore\Logs\e
db*.*
%windir%\SoftwareDistribut
ion\Datast
ore\DataSt
ore.edb
%windir%\SoftwareDistribut
ion\Downlo
ad
%windir%\SoftwareDistribut
ion\EventC
ache
and delete the following files:
%windir%\SoftwareDistribut
ion\Report
ingEvents.
log
%windir%\WindowsUpdate.log
. At the client, delete the three values in the registry key at:
HKLM\Software\Microsoft\Wi
ndows\Curr
entVersion
\WindowsUp
date
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
