Operator Console Tasks

Operator console tasks execute on the same computer that is hosting the Operator console. These tasks can be launched in context to the users selection. For example, the name of the selected computer can be passed into the task as a parameter to provide context on how the task should run. For more information on security and roles, see the MOMĀ 2005 Security Guide.

Operator console tasks run under the security context of the user that is running the Operator console. Any MOM User, MOM Author, or MOM Administrator can run a console task.

Operator console tasks have the following four properties to configure:

View Type

Console tasks can be defined for three different view types:

Alerts

Tasks defined for the Alerts view type are only executable when an alerts view is active and a single alert is selected.

Events

Tasks defined for the Events view are only executable when an events view is active and a single event is selected.

Computers

When a task is defined for the Computers view type, it will be executable in any of the following view types:

  • Alert

  • Event

  • Attribute

  • Computer Tasks defined for the Computers view type will not be available when the computer group view type is selected.

  • Performance data

  • Computer performance

  • Diagram

Table 7.1 Various Properties of the Task Views

Task View Type Definition

Tasks Available in Operator console Views Types

Multi-select

Alert

Alert

No

Event

Event

No

Computer

Alert

Event

Computer

Attribute

Computer Performance

Performance Data

Diagram

No

Command

Console tasks can be only command-line tasks. The action that is executed is specified in terms of a command line to execute. When a task gets launched against the selected item in the Operator console, the properties of the item can be passed to the command line as parameters. For example, if a user wants to connect to the computer that raised an alert using Remote Desktop, the user can create a console task. The command line to execute can be set to "mstsc.exe $Computer Name$". Here, the variable $Computer Name$ will be replaced by the computer name of the selected item in the Operator console. Tasks defined for the computer view type will be available for computers, alerts and events.

Commands should begin with a executable file name (.exe, .bat, .wsf, .js, .vbs, .cmd, etc.) including the extension. Command-line parameters can then, optionally, be included after the file name.

Depending on the view type selected, a different set of relevant attributes are available to be passed into the command line as parameters. For example, if the Alerts view type is selected, the Alert Name of the selected alert can be passed as a parameter.

Management pack developers should always use the secure method of creating command tasks. The Windows command interpreter should, generally, not be used. Tasks should be created such that the task application and the parameter string are separated, to avoid malicious appropriation of the task command.

Starting Folder

The executable file is located in the starting folder. In addition, this is the starting folder if you are using a batch file.

Output Display

Some tasks generate standard output that the user would want to see as a result of the task. One example of this is the ping.exe tool . Some tasks, on the other hand, do not generate standard output, and may actually launch another user interface. An example of this is Remote Desktop (mstsc.exe). When Display Output is selected, the standard output will be captured and displayed in an output window in the Operator console.