Q. Is there a way to test a WMI probe from a command prompt?

A. Yes. You need to first determine the command that you need to use. The easiest way to do this is to enable detailed logging for "Command-Line Probes & Notifiers" using the Help -> Diagnostics -> Detailed Logs window, filtering on the IP address of a device using the probe. You will see this entry added to the server debug log:

  • 15:17:27 Toggled command-line probe/notifier debug option on.

In this example, I enabled logging for the WMI - CPU Utilization probe. When you reprobe the device, the debug log will contain the actual command that is sent:

  • 15:17:57 XCmdLine::OpenForProbe -- Path: ; Cmd: "C:\Windows\system32\cscript.exe" /nologo cpu_util.vbs; Arg: -h -u -p -w 80 -c 90
    15:17:57 XCmdLine::OpenForProbe -- Established path: "C:\Windows\system32\cscript.exe" "/nologo" "cpu_util.vbs".
    15:17:57 XCmdLine::SendProbe -- Sending probe: "C:\Windows\system32\cscript.exe" "/nologo" "cpu_util.vbs" -h -u -p -w 80 -c 90
    15:17:57 XCmdLine::OpenForProbe -- Probe sent.

The relevant line here is this:

  • "C:\Windows\system32\cscript.exe" "/nologo" "cpu_util.vbs" -h -u -p -w 80 -c 90

Simply open a command prompt on Windows, then navigate to the relevant WMI probe folder in the <IM Settings location>\Tools folder, and copy/paste the command from the debug window (see second note below):

  • "<IM Settings location>\Tools\com.dartware.wmi.cpu_uti
    lization> "C:\Windows\system32\cscript.exe" "/nologo" "cpu_util.vbs" -h -u -p -w 80 -c 90

This is the output from the command:

  • \{PercentProcessor0:=0.0,PercentProcessor1:=0.0,reason:="Processor Time is below
    80%"}\B5\WMI CPU Utilization\P0\
    \4\Processor 0:\0\ $PercentProcessor0 %
    \4\Processor 1:\0\ $PercentProcessor1 %


1. Adding a -v to the end of the command will produce more verbose output.

2. The path to the <IM Settings location> varies by Windows platform. See the User Guide, Reference section, Files and Folders for the exact path to substitute for this placeholder

Authentication isn't entered with the command, and so isn't displayed in the user session or in the log.

If the local machine's WMI is being queried, just enter a space, then hit return.

For a remote system, enter user<space>password, then return.