Updated: June 1, 2015
Applies To: System Center 2012 SP1 - Orchestrator, System Center 2012 - Orchestrator, System Center 2012 R2 Orchestrator
Welcome to System Center 2012 - Orchestrator. Orchestrator is a workflow management solution for the data center. Orchestrator lets you automate the creation, monitoring, and deployment of resources in your environment. This topic is intended solely to point you to information on various Orchestrator features.
The following topics provide information to help you deploy and use Orchestrator.
You can download a copy of this technical documentation from the Microsoft Download Center. However, for the most up-to-date information, always use the TechNet library.
The following table compares Orchestrator to the other Microsoft automation tools, Service Management Automation and Microsoft Azure Automation.
Access to Resources
Orchestrator is intended for automation of all on-premises resources. It uses a different runbook engine than Service Management Automation and Azure Automation.
Orchestrator runbooks can access resources that are on-premises and in the private cloud. They can access resources in Azure using the Windows Azure Integration Pack for Orchestrator.
Orchestrator has a graphical interface to create runbooks without requiring any scripting. Its runbooks are composed of activities from Integration Packs that are written specifically for Orchestrator. You can also use the Run .NET Script activity to run PowerShell to perform any functionality that is not included in an integration pack.
Service Management Automation is installed locally in your data center as a component of Windows Azure Pack and is intended to automate management tasks in the private cloud.
While runbooks in SMA will typically use System Center and Windows Azure Pack cmdlets to access WAP components, they can access any resource in your data center. They can include Azure cmdlets in order to manage components in the public cloud for hybrid scenarios.
Service Management Automation and Azure Automation use an identical runbook format based on Windows PowerShell Workflow. While runbooks in Azure Automation will primarily use Azure cmdlets to access public cloud resources, runbooks in SMA will typically use System Center and Windows Azure Pack cmdlets to access WAP components.
Azure Automation runbooks run in the Azure public cloud and are intended to automate Azure-related management tasks.
Runbooks in Azure Automation cannot access resources in your data center that are not accessible from the public cloud. They also have no way to access Orchestrator or SMA runbooks.
Azure Automation runbooks can access any external resources that can be accessed from a Windows PowerShell Workflow.