This article applies as of PRTG 22
Getting data for System Information tables
To show data in the tables on the System Information tab of a device, PRTG requests the data on this device using protocols like Windows Management Instrumentation (WMI) and Simple Network Monitoring Protocol (SNMP), depending on the particular information request.
Basically, this works with the same technologies as for sensors that you use for monitoring. You must ensure that the necessary protocols are enabled and work on the device for which you want to get system information.
Prerequisites for System Information data
If you already monitor a device with WMI and SNMP sensors, it is most likely that PRTG automatically fills the tables on the System Information tab without the need for you to take action. Just click the System Information tab of a device and you will see the retrieved information for this device.
Meet the following requirements to show all available system information for a device:
- Provide valid credentials for the target system in the device settings or inherit the Windows and SNMP credentials from a parent group or parent probe.
- Enable the Remote Registry Windows service on the target computer, for example, via services.msc, and set its start type to automatic. If this service is enabled, you get more information in the Software table.
- Enable the Remote Procedure Call (RPC) Windows service on the target system, for example, via services.msc, and set its start type to automatic.
- Configure WMI on the probe system and target system to get data for the system information tables System, Hardware, Software, Users, Services, and Processes. For more details about WMI, see:
- Configure SNMP to get information for the System, Hardware, Software, and Processes tables from systems that do not run Windows. For more information about SNMP, see:
You will also get information data if you do not fulfill all requirements (for example, if you configure only WMI but not SNMP). However, not all information will be available and some tables may remain empty.
To retrieve information for the Software table, PRTG uses Uninstall registry keys, so the displayed software might differ from the software that the Windows computer shows under Programs and Features. If the target device is the probe system (local or remote), do not use the DNS name as the address of this device but localhost, 127.0.0.1 (IPv4), or ::1 (IPv6). Otherwise, you may get an error in the Software table.
Note: The System Information feature is enabled by default. To retrieve the data, PRTG automatically uses Credentials for Windows Systems and Credentials for SNMP Devices as defined in the device settings or as inherited from a parent object like the root group. Consider this when you monitor devices outside the local network, particularly when using SNMP v1 or SNMP v2c that do not provide encryption.
Error messages for System Information
You may see one of the following messages if you do not meet the requirements. If you get an error message that is not listed below, refer to the general introductions to WMI and SNMP.
Error message | Explanation and troubleshooting |
Please wait. Collecting system information… | A table shows this message until PRTG can provide the according data. This may take up to a few minutes, depending on the target system and the used technology (WMI takes longer than SNMP). Usually, the table soon shows system information. |
RPC Server not accessible. Port Error (Socket Error # 10061 Connection Refused.) | Make sure that you provide the correct credentials for the target system in the device settings and that the RPC Windows service is running. Also check your WMI configuration (see My WMI sensors don't work. What can I do?). |
The sensor could not connect to the Remote Registry Windows service of the target system. To resolve this issue, make sure that the service is running. Also make sure that you entered correct Credentials for Windows Systems in the device settings. For more information, see https://kb.paessler.com/en/topic/67824. (code: PE255) | Make sure that you provide the correct credentials for the target system in the device settings and enable the Remote Registry Windows service (see section Prerequisites for System Information Data). |
No Response (check: […]) (SNMP error # -2003) | Check your SNMP configuration. See My SNMP sensors don’t work. What can I do? for basic requirements. |
Socket Error # 11001 Host not found. | The device is not available. Resume the device and check its IP address or DNS name in the device settings. |
80070005: Access is denied. | Make sure that you provide the correct credentials for the target systemin the device settings. |
Metascan Timeout. | This is a WMI timeout and occurs if PRTG has not been able to establish a WMI connection for several minutes. Check your WMI configuration and particularly consider the WMI settings on the target system. |
80041003: The current user does not have permission to perform the action. | Check the access rights of the user account with which you are running the PRTG probe service. We recommend that you run the PRTG probe service with admin permissions. |
Could not validate sensor preconditions. | Make sure that you provide the correct credentials for the target system in the device settings. |
80041001: The call failed. | Check your WMI configuration and also see this article in the Microsoft Knowledge Base. |
800706BA: The RPC server is unavailable | Restart the target device and (re-)run Windows Update. See this Microsoft article for details. |
Error: Could not access in 32 bit Registry –or– Error: Could not access in 64 bit Registry | If the target device is the probe system, use localhost, 127.0.0.1 (IPv4), or ::1 (IPv6) as address for the target device instead of the DNS name. |
More
Add comment