Sbs 2016 wsus not updating clients
One of the first steps you will need to take during the initial configuration of a WSUS Server is to establish communication between WSUS Server and clients.As clients (endpoints) we assume that they can be either Windows clients or Windows Servers.I setup a WSUS server in a test lab and the results of client machines registering themselves with the WSUS server were flaky; especially if they weren’t on the same domain as the WSUS server.One of my cloned machines was having trouble until I changed the SID with New SID from Microsoft.After you set the switch to Enabled, type the WSUS Server address in the two fields like as shown in the figure below.Note: If the Configure Automatic Updates policy is disabled, then this policy is not applicable.The others didn’t appear to have any duplicate SID problems but having them appear in the WSUS administration webpage was still a challenge.
Next, we will go through the individual settings for scheduling updates, configuring alerts, etc.Root of his cause was the same, WSUS was pointing the Windows Update back to itself thus causing the error and apparent network connection issues.(Duh – Windows Update couldn’t find Microsoft Update Servers in my systems! Remove the invalid entry in the registry for the mis-pointing URL reference.These are the two most important policies for WSUS Server.
If you encounter a problem when setting it up initially, then take a look at these policies first.
Obviously if WSUS isn’t running on your server, it’s not going to have it.