Follow my guide from the top to the bottom.... Even if you think you have done the steps already.
https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly/
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi.
I am currently encountering the following problem with the title of this article, and have been investigating various issues, but have not made any progress.
We are currently encountering the following problem and have been investigating it in various ways, but have not made any progress.
■Background
We have been unable to perform Windows Update on a WSUS client (Windows Server) since some time ago, and when we checked the status report of the client, we found that the client's status was not being updated.
We found that the client's status reports were not being properly sent to the WSUS server.
■Configuration
WSUS Server: WindowsServer2012R2
WSUS Client: WindowsServer2016
Client specifies WSUS server as the destination for Windows Update.
*Some clients and servers are on the same segment (no FW in between), and some are on different segments (with FW in between).
■What we have checked and tried
We have tried various things based on information from forums and information found on the Internet, but there has been no improvement.
Check the logs and status on the client side to confirm that communication between the server and the client is normal.
→Check WindowsUpdate.log and ReportEvents.log, and check the connection status using netstat.
Delete the target client on the WSUS server.
Reset terminal information on the client side + delete the target client on the WSUS server
Execute a command in PowerShell to force a report (Reference: https://www.tksoft.work/archives/3627#toc4)
Restart the WSUS server.
Thank you for your cooperation.
Follow my guide from the top to the bottom.... Even if you think you have done the steps already.
https://www.ajtek.ca/wsus/client-machines-not-reporting-to-wsus-properly/
Hello there,
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.?
The complete guide to WSUS and Configuration Manager SUP maintenance https://learn.microsoft.com/en-US/troubleshoot/mem/configmgr/wsus-maintenance-guide
Ensure IP address between the machine and WSUS were the same.
Check HKEYLM\Software\Policies\Microsoft\Windows\Windows Update\ and ensure WUServ and WuStatusServer point to the correct server:port.
The below thread discusses the same issue and you can try out some troubleshooting steps from this and see if that helps you to sort the Issue.
https://learn.microsoft.com/en-us/answers/questions/362781/wsus-does-not-receive-status-reports-from-clients.html
https://learn.microsoft.com/en-us/answers/questions/317072/windows-10-clients-stops-reporting-to-wsus-console.html
------------------------------------------------------------------------------------------------------------------------------------------------
--If the reply is helpful, please Upvote and Accept it as an answer–
Thank you, AJTek-Adam-J-Marshall.
The server registry for the relevant WSUS client contained the following two items.
HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SusClientId
HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SusClientIDValidation
I have two questions here.
The status report has stopped reporting all of a sudden. Do you have any information as to the cause?
Does deleting the above two registry entries affect the server behavior of the WSUS client?
Thank you, LimitlessTechnology-0326.
This WSUS server was not created by me, but I took over its operation.
Therefore, maintenance may be inadequate.
I will read the link.
The page I linked to has the information you're asking including a detailed run through of the client side script, what it does, why you should do it (answering your questions about those 2 registry keys), and also, as LimitLessTechnology-0326 also mentions, the very last troubleshooting step is that it's your actual WSUS server due to lack of proper maintenance.