Installing Microsoft System Center Orchestrator 2012 SP1

2013/06/27 | 3 minute read |

In one of my last post I installed a new SQL Server 2012 in my Home Lab. This was a requirement for a few incoming home lab projects. One of those projects is Microsoft System Center 2012 Orchestrator. I will have to install, configure and manage this product at my work and thought it would be nice to get familiar with it.
In 2009, Microsoft bought a company called Opalis that offers an automation platform for orchestrating and integrating IT tools to decrease the cost of datacenter operations while improving the reliability of IT processes. It enables IT organizations to automate best practices, such as those found in Microsoft Operations Framework (MOF) and Information Technology Infrastructure Library (ITIL). Opalis operates through workflow processes that coordinate System Center and other management tools to automate incident response, change and compliance, and service-lifecycle management processes.
Opalis was recently renamed Orchestrator and integrated into the System Center suite.
The following procedure will cover a basic/generic install of System Center Orchestrator 2012. This is to be used as a template or POC only.
Resources</b>
* Technet Documentation * Download * VIDEO:Microsoft System Center 2012 - Orchestrator: Crash Course * VIDEO:What's New with Orchestrator Integration Packs for System Center and SP1 * VIDEO:Edge Show 39 - Orchestrator Enhancements in System Center 2012 SP1 * VIDEO:Best Practices For Runbook Authoring and Managing Orchestrator * VIDEO:Orchestrator Best Practices: Lessons Learned at Cargill * VIDEO:Microsoft System Center 2012 - Orchestrator: Integration Packs * VIDEO:Pairing Configuration Manager 2012 and Orchestrator 2012 * VIDEO:Orchestrator Architecture Overview with SC 2012 SP1 Orchestrator Part 1 Part 2 * VIDEO:Charles Joy - Youtube channel * LAB:Microsoft System Center 2012 - Orchestrator: Overview and Automation of IT Process * LAB:System Center 2012: Orchestrator (SCO) & Service Manager (SCSM) * CODEPLEX: System Center 2012 Orchestrator Community Releases * CODEPLEX:Community Project for System Center Orchestrator (SCORCH) Integration Packs and Utilities
</b>
Deployment</b>
Server Names and Roles:
LAB1OR01- System Center 2012 Orchestrator SP1
Operating System : Windows Server 2012 Standard
Joined to Domain
* Orchestrator Roles: * Management Server * RunBook Server * Orchestrator Web Service Server * RunBook Designer client application
LAB1SQL01- Microsoft SQL Server 2012 SP1 Standard Edition
Operating System : Windows Server 2012 Standard
Joined to Domain
Process:
* * Active Directory, Create the following accounts and groups * * DOMAIN\svc-scorch (SCO Management, RunBook and Monitor Account) * DOMAIN\ScorchUsers (SCO Users with permissions/ this is Domain Global Group) * Add the domain users that need access to SCO in the group ScorchUsers. * Install Prerequisites * Install System Center Orchestrator Server Prerequisites
* * Mimimum of 1GB of RAM * .Net 3.5 SP1 * IIS Role * Add DOMAIN\svc-scorch and DOMAIN\ScorchUsers to the Local Administrators Group.
Installation</b>
1 - Click on Install.If you did not install .Net Framework 3.5 yet, you'll get the following warning 2 - Install the .Net Framework 3.5 Features in the Server Manager console.
3 - In the next screen enter your information and Product Key (if you have one). Click Next.
4 - Read and Accept the license terms.ClickNext. 5 - Select the System Center 2012 Orchestrator features to install. Here I leave the default selection.ClickNext. 6 - The Setup wizard will check if you have all the prerequisites.ClickNext.
7 - If one Prerequisiteis missing you'll get the following display. Tick the "Enable IIS Role" and click on Next. SCO Setup will automatically install the missing role or feature. 8 - Once installed, you'll have to specify the Service account for System Center Orchestrator. Ensure this is a success and click Next. 9 - Configure the database server connection, Type the local computer name if you installed SQL on this server or provide a remote SQL server (and instance if using a named instance) to which you have the System Administrator (SA) Rights in order to create the System Center Orchestrator database and assign permissions to it. Test the database connection and click Next.
10 - Configure Orchestrator Users Group. Browse Active Directory and select the domain global group created ScorchUsers. Click Next. 11 - Accept the defaults Web Service ports 81 and 82. Click Next 12 - Accept the default installation location. Click Next 13 - Select the appropriate options for Microsoft Update and Customer Experience. Click Next
14 - Finally click Next and the Installation will start. The setup will install all the roles and create the Orchestrator database. This process should be very quick. 15 - Once completed, you'll see the following display.ClickClose when you are done. You can open SQL Management Console and see that the Orchestrator database has been created. 16 - Verify your consoles open successfully.
Runbook Designer
Orchestrator Console will require Microsoft Silverlight
Orchestrator Console http://localhost:82
Deployment Manager