Knowledge Base FAQ Item #7000010

Q7000010: I'm having problems monitoring processes on a remote Windows server. How can I troubleshoot?

ActiveXperts uses WMI (Windows Management Instrumentation) to collect data about (remote) Windows machines. WMI is part of Windows operating systems and installed by default. First check out the following:

WMI can use WinRM (preferred), or DCOM (legacy). In ActiveXperts, the WMI operation mode can be set per server. By default, the global WMI operation mode is used; see Tools->Options->{Windows Machines} in the Manager application.

Ensure that Windows WMI services are running on the monitoring server and the monitored server, and that firewall settings do not prevent you from accessing the remote computer via WMI.

 

Troubelshoot Process monitoring using WMI/WinRM

Run the following Powershell command to query Process usage using WMI through WinRM:

Get-WSManInstance -ComputerName computername -Enumerate -ResourceURI wmicimv2/* -Filter "SELECT * FROM Win32_PerfRawData_PerfProc_Process" | Select-Object Name,HandleCount

or (with alternate credentials):

# Prompt to enter the username and password
$objCred = Get-Credential 
# Call Get-WSManInstance
Get-WSManInstance -ComputerName computername -Credential $objCred -Enumerate -ResourceURI wmicimv2/* -Filter "SELECT * FROM Win32_PerfRawData_PerfProc_Process" | Select-Object Name,HandleCount

To verify WMI access through WinRM, see FAQ #Q7260015

 

Troubelshoot Process monitoring using WMI/DCOM

Run the following command to query Process usage using WMI through DCOM:

WMIC /node:computername PATH Win32_PerfRawData_PerfProc_Process GET Name, HandleCount

or (with alternate credentials):

WMIC /node:computername /user:user /password:password PATH Win32_PerfRawData_PerfProc_Process GET Name, HandleCount 

To verify WMI access through DCOM, see FAQ #Q7250015

(viewed: 1870)