Select a group whose members will have access to the Runbook Designer and Deployment Manager. This can be a local group but recommend to be an Active Directory group so that it can be centrally managed. If the group does not exist, then it will be created and the current user account added to it.
Members of this group have administrative access to Orchestrator and have access to all configuration and data stored in the Orchestrator database, including encrypted data.
Runbook servers handle running instances of active runbooks. Runbook servers require active communication to the Datastore ...
Runbooks cannot be processed until you deploy at least one runbook server. Would you like to deploy a runbook server now? ...
Runbooks that start with Monitor activities cannot run multiple, concurrent requests. The maximum number of requests has ...
Save Event Log is used to save the messages in a specific Event Log on a local or remote computer. These messages are saved ...
Select a group whose members will have access to the Runbook Designer and Deployment Manager. This can be a local group but ...
Setup detected that one or more components are already installed on this computer. Use the Standalone installations below ...
Setup has detected Opalis 6.3 installed on this computer. To continue installing System Center 2012 Orchestrator, uninstall ...
Setup will install the missing prereqisites when you click Next. For some prerequisites, you need to select an option before ...
Specify the database server, instance name, and port number for the Orchestrator database. You must have sufficient permissions ...