Without it, WMI sensors do not work.įor this sensor to work with Windows performance counters, make sure that the Remote Registry Windows service runs on the target computer. This is necessary because the PRTG probe service only runs with 32-bit support. This allows 32-bit applications to be run on 64-bit systems. WoW64 must be installed on target systems that run Windows Server 2016. However, WMI connections might still work.įor this sensor to work with Windows performance counters, make sure that at least Windows Server 2008 R2 is installed on the probe system (on every cluster node, if on a cluster probe). Otherwise, a connection via performance counters is not possible. If you use local credentials, make sure that the same Windows user accounts (with the same user name and password) exist on both the probe system and the target computer. Preferably, use Windows domain credentials. This sensor requires credentials for Windows systems in the settings of the parent device.

If you want to use this sensor, add it to a remote probe device. You cannot add this sensor to the hosted probe of a PRTG Hosted Monitor instance. This sensor supports the IPv6 protocol.This sensor can use a hybrid approach with Windows performance counters and WMI as fallback to query data.The sensor cannot show values above 4 GB for 64-bit processes if you use performance counters.This sensor requires WoW64 (Windows 32-bit on Windows 64-bit) for target systems that run Windows Server 2016.This sensor requires that the Remote Registry Windows service runs on the target computer.This sensor requires at least Windows Server 2008 R2 on the probe system.This sensor requires credentials for Windows systems in the settings of the parent device.

We recommend that you use no more than 200 sensors of this sensor type on each probe.

This sensor has a high performance impact.

For a detailed list and descriptions of the channels that this sensor can show, see section Channel List.

Where is windows 10 process monitor