Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

Orchestrator 2012 SP1 - QuickStart deployment guide

Orchestrator 2012 SP1 - QuickStart deployment guide

  • Comments 9
  • Likes

 

System Center Orchestrator 2012 SP1 is extremely easy to setup and deploy.  There are only a handful of prerequisites, and most can be handled by the setup installer routine.

The TechNet documentation does an excellent job of detailing the system requirements and deployment process:

http://technet.microsoft.com/en-us/library/hh420337.aspx

The following document will cover a basic install of System Center Orchestrator 2012 at a generic customer.  This is to be used as a template only, for a customer to implement as their own pilot or POC deployment guide.  It is intended to be general in nature and will require the customer to modify it to suit their specific data and processes.

SCORCH can be scaled to match the customer requirements. This document will cover a typical two server model, where all server roles are installed on a single VM, and utilize a remote database server or SQL cluster.

This is not an architecture guide or intended to be a design guide in any way.

Definitions:

SCORCH          System Center Orchestrator

Server Names\Roles:

SCORCH          Orchestrator 2012 role server

  • Management Server
  • Runbook Server
  • Orchestrator Web Service Server
  • Runbook Designer client application

DB1                  SQL 2012 Database Engine Server

 

Windows Server 2012 will be installed as the base OS for all platforms.  All servers will be a member of the AD domain.

SQL 2012 will be the base standard for all database services. SCORCH only requires a SQL DB engine (locally or remote) in order to host SCORCH databases.

High Level Deployment Process:

1.  In AD, create the following accounts and groups, according to your naming convention:

a.  DOMAIN\scorchsvc                       SCORCH Mgmt, Runbook, and Monitor Account

b.  DOMAIN\ScorchUsers                   SCORCH users security global group

c.  DOMAIN\sqlsvc                              SQL Service Account

2.  Add the domain user accounts for yourself and your team to the ScorchUsers group.

3.  Install Windows Server 2012 to all server role members.

4.  Install Prerequisites.

5.  Install the SCORCH Server.

Prerequisites:

1.  Install Windows Server 2012 on all servers.

2.  Join all servers to domain.

3.  Ensure SCORCH server has a minimum of 1GB of RAM.

4.  On the SCORCH server, .Net 3.5SP1 is required. Setup will not be able to add this feature on Windows Server 2012.  Open an elevated PowerShell session (run as an Administrator) and execute the following:

Add-WindowsFeature NET-Framework-Core

5.  On the SCORCH server, IIS (IIS Role) is required. Setup will add this role if not installed. 

6.  On the SCORCH .Net 4.0 is required. This is included in the WS2012 OS (.NET 4.5)

7.  Install all available Windows Updates as a best practice.

8.  Add the “DOMAIN\scorchsvc” domain account explicitly to the Local Administrators group on the SCORCH server.

9.  Add the “DOMAIN\ScorchUsers” global group explicitly to the Local Administrators group on the SCORCH server.

10.  On the SQL database server, install SQL 2012.

  • Setup is fairly straightforward. This document will not go into details and best practices for SQL configuration. Consult your DBA team to ensure your SQL deployment is configured for best practices according to your corporate standards.
  • Run setup, choose Installation > New SQL server stand-alone installation…..
  • When prompted for feature selection, install ALL of the following:
    • Database Engine Services
  • Additionally, the product documentation for SCVMM states to install the management tools – complete:
    • Management Tools – Basic and Complete (for running queries and configuring SQL services)
  • On the Instance configuration, choose a default instance, or a named instance. Default instances are fine for testing and labs. Production clustered instances of SQL will generally be a named instance. For the purposes of the POC, choose default instance to keep things simple.
  • On the Server configuration screen, set SQL Server Agent to Automatic.  I prefer to use a service account for SQL, so I will set the Agent and DB Engine to run under my DOMAIN\sqlsvc account and provide the password.  This is optional.
  • On the Collation Tab – you can use the default of SQL_Latin1_General_CP1_CI_AS or choose another supported collation.
  • On the Account provisioning tab – add your personal domain user account or a group you already have set up for SQL admins. Alternatively, you can use the ScorchUsers global group here. This will grant more rights than is required to all ScorchUser Admin accounts, but is fine for testing purposes of the POC.
  • On the Data Directories tab – set your drive letters correctly for your SQL databases, logs, TempDB, and backup.
  • Setup will complete.

Step by step deployment guide:

1.  Install SCORCH 2012:

  • Log on using your domain user account that is a member of the ScorchUsers group.
  • Run Setuporchestrator.exe
  • Click Install
  • Supply a name, org, and license key (if you have one) and click Next.  If you don't input a license key it will install Eval version.
  • Accept the license agreement and click Next.
  • Check all boxes on the getting started screen, for:
    • Management Server
    • Runbook Server
    • Orchestration Console and Web Service
    • Runbook Designer
  • On the Prerequisites screen, check the boxes to remediate any necessary prerequisites, and click Next when all prerequisites are installed.
  • Input the service account “scorchsvc” and input the password, domain, and click Test. Ensure this is a success and click Next.
  • Configure the database server. Type in the local computer name if you installed SQL on this SCORCH Server, or provide a remote SQL server (and instance if using a named instance) to which you have the “System Administrator” (SA) rights to in order to create the SCORCH database and assign permissions to it. Test the database connection and click Next.
  • Specify a new database, Orchestrator. Click Next.
  • Browse AD and select your domain global group for ScorchUsers. Click Next.
  • Accept defaults for the SCORCH Web service ports of 81 and 82, Click Next.
  • Accept default location for install and Click Next.
  • Select the appropriate options for Microsoft Update, Customer Experience and Error reporting. Click Next.
  • Click Install.
  • Setup will install all roles, create the Orchestrator database, and complete very quickly.

2. Open the consoles.

  • Open the Deployment Manager, Orchestration Console, and Runbook designer. Ensure all consoles open successfully.

Post install procedures:

1.  Lets register and then deploy Integration Packs that enable Orchestrator to connect to so many outside systems.

Download the toolkit, add-ons, and IP’s for SCORCH 2012 SP1.

  • Make a directory on the local SCORCH server such as “C:\IntegrationPacks”
  • Copy to this directory, the downloaded IP’s, such as the following:
    • SC2012SP1_Integration_Pack_for_Configuration_Manager.oip
    • SC2012SP1_Integration_Pack_for_Data_Protection_Manager.oip
    • SC2012SP1_Integration_Pack_for_Operations_Manager.oip
    • SC2012SP1_Integration_Pack_for_Service_Manager.oip
    • SC2012SP1_Integration_Pack_for_Virtual_Machine_Manager.oip
    •                  
  • Open the Deployment Manager console
  • Expand “Orchestrator Management Server
  • Right click “Integration Packs” and choose “Register IP with the Orchestrator Management Server
  • Click Next, then “Add”.  Browse to “C:\Integration Packs” and select all of the OIP files you copied here.  You have to select one at a time and go back and click “Add” again to get them all.
  • Click Next, then Finish.  You have to accept the License Agreement for each IP. 
  • Now when you select “Integration Packs” you can see these IP’s in the list.
  • Right Click “Integration Packs” again, this time choose “Deploy IP to Runbook server or Runbook Designer”.
  • Click Next, select all the available IP’s and click Next.
  • Type in the name of your Runbook server role name, and click Add.
  • On the scheduling screen – accept the default (which will deploy immediately) and click Next.
  • Click Finish.  Note the logging of each step in the Log entries section of the console.
  • Verify deployment by expanding “Runbook Servers” in the console.  Verify that each runbook was deployed.
  • Open the Runbook Designer console.
  • Note that you now have these new IP’s available in the designer for your workflows.

Additionally – you can download more IP’s at:

http://technet.microsoft.com/en-us/library/hh295851.aspx

Such as the VMware VSphere IP, or the IBM Netcool IP.

Additionally – check out Charles Joy’s blog on popular codeplex IP’s which have been updated for Orchestrator:

http://blogs.technet.com/b/charlesjoy/

Comments
  • Hey Kevin, have you tried upgrading an existing Scorch? I have tried a couple of times following the MS guide and it always erases my previous folders and runbooks. There's no error or complaint. It supposedly upgrades the DB but everything is gone,including global variables and such.

    Any ideas?

    Jose

  • For Orchestrator - you need to uninstall the core components (management server, runbook server, runbook designer etc) but RETAIN the database.

    You then install the new version and state to connect to an existing Orchestrator SQL Server \ database.

    technet.microsoft.com/.../jj900492.aspx

  • Shall we use Orchestrator for servers which are located in other domains also ?

  • I mean if we open the port for servers which are located in other domains will it be possible to run the workflow located in those domains ??

  • I'm standing up an all in one to do some POC work.  Interestingly enough it appears that if I change the default path (we don't typically install things on c:) the installtion fails trying to install the management server.  The log shows some cryptic messages that appears to suggest there was an ACLing issue and that a separate message that the service couldn't be started.  Just a tid bit if someone else runs across the same issue -- worked fine with default path but not if I specified a path.

  • Where can I download the mentioned Integration Pack: SC2012SP1_Integration_Pack_for_Operations_Manager.oip

    I noticed that it did not appear on your URLs:

    technet.microsoft.com/.../hh295851.aspx

    blogs.technet.com/.../charlesjoy

  • Kevin, do you know if SQL AlwaysOn Availability Groups and/or SQL Mirroring are *officially supported* with System Center Orchestrator 2012 SP1 or SCORCH 2012 R2? After doing some research, it looks like it can be made to work if the SQL service master key is synchronized on the SQL Servers... but I do not want to implement something that is not supported by Microsoft.

    Thanks!

  • Frank - SQL always on is supported for SCO:

    technet.microsoft.com/.../jj628198.aspx

    SQL Server 2012 AlwaysOn Support:

    In System Center 2012 SP1, SQL Server 2012 AlwaysOn is supported in the following components:

    • App Controller

    • Operations Manager

    • Orchestrator

    • Service Manager

    • VMM

    SQL Server AlwaysOn is not supported with Data Protection Manager (DPM) and Configuration Manager.

  • when installing SCORCH with SQL always on, can you install the database onto the always on listener or do you have to move the database into the group? Thanks, Kind Regards Zach

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Search Blogs