WMI Trigger


Launches a task when a WQL 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.

Practical Usage

Normally used by Network Managers or Systems Administrators to monitor for common issues to occur on various systems and network components/devices and execute a task to resolve such problems in case they occur. During execution, the task can determine the exact issue and direct itself to perform proper actions to correct the problem.

Related Topics  








The WMI query that should be executed (e.g. select IDProcess from Win32_PerfRawData_PerfProc_Process where name='iexplore').

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



The WMI namespace to execute the query under (e.g. root\CIMV2). Click the down arrow to select from a drop-down list of available namespaces.

Use local/remote computer


Determines which computer this trigger should monitor. The available options are:

  • Use local computer - The local computer will be monitored.

  • Use remote computer - A remote computer will be monitored.

Remote computer


The computer name or IP address of the remote computer to monitor. This parameter is active only if the Use remote computer option is selected. If the Use local computer parameter is selected, this parameter is irrelevant.

Use specified user


If set to YES, indicates that a username/password is required to connect to an Agent (set to NO by default).



The username used to connect to the remote agent. Active only if the Use specified user parameter is set to YES.



The password used to connect to the remote agent. Active only if the Use specified user parameter is set to YES.

Polling Interval 'x' seconds


Specifies how often this trigger 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 every 1 second.





Enable trigger


If set to YES (default), specifies that the trigger is enabled. If set to NO, the trigger is disabled.

Trigger on startup if condition is true


If set to YES, the trigger will act on conditions that already exist upon startup. If set to NO (default), existing conditions are ignored. For example, assume the file to monitor already exists in the target folder upon creation or startup of this trigger. Yes, will immediately launch the task, however, NO will not.

Trigger after the condition has been met 'X times


If set to YES, specifies how many times the trigger condition must be met before the task is started.

additional notes


When this trigger is activated, it automatically passes the AMTrigger object to the task. AMTrigger is a standard AutoMate dataset and can be used much like the datasets created by the SQL Query and Email actions. The fields of AMTrigger can be used within a task to determine specific values, such as whether or not the task was started by a trigger, which trigger started the task, when the trigger was activated and other properties. AMTrigger populates a unique set of field–value pairs for each AutoMate trigger. The following table lists the ones specific to this trigger. For more details about a specific AMTrigger field–value pair, click the associated link.


Data Type

Return Value



Returns the result of the WQL query or WMI event that initiated the trigger.


NOTE: A full list of AMTrigger objects exclusive to each trigger can be viewed from the Expression Builder by expanding Objects -> Triggers and selecting the desired trigger.