Link to home
Start Free TrialLog in
Avatar of RhoSysAdmin
RhoSysAdminFlag for United States of America

asked on

ALL of our WSUS clients have failed to report their status in more than 30 days

We have WSUS 3.0 sp1 running on a W2K19 server that has run reliably for over a year.  We discovered recently that it appears NONE of our WSUS clients have reported their status in more than 30 days.  


The event that coincides with this is a reboot after the installation of some Microsoft updates.  During the install of those updates, one of the W2K19 CU failed to install. When reviewing the "Last Status Report" timestamps in the WSUS Admin Console, we haven't seen any since the time of the WSUS server reboot.


I've been working through the steps in this article but haven't found anything out of sorts yet. The last thing for us to try is the "wsusutil.exe reset" command.  We wanted to check with the experts to see if there are any other things to check that may provide better feedback as to what the issue could be before we try something that's not going to tell us when it's done or what it found.


Any advice is greatly appreciated!  

Avatar of Darrell Porter
Darrell Porter
Flag of United States of America image

Any errors in the Windows event logs?
Is the Windows firewall enabled on the server?  If so, did the patch somehow change the firewall rules?
Are the client systems getting any errors in the Windows event logs related to this issue?
Has it been tested to determine if the clients can ping or otherwise access the WSUS server outside the environment without VPN active?
Which of the steps in the referenced article have you tried?
Is it possible that client updates fouled the client WSUS configuration?
Avatar of RhoSysAdmin

ASKER

I've done the WSUS reset on a few clients and removed them from the WSUS Admin console.  They re-appeared in short order (in the correct WSUS client-side group) and have yet to report a status 24 hours later.

I've confirmed the firewall ports are open and IIS is working (testing the two url's mentioned in the article).
I've confirmed DNS is correct and working.
I've confirmed the test clients are using WSUS :
PS C:\Windows\System32> $(New-Object -ComObject "Microsoft.Update.ServiceManager").Services | Select-Object Name, IsDefaultAUService

Name                          IsDefaultAUService
----                          ------------------
Windows Server Update Service               True
Windows Update                             False

Open in new window


I start the "wsusutil reset" yesterday.  I have no way of knowing if it still has work to do.  But there are no status updates yet after all the checks I did yesterday.

I've yet to find an event error that hasn't appeared intermittently before this issue started.  
I ran Get-WindowsUpdateLog on a couple of clients that I had reset, and I'm seeing the same thing on each :
2021/12/10 17:26:58.5522095 2400  5148  Misc            Got WSUS Reporting URL: http://wsus1:8530/ReportingWebService/ReportingWebService.asmx""
2021/12/10 17:26:58.5524049 2400  5148  IdleTimer       WU operation (CLegacyEventUploader::HandleEvents) started; operation # 295; does use network; is at background priority
2021/12/10 17:26:58.5524561 2400  5148  WebServices     Auto proxy settings for this web service call.
2021/12/10 17:26:58.5601689 2400  5148  WebServices     WS error: The body of the received message contained a fault.

Open in new window

So when I look on the server, I'm seeing this error repeatedly :
Log Name:      Application
Source:        Windows Server Update Services
Date:          12/10/2021 3:06:29 AM
Event ID:      12002
Task Category: 9
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      WSUS1.ms.rhoworld.com
Description:
The Reporting Web Service is not working.

Open in new window


I found this discussion and updated the permissions for %windir%\temp and as well as the .NET directory listed.  I'll restart the server once the "Server Cleanup Wizard" completes.

Let me know if we should be doing something different.

Permissions changes and run of "Server Cleanup Wizard" failed to fix my issue.  I'm still seeing error 12002.

Where do I go from here?  I really don't want to do a re-do.
ASKER CERTIFIED SOLUTION
Avatar of RhoSysAdmin
RhoSysAdmin
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial