WSUS - Server 2019 datacenter not checking in to WSUS automatically

Question

Hi All
I have this specific Server 2019 Datacenter which is not checking into WSUS on a schedule.
WSUS policies set via GPO. All other servers are fine. Its just this one particular one that i am having issues with.
The registries have been updated OK. It is meant to check in every 8 hours.

However, if i click the "Check for updates" button locally on the server, that will check the server in.
Also, running some commands locally also checks the server in... not immediately.. but eventually.
Just not sure right now which one did it, as i ran bunch of them, including (wuauclt, usoclient, and powershell).

Then if i let it sit like this, server does not check in every 8 hours automatically. Requires manual intervention to check it in to WSUS again.

Any ideas?
Thanks
DM

Answer 1

Hi DavidMoon-1992,

Thanks for your posting on Q&A.

In order to research further, please help to share with me the policies which force the Windows Server 2019 client to check into WSUS on a schedule.

In addition, have you tried to clean up the database recently? If not, please consider cleaning the database first.

Please let me know if there are any updates about this issue.

Wish you have a nice weekend.

Regards,
Rita

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

To add to Rita's point:

Are you performing the proper WSUS maintenance including but not limited to running the Server Cleanup Wizard (SCW), declining superseded updates, running the SQL Indexing script, etc.?

https://www.ajtek.ca/wsus/how-to-setup-manage-and-maintain-wsus-part-8-wsus-server-maintenance/

It's not just running the SCW.

Are you sure you've followed the directions here:

https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly/

Yes, you've probably run the script before (or variations of it), but did you delete the computer object in the WSUS MMC Console first and run the exact client side script to get it going again? If that doesn't work, keep following the troubleshooting section below it.