Runtime Tasks

Runtime tasks are executed either on a Management Server or an agent-managed Computer. All runtime tasks should specify the following:

• Task Type: Command line, Script, Managed Code, File Transfer.

• Target Class name: specifies what type of entity the task is designed for. This information is used by the Operator console to present instances of the class as possible task targets when the user is launching the task.

• Target Role

• The task target role controls two things. First, it controls which attributes are available for passing into the command as parameters. Secondly, it controls which targets the task can be launched against. For example, if a task is defined for the Exchange role and the user tries to launch the task against a computer that does not have that role, the Run Task Wizard will fail. In addition, if the computer the user has selected to run the task on hosts more than one instance of the target role, the user can select which instance(s) to run the task on. The task will be run once for each selected target role instance.

• Run Location can be one of the following:

  • Run it on the Management Server.

  • Run it on the Agent.

  • Run it as close as possible to the managed computer. If the target computer has an Agent then it runs on the Agent, otherwise it runs on the Management Server.

When the user wants to launch a runtime task from the Operator console, the user selects a list of target computers and selects the runtime task to launch. The task targets are the list of instances of the specified class discovered by service discovery.

Runtime tasks always run under the security context of the Action Account. It is not possible to substitute security context (i.e. Run As) when running a task. Only MOM Authors and MOM Administrators can run Runtime Tasks. For more information about security and role, see the MOM 2005 Security Guide.

There are four types of Runtime Tasks:

• Command line

• Script

• Managed Code

• File Transfer