Reproduced WSUS client Troubleshooting--using WSUS clients tools

1-1
1. Checking clients with WSUS client tools software

: http://www.microsoft.com/en-us/download/details.aspx?id=30827
There are three software checks:
wuserver=http://10.10.10.5:8530
-------(WSUS server address)
wustatusserver=http://10.10.10.5:8530-----(WSUS server address)
(1) Usewuserver is enable
---------Pass
(2) Onnection to server
----------Pass
(3) SelfUpdate Folfer is present
----------Pass
2-1 If all three items show pass and the client still does not have patch updates
Example: If the first two items pass and the error 80072efd is displayed
Workaround: Use Proxycfg-p proxyservername:port (proxyservername:port WSUS server address and port) on the client

2-1
1. Stop automatic Updates service and BITS service, run at the command prompt:
net stop Wuauserv
net stop bits
2. Delete the%windir%\softwaredistribution directory
3. Start the automatic Updates service and BITS service, and when these 2 services do not start, they will automatically create softwaredistribution and related sub-files.
Run at the command prompt:
net start wuauserv
net start bits
4. When the%windir%\softwaredistribution directory has been created, let the client immediately connect to the domain WSUS server.
Wuauclt.exe/resetauthorization/detectnow
5. After 15 minutes, check to see if the client is checking for the required updates.
If the problem persists, on the WSUS client, do the following:

1. Confirm Background Intelligent Transfer service starts
2. Run the following command to rename the Catroot2 folder
net stop cryptsvc
ren%systemroot%\system32\catroot2 oldcatroot2
net start cryptsvc

If the above operation is still unresolved, please copy the WindowsUpdate.log log file to the system disk Windows folder for professional analysis. (Note: Make sure that the WSUS server is not a problem and that other PCs can update properly.) ）

PS: The first few days by this WSUS client can not receive the update prompt to make a quick crash, WSUS is no problem, the other several machines also received the update prompt, finally emperor not negative, found this method. Finally can receive the prompt!! The two machine systems are Windows Server 2003.

Reprint Address: http://blog.csdn.net/flyuniverse_shell/article/details/7492213

[Reprint]wsus Client Troubleshooting-Using WSUS Client tools