Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Windows Update Monitoring Inconsistency

Hello all,

I am new to SolarWinds and have been tasked with getting SAM up am running on an already built environment. I am running into an issue with the Windows Update Monitoring application. Specifically, the "Machine restart status after installing Windows Updates" application. When viewing the data on my SAM dashboard, it shows that none of my servers require a reboot. They report back with a "0" for the Statistic status and show up. But I know this to be incorrect as I have a handful of servers which are currently pending a reboot. The kicker is when I run the script which is included in the "machine restart status after installing Windows Updates" on one of the target servers which requires a reboot, the script works properly and generates a "1" for the Statistic status.

SolarWinds is installed on a Server 2016 Standard machine and pointed to a SQL cluster. I manage servers ranging from 2008 R2 to 2016. I am on a standalone domain with no Internet connection. I made sure the servers meet the requirements for PowerShell and .net as well as are remote enabled. I have tried using different accounts for the application as well as looking through logs but I don't see any glaring issues. But then again, I am quite green to the SolarWinds world. Please let me know if there is any other data that would be helpful.

Thank you!

Find more posts tagged with

Accepted answers

networkguy101

Well, this doesn't really provide insight to the issue but I changed the option to have the script run locally and it seems to be working now. Don't know why or how but its up and running for now. I will mark this as answered.

All comments

wesgray

Look for an option in the monitor itself to run script on "remote host"

networkguy101

Thank you for your reply. I changed the option to the Remote Host but am now receiving a PowerShell script error which may be pointing to a TrustedHost list. Im going to dig in deeper so see if I can figure that one out.

networkguy101

After some troubleshooting, I still cannot figure out what the issue is. I get the following error when using the "remote host" option:

"PowerShell script error. Connecting to remote server XXX failed with the following error message: The WinRm client cannot process the request. Default authenitcation may be used with an IP address under the following contitions: the transport is HTTPS or the destination is in the TrustedHosts list, and explicit credentials are provided. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. For more information on how to set TurstedHosts run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting help topic."

I added both servers to each others trusted hosts list. I tried adding them with the FQDN and IP but it didnt make a difference. Any ideas?

networkguy101