WMI Condition


Starts a task when a WQL (WMI Query Language) query executed on the agent machine returns true or more than 0 rows. Queries built using WQL are used to manage and control the WMI Service.   

WMI (Windows Management Instrumentation) is a technology built into Windows operating systems that provide direct access to managed resources on a system and allows components and devices in enterprise environments (i.e. hard disks, network/video adapters, BIOS, CPU and Windows components) to be centrally administered and controlled. WMI can be used to obtain information about such devices or to make configuration changes to them.

Practical Usage

Normally used by Network Managers or Systems Administrators to monitor for common issues to occur on various system and network components/devices and execute a task to resolve such problems in case they occur.


General Properties




Specifies the WMI query that should be executed. An example of WQL is select IDProcess from Win32_PerfRawData_PerfProc_Process where name='iexplore'

The above query will monitor for the process iexplore to start.


Specifies the WMI namespace to execute the query under (i.e. root\CIMV2)

Use local computer

Enable this option to monitor for queries on the local machine.

Use remote computer

Enable this option to monitor for queries on a remote machine. If enabled, the computer name, IP address or host name of the remote machine must be entered in the provided text-box.

Use specified user

Enable this option if a specified username/password is required to connect to an Agent. If Use specified user is enabled, a valid username and password must be entered in the provided Username and Password text-boxes.

Polling interval

Determines how often this condition monitors for the resource value. The polling interval is the maximum amount of elapsed time (in seconds) before each status check. The default value is 1 second.

Behavior Properties

The Behavior tab properties dictate how the system should react upon the occurrence of a condition. These properties are significant in determining whether the AutoMate Condition should act as a trigger object (used to fire off workflow execution), wait object (used to suspend workflow execution) or conditional (decision making) object.

More about condition behavior


When this trigger is activated, it automatically passes the "AMTrigger" object to the task. AMTrigger can be used within a task to determine whether or not the task was started by a trigger, which trigger started the task, when the trigger was activated and other trigger related properties. F

Exclusive AMTrigger Fields

The AMTrigger fields described in the table below are specific only to the WMI Condition.



Return Value



Specifies the results returned by the Agent.


When this condition is used in the middle of a workflow (as opposed to triggering condition) it automatically passes the AMCondition object to the task.

Exclusive AMCondition Fields

The AMCondition fields described in the table below are specific only to the WMI Condition.




Return Value



Specifies the results returned by the Agent.


NOTE: A full list of AMCondition and AMTrigger objects exclusive to each Event/Condition can be viewed from the Expression Builder by expanding the Objects folder and selecting the desired object from either the Triggers or Conditions folder.

See Also

About Events & Conditions | Condition_Behavior | Event Log Condition | File Condition | Idle Condition | Key Event | Logon Condition | Performance Condition | Process Condition | SNMP Trap Condition | Window Condition | WMI Condition