System Center Orchestrator 2012 R2 provides an automation framework that can be used to automate tasks within the datacenter which would otherwise require manual intervention or development of ad-hoc scripts.
In this article I will describe the process of installing System Center Orchestrator 2012 R2 in a lab environment, while Orchestrator 2012 R2 footprint is the smallest among the various System Center Products proper planning before the deployment is key to avoid issues later on for this reason I encourage you to read my post about Orchestrator 2012 R2 Architecture.
Orchestrator 2012 R2 – Getting Pre-requisites ready
As I already wrote among the various components of the System Center family Orchestrator 2012 R2 is the one with the smallest footprint and the main requisite that needs to be satisfied is a Windows machine with installed SQL.
To deploy Orchestrator 2012 R2 database you can follow my post on installing SCCM SQL Database with the only required features being
- Database Engine
- Management tools (optional but highly recommended)
Orchestrator 2012 R2 does not have the same collation requirements as Configuration Manager so you can use the default collation without any problem.
Orchestrator 2012 R2 – Service Accounts
From a requirement point of view Orchestrator does not need Active Directory nor needs to be joined to the domain even if I strongly recommend to do so for security and manageability reasons, during the installation Orchestrator 2012 R2 will require you to configure a service account that will be used to run the various components making up the Orchestrator Deployment in the lab environment the following accounts have been created/used
- SQLService – Used running SQL DB Services
- SCORService – Used as Orchestrator Service account for Management, Runbook and Monitor Account
- SCORUsers – Global Security group with members users who will be using Orchestrator
Orchestrator 2012 R2 – Installation
Orchestrator 2012 R2 installation is a rather straightforwrd process and as the product does not have a tight integration with Active Directory so there is no need for schema extension like it happens, for example, with Exchange.
Once you have downloaded Orchestrator 2012 R2 trial installation files just double-click the Install button to start the installation wizard
In the next page you will be asked to input your data and, if you have, the license key
Once you have accepted license terms you will be asked which components will be installed, as this is a lab deployment all components will be installed on a single system which is something to avoid in a production environment
Once you click next the prerequisites wizard will run eventually asking you to install/activate missing features or if there is any other obstacle blocking installation, you even have the option to view all system requirements for the various components
Once all required features and roles are installed and correctly activated you will be required to enter credential for the Service Account Orchestrator will use and name of the database server which in the lab configuration will be the same as the Orchestrator Server
Once you have specified the correct database server and tested the connection Orchestrator will ask you if you want to configure a new instance or use an existing one, unless you’re recovering the management server choose to deploy a new instance named accordingly
Next you will need to specify users allowed to use/connect to the Orchestrator instance, setup wizard will propose a default local group which can be changed to a domain one for easier management
Finally you will be able to specify installation path and update settings
After specifying if you want to participate or not in the customer experience program the installation wizard will display a summary with installation settings where you can change anything as appropriate
[su_note note_color=”#ffff96″ text_color=”#000000″ radius=”5″]Note: I strongly recommend to run Microsoft update on the server before importing any integration pack or performing any other configuration task, as I write System Center Orchestrator 2012 R2 Rollup 2 is available. [/su_note]
If there is any issue during the installation it will be displayed in summary page, after Orchestrator 2012 R2 is installed correctly you can start importing integration packs for automating tasks but that will be described in a separate article.