Execute Runbook

This task sequence step runs Microsoft System Center 2012 - Orchestrator runbooks on the target computer. An Orchestrator runbook is the sequence of activities that orchestrate actions on computers and networks. You can initiate Orchestrator runbooks in MDT using this task sequence step type.

Note This task sequence step is not included any MDT task sequence templates. You must add this task sequence step to any task sequences you create.

The unique properties and settings for the Execute Runbook task sequence step type are:

Properties

Name	Description
Type	Set this read-only type to Execute Runbook.
Name	The name of the task sequence step, which should reflect the name of the runbook being run.
Description	Informative text that provides additional information about the task sequence step

Settings

Name	Description
Orchestrator Server	Type the URL for the Orchestrator web service, which includes the server name. The Orchestrator web service can use either Hypertext Transfer Protocol (HTTP) or HTTP over Secure Sockets Layer (HTTPS). The Orchestrator web service defaults to port 81. The Orchestrator web service supports multiple runbook servers. By default, a runbook can run on any runbook server. A runbook can be configured to specify which runbook servers should be used to run the runbook. Note The Orchestrator web service supports the ability to run a runbook on a specific runbook server. This feature is not supported in MDT. Specify the URL in any of the following formats: · servername. When using this format, the URL defaults to: http://<servername>:81/Orchestrator2012/Orchestrator.svc · servername:port. When using this format, the URL defaults to: http://<servername:port>/Orchestrator2012/Orchestrator.svc. · http://servername:port. When using this format, the URL defaults to: http://<servername:port>/Orchestrator2012/Orchestrator.svc. · https://servername:port. When using this format, the URL defaults to: https://<servername:port>/Orchestrator2012/Orchestrator.svc. · http://servername:port/Orchestrator2012/Orchestrator.svc. When using this format, MDT assumes that you are providing the fully qualified URL, because the value ends with .svc. · https://servername:port/Orchestrator2012/Orchestrator.svc. When using this format, MDT assumes that you are providing the fully qualified URL, because the value ends with .svc.
Runbook	Click Browse, and then select the name of the Orchestrator runbook that this task sequence should run. Note To successfully browse for Orchestrator runbooks, install the ADO.NET Data Services Update for .NET Framework 3.5 SP1 for Windows 7 and Windows Server 2008 R2.
Automatically provide runbook parameters	Select this option to automatically provide the Orchestrator runbook input parameter values( which assumes that the runbook parameter values are task sequence variables). For example, if a runbook has an input parameter named OSDComputerName, then the OSDComputerName task sequence variable value is passed to the runbook. Note This option works only for input parameters that are valid task sequence variable names and do not contain spaces or other special characters. Although spaces and other special characters are supported as Orchestrator parameter names, they are not valid task sequence variable names. If you need to pass values to parameters with spaces or other special characters, use the Specify explicit runbook parameters option. The other option is Specify explicit runbook parameters. Note The values provided for the runbook input parameters to the Orchestrator web service are formatted as XML. Passing values that contain data that is or resembles XML-formatted data may cause errors.
Specify explicit runbook parameters	Select this option to explicitly provide the Orchestrator runbook input parameters. You must configure the following settings for each input parameter that the Orchestrator runbook requires: · Name. This is the name of the input runbook parameter. Note If you change the parameters for an existing Orchestrator runbook, you need to browse (reselect) for the runbook again, because MDT only retrieves the parameter list when initially adding the Orchestrator runbook. · Value. This can be a constant or a variable, such as a task sequence variable or an environment variable. For example, you can specify a value of %OSDComputerName%, which will pass the value of the OSDComputerName task sequence variable to the runbook input parameter.
Wait for the runbook to finish before continuing	This check box controls whether the task sequence step will wait for the runbook to finish before proceeding to the next task sequence step. If this check box is: · Selected, then the task sequence step will wait for the runbook to finish before proceeding on to the next task sequence step. When this check box is selected, the task sequence step will poll the Orchestrator web service for the runbook to finish. The amount of time between polls starts at 1 second, then increases to 2, 4, 8, 16, 32, and 64 seconds between each poll. Once the amount of time reaches 64 seconds, the task sequence step continues to poll every 64 seconds. · Cleared, then the task sequence step will not wait for the runbook to finish before proceeding to the next task sequence step. Note This check box must be selected if the runbook returns output parameters.