Building Microsoft System Center Cloud – SCOrch 2012 R2 – Orchestrator 2012 R2 installation – Complex deployment

Simplified deployment with all features on one server is described in the Orchestrator simplified installation guide in the previous article.

Uninstall previous Orchestrator

  • Standard uninstall in Program and Features…

Install and configure SQL Server

Highly-available databases in AlwaysOn Available Groups

I recommend you to use the Microsoft SQL Server 2012 AlwaysOn Available Groups for every System Center products that supports it.

After installation

Highly-available VM with SQL Server

If you do not want to use SQL Server AlwaysOn Available Groups you can simply deploy a separate VM and install SQL Server. But I suggest you to use highly-available databases in AlwaysOn Available Groups even when the installed System Center product is not highly-available.

  • Same as in in the simplified installation in the previous article.
  • Named instance
      • SCO1

Install .NET Framework 3.5

Install on Management Server, Runbook Server and also Web Service server.

  • Install .NET 3.5 from the installation media (offline installation) without need to download it from the Microsoft.
  • Command Prompt
dism.exe /Online /Enable-Feature /FeatureName:NetFX3 /All /Source:D:\Sources\sxs /LimitAccess
  • Do not forgot to install .NET 3.5 security updates.

Install Orchestrator Management Server

  • Login as member of SCOrch Users (Administrators) and SQL DB Administrators in order to create required databases during installation.
  • Install
  • Select only Management Server feature.
  • Set service account
      • serscos0
  • SQL Server Cluster with highly-available databases in AlwaysOn Available Groups
    • Choose SQL cluster.
  • Standalone highly-available VM with standalone SQL Server
    • Choose SQL DB server.
  • Let installer to create a new database.
  • Select SCOrch Users (Administrators) group and grant remote access to Runbook Designer.
      • scoadmins0
  • Accept default location.
  • Install

Install Orchestrator Runbook Server

First server

  • Install – Runbook Server
  • Set service account.
      • serscos0
  • SQL Server Cluster with highly-available databases in AlwaysOn Available Groups
    • Choose same SQL cluster as for Management Server server.
  • Standalone highly-available VM with standalone SQL Server
    • Choose same SQL DB server and instance as for Management Server server.
  • Use existing database.
  • Accept default location.
  • Install

Another Runbook servers

  • Repeat the previous steps…

Install Orchestrator Web Service

Optional when you need to use Orchestration Console or connect to the Orchestrator from third party application.

  • Install – Orchestration Console and Web Service
  • Accept default ports for the web services.
      • 81
      • 82
  • Same process as noted in the previous article.

Leave a Reply

Your email address will not be published. Required fields are marked *

Active Directory Advanced function AlwaysOn Availability Groups AlwaysOn Failover Cluster Instances Building Cloud Cloud Cluster Cmdlet Database Deployment Design DFS Domain Controller DSC Fabric Failover Clustering File Server Group Policy Hardware Profile Host Hyper-V Installation Library Library Asset Library Server Network Operations Manager Orchestrator PowerShell PowerShell User Group PowerShell Workflow Security Service Manager SQL Server Storage System Center Template Time Time Synchronization Tips Virtual Machine Virtual Machine Manager VM Network VM Template Windows Server 2012 R2