Windows Clients are not registering to the domain's WSUS

Sometimes there is a problem with Windows not reporting to the WSUS-Service. This is a quick fix that I found working.

First start a administrative powershell and stop the Update-Service and the BITS-Service on the Client

 PS C:\> net stop bits  
 PS C:\> net stop wuauserv  

Now have a look at the corresponding registry object

 Get-ItemProperty HKLM:\Software\Policies\Microsoft\Windows\WindowsUpdate  

In my case, the entries "WUServer" and "WUStatusServer" were set to update.microsoft.com. We can fix that by running

 PS C:\> Set-ItemProperty HKLM:\Software\Policies\Microsoft\Windows\WindowsUpdate -Name "WUServer" -Value "http://wsus.domain.tld:8530"  
 PS C:\> Set-ItemProperty HKLM:\Software\Policies\Microsoft\Windows\WindowsUpdate -Name "WUStatusServer" -Value "http://wsus.domain.tld:8530"  

To check if the keys are set, run

 PS C:\> Get-ItemProperty HKLM:\Software\Policies\Microsoft\Windows\WindowsUpdate -Name "WUServer","WUStatusServer"  

If the keys are now valid, we can start the BITS and Wuauserv again.

 PS C:\> net start bits  
 PS C:\> net start wuauserv  

To register the client to WSUS, run the following command.

 PS C:\> wuauclt /detectnow /reportnow /updatenow  

The client should now show up in the WSUS.

Feel free to comment and / or suggest a topic.