Your WSUS Server currently shows that no computers are registered to receive updates.

Question

As always, this seems to be a very common issue for WSUS servers, with no real answers.
I've spent the last few weeks building 4 iterations of a Windows Server 2019 machine, to have WSUS installed.
I've used a basic WSUS installation, and I've got one client I want to connect to it.

The client is configured to connect via GPO, and this seems to be working correctly on the client side (from WindowsUpdate.log):
2021/04/28 17:15:32.2317770 6736 5372 Shared InitializeSus
2021/04/28 17:15:32.2324165 6736 5372 IdleTimer Non-AoAc machine. Aoac operations will be ignored.
2021/04/28 17:15:32.2325845 6736 5372 Agent WU client version 10.0.18362.1474
2021/04/28 17:15:32.2330721 6736 5372 Agent SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2021/04/28 17:15:32.2332181 6736 5372 Agent Base directory: C:\Windows\SoftwareDistribution
2021/04/28 17:15:32.2341575 6736 5372 Agent Datastore directory: C:\Windows\SoftwareDistribution\DataStore\DataStore.edb
2021/04/28 17:15:32.2354567 6736 5372 DataStore JetEnableMultiInstance succeeded - applicable param count: 5, applied param count: 5
2021/04/28 17:15:32.2732721 6736 5372 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
2021/04/28 17:15:32.2735604 6736 5372 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2021/04/28 17:15:32.2758815 6736 5372 Shared Network state: Connected
2021/04/28 17:15:32.3602462 6736 5372 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
2021/04/28 17:15:32.3602576 6736 5372 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2021/04/28 17:15:32.3602671 6736 5372 Shared Power status changed
2021/04/28 17:15:32.3653793 6736 5372 Agent Initializing global settings cache
2021/04/28 17:15:32.3653817 6736 5372 Agent WSUS server: http://UWM-MEM-01.uwm.local:8530
2021/04/28 17:15:32.3653834 6736 5372 Agent WSUS status server: http://UWM-MEM-01.uwm.local:8530
2021/04/28 17:15:32.3653849 6736 5372 Agent Alternate Download Server: (null)

But, no matter what I do, the WSUS server will not show that there's a computer communicating with it. It's also set to do the targeting. The GPO is successfully applied... I've done everything in accordance to the 15+ guides that I've reviewed over the past few weeks, and I'm literally just spinning in circles making no progress at all now.

It's gotten to the point where I'm stumbling into other Microsoft issues, like IIS pass-through authentication doesn't work either in the latest revision of IIS, and it just always shows an authorization error.

Please can anyone offer me some guidance on how to rectify this? It's driving me insane.

Answer 1

@Steve Y
For some reason, I left it last night and the computer finally registered - with no changes made. It shouldn't take weeks to register a device when on the same switch, with no firewalling, routing, or anything to prevent it, right?
We should wait for a while and the clients will registered to the WSUS server, about a day if there is no error occurred.

I've enabled SSL this morning, and its failing to connect again, but I suspect its just going to take a long time before reporting in again.
Perhaps you didn't enabled the SSL correctly.

According to the log you provided, the clients did try to connect to the WSUS server under 8531 not 8530. But I didn't find any error information. Perhaps the log is too short to review.

Refer to the below step to check the connection between the WSUS server and the clients:
We could open the IE on the client and connect to the WSUS server as the below URL:

https://WSUS server's FQDN:8531/selfupdate/iuident.cab  

If the connection is OK, a file will be downloaded from the WSUS server to the client.

Please refer to the below link to configure the SSL on the WSUS Server:
https://learn.microsoft.com/en-us/windows-server/administration/windows-server-update-services/deploy/2-configure-wsus#25-secure-wsus-with-the-secure-sockets-layer-protocol

Note that we have to import the certificate to all the clients which registered to the WSUS server to enable the SSL.

Hope the above will be helpful.

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

@Steve Y
In my opinion, we use the usoclient.exe command to scan for updates and download an install updates in windows 10, and windows server 2016 or newer.
Here is a related link for your reference:
https://learn.microsoft.com/en-us/archive/blogs/yongrhee/wuauclt-detectnow-in-windows-10-and-windows-server-2016

In addition, I found a related link about how to use the usoclient.exe command for your reference. Note that the link is not from MS, just for your reference.

Hope the above will be helpful.

Have a good day :)

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.