Hello Kevin,
thank you for your KB-Post.
I'll stick to English since we'd like anyone who stumbles across this on the KB when facing a similar issue can also make use of this information.
For best results please make sure to use FQDN addresses instead of IP Addresses.
The Windows Updates Status (Powershell) sensor uses powershell-remoting. We can tell from experience that this works a lot better when the probe and target system are part of the same Active Directory domain. But if you get Powershell Remoting working without it, the sensor should work as well.
Please review the following related troubleshooting guides:
You can also troubleshoot the sensor outside of PRTG running the following command line:
| PS C:\Program Files (x86)\PRTG Network Monitor\Sensor System> .\LastWindowsUpdateSensor.exe -host='SERVERFQDN' -user='DOMAIN\ACCOUNT' -pass='PASSWORD' |
You can test different account and password combinations, please note that the username/password should preferably the same on both systems for best results. Once you get the sensor working in command line you can test the same credentials in PRTG, they should work. Within PRTG the credentials should be defined on the Credentials for Windows Systems within the Device's Settings.
Please review the sensor's remarks for a complete list of remarks that need to be taken into consideration.
In some cases the impersonation performed by the sensor (for the credentials) may not work, in that case you might want to configure the PRTG Probe Service to run with an account different that local_system which is only valid locally.
Best Regards,
Luciano Lingnau [Paessler Support]
Add comment