Troubleshoot wsus client not updating

25-Oct-2019 20:38

Under IIS Manager App – Expand Server name – Sites – WSUS Administration Right click – Edit Bindings Now Assign a different Port Number (i.e.

1234 ) Once this is done, you will need to restart the Website While still in IIS Manager App – Expand Server name – Sites – WSUS Administration – Restart Website Now when you connect to WSUS, select the custom new port That should allow you now to be able to run the Cleanup and re-indexing of the DB for WSUS.

Note: During this step, your clients will not be able to connect to your WSUS instance.

Application Pools – Add Application Pool Once you have created the App Pool, we need to change the Website over to the Pool First Now our Next Step is to change the Bindings and assign a different port number to the HTTP Connection for WSUS, so that the clients are unable to scan against it, thereby freeing up the memory for us.

Once you have completed this, make sure to change the Bindings Pool back to what it was before so that the clients can now start scanning again.

As long as the correct configuration is applied in the environment, and the regular maintenance in place, you should not have any further WSUS Performance issues.

This gives the appearance of a magician’s disappearing act with computers objects.

Hopefully you should now see the client reporting correctly in the WSUS Console.

If not, temporarily stop the Windows Update Service and delete the C:\Windows\Software Distribution folder and force another Windows Update.

An important Step is missed by a lot of customers, that is configuring your WSUS App Pool Correctly.

The App Pool memory in a lot of cases is left at the Default 1.9GB of memory.

This gives the appearance of a magician’s disappearing act with computers objects.

Hopefully you should now see the client reporting correctly in the WSUS Console.

If not, temporarily stop the Windows Update Service and delete the C:\Windows\Software Distribution folder and force another Windows Update.

An important Step is missed by a lot of customers, that is configuring your WSUS App Pool Correctly.

The App Pool memory in a lot of cases is left at the Default 1.9GB of memory.

More than 75% of the time that clients have issues, it is due to cloning or imaging computers.