What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

Der angegebene Host ist unbekannt | Windows Update Status

Votes:

0

Your Vote:

Up

Down

Hallo,

der Windows Update Status-Sensor läuft eigentlich gut, nur leider gibt es grade bei unseren Hyper-Vs Probleme bzw. keine Daten zurück. Es handelt sich dabei um einem physikalischem Windows 2012 R2 (nicht in der Domäne). Angesteurt wird dieser via IP-Adresse. .NET Framework 4.0 oder höher ist installiert, Remote Powershell ist zugelassen. Credentials sind korrekt.

Alle anderen Sensoren auf dem Gerät laufen (WMI's).

Muss der Server in der Domäne sein? Der PRTG Server selbst ist auch nicht in der Domäne.

Viele Grüße

hyper-v powershell windows-2012-r2 windowsupdate wsus

Created on Oct 12, 2016 10:30:17 AM by  KevinDreifke (0) 1



1 Reply

Votes:

0

Your Vote:

Up

Down

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]

Created on Oct 14, 2016 7:55:12 AM by  Luciano Lingnau [Paessler]

Last change on Oct 14, 2016 7:59:34 AM by  Luciano Lingnau [Paessler]



Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.