WMI Condition
Description
Monitors for a WQL (WMI Query Language) query executed on the agent computer to return TRUE or more than 0 rows and evaluates as TRUE when the condition is met. 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 (for example, 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. This condition can be set as one of the following workflow elements:
-
Trigger element - When positioned in the beginning of a workflow, triggers its execution when the monitored condition (that is, WQL query returns TRUE) evaluates to TRUE.
-
Wait element - Suspends execution of a running workflow until the monitored condition (that is, WQL query returns TRUE) valuates to TRUE.
-
Conditional element - Determines the course of a workflow depending on whether or not a specific condition (that is, WQL query returns more than 0) evaluates to TRUE.
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.
Parameters
General
| Property | Type | Description |
|---|---|---|
| WQL | String | Specifies the WMI query that should be executed.
For example, the following query will monitor for the process
"iexplore" to start: select IDProcess from Win32_PerfRawData_PerfProc_Process where Press the Query Builder button to open the WMI Query Builder which is a separate IDE that can aid in query construction. |
| Namespace | String | Specifies the WMI namespace to execute the query under (for example, root\CIMV2) |
| Use local computer | Yes/No | Enable this option to monitor for queries on the local computer (enabled by default). |
| Use remote computer | Yes/No | Enable this option to monitor for queries on a remote machine. If enabled, the computer name, IP address or hostname of the remote machine must be entered in the provided text-box. |
| Use specified user | Yes/No | 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. |
| Username | String | The username used to connect to the agent. |
| Password | String | The password related tot he username entered above. |
| Polling interval | Number | 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
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.
Additional notes
AMTrigger
When the Key event is used to trigger workflow execution, it automatically creates an AMTrigger dataset which can be used much like the datasets created by the Database - SQL query activity and Email action. The fields that AMTrigger generates can be used to determine properties of the object that caused the workflow to launch, such as the type of trigger, when the trigger was activated and what system event or condition took place to activate the trigger. Along with a collection of global AMTrigger fields that are created and populated by every instance of AMTrigger, a unique set of AMTrigger fields exclusive to each Automate trigger are created as well.
To view AMTrigger values exclusive to the WMI condition, see AMTrigger - WMI.
AMCondition
When the WMI condition is used in the middle of a workflow as wait or conditional object, it automatically creates an AMCondition dataset. Similar to AMTrigger, the fields that AMCondition generates can be used to determine properties of the object that caused the condition to activate. Along with a collection of global AMCondition fields that are created and populated by every instance of AMCondition, a unique set of AMCondition fields exclusive to each Automate condition are created as well.
To view AMCondition values exclusive to the WMI condition, see AMCondition - WMI.