WSUS Downstream server showing 0% Installed/Not Applicable Percentage on upstream

Question

Hello all, I am having an issue with one of my WSUS downstream servers not reporting the correct Installed/Not Applicable Percentage on my upstream server. I have 4 total downstream servers, and 3 are reporting correctly. All the servers are running server 2019, and when I do a sync from the downstream, I do see the Last Synchronization date updating, however the percentage stays at 0. On the downstream server that is having the issue, computers are reporting in correctly, it just seems like that info is not being relayed to the upstream server. I have compared all the IIS settings to my other servers and they are all the same, so I dont think that is the issue. The downstream is also getting all the approvals from the upstream, so the communication between the two seems to be working. Any thoughts on what might be happening with this?

Answer 1

Hi,

I'd be happy to help you out with your question. Sorry for the inconvenience caused.

To resolve this issue please try following steps :-

First, check the event logs on both the upstream and downstream servers for any errors or warnings related to WSUS or Windows Update. This will help you identify the root cause of the issue.

Next, restart the WSUS service on both the upstream and downstream servers to see if that resolves the problem.

If that doesn't work, try resetting the downstream server's update status by running the following command on the downstream server: "wuauclt /resetauthorization /detectnow". This should force the downstream server to re-register with the upstream server and report its update status.

Also, check the firewall settings on both the upstream and downstream servers to make sure that the necessary ports are open for WSUS communication.

Make sure that the downstream server is pointing to the correct upstream server in its WSUS configuration.

Finally, if none of the above solutions work, you may need to remove the downstream server from WSUS and re-add it as a new downstream server. This will require re-approving updates and may take some time to complete, but it should reset the server's status and hopefully resolve the issue.

If you have any other questions or need assistance with anything, please don't hesitate to let me know. I'm here to help.

If the reply was helpful, please don’t forget to upvote or accept as answer, thank you.