Troubleshooting WSUS

Clients disappearing from WSUS Console

Client computers registered in the WSUS console appeared to disappear / overwrite each other. Research revealed this was related to the fact the OS was imaged and the servers had an identical “SusClientID” registry key entries.

To resolve this issue, perform the following steps

  • Delete the SusClientId registry key

reg delete “HKLM\Software\Microsoft\Windows\CurrentVersion\WindowsUpdate” /v SusClientId /f

  • Restart the “Windows Update” service

net stop wuauserv
net start wuauserv

  • Reset the WSUS authorization. From a command line enter the following command

wuauclt /resetauthorization /detectnow

Automatic Update client unable communicate with WSUS Server – Error 80072ee2

Several computers (all running Server 2008) failed to communicate with the internal WSUS server. The servers were not experiencing any networking problems and there was no firewall blocking traffic. Checking the C:\Windows\WindowsUpdate.log revealed the following error message.

WARNING: SendRequest failed with hr = 80072ee2. Proxy List used: <>

Researching the issue revealed that Window Update does NOT rely on Internet Explorer’s Proxy server settings (which in this instance were blank) but rather the WinHTTP service. This service is configured via netsh.

  • Run “netsh winhttp show proxy” to show the whether WinHTTP proxy is configured

  • Run “netsh winhttp reset proxy” to connect to Internet directly without using any kind of proxy server.
  • Force Update detection by running “wuauclt /detectnow” from a command prompt

Checking the WindowsUpdate.log file again, browse to the end of the log file should start logging entries

2012-02-22    14:17:54:295     780    d5c    AU    Triggering AU detection through DetectNow API

2012-02-22    14:17:54:295     780    d5c    AU    Triggering Online detection (non-interactive)

2012-02-22    14:17:54:295     780    1fd4    AU    #############

2012-02-22    14:17:54:295     780    1fd4    AU    ## START ## AU: Search for updates

2012-02-22    14:17:54:295     780    1fd4    AU    #########

Check the WSUS console after a period of time will hopefully reveal the client server is now able to communicate successfully.


One thought on “Troubleshooting WSUS

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s