Microsoft System Center 2012 Orchestrator Cookbook

By Samuel Erskine , Andreas Baumgarten , Steve Beaumont
    Advance your knowledge in tech with a Packt subscription

  • Instant online access to over 7,500+ books and videos
  • Constantly updated with 100+ new titles each month
  • Breadth and depth in over 1,000+ technologies
  1. Unpacking System Center 2012 Orchestrator

About this book

Microsoft System Center Orchestrator 2012 simplifies the process of automating systems administration tasks. Originally a third-party product named Opalis, which Microsoft acquired in 2009, Orchestrator provides a simplified way of building complex automation. System Center Orchestrator is a complete solution that goes beyond basic automation.

"Microsoft System Center 2012 Orchestrator Cookbook" will teach you how to plan, create and manage powerful runbooks to help you automate mission-critical and routine administration tasks.

In this practical Cookbook you will learn how to master System Center 2012 by creating runbooks to control and automate every feature possible. You will start by learning how to efficiently install and secure System Center Orchestrator.


You will then learn how to plan and create functional and fault-tolerant System Center runbooks to automate daily tasks and routine operations. Diving deep into runbooks, you will learn how to create powerful and practical runbooks for the entire System Center family of products.

Unleashing your inner control freak, you will then master System Center automation by creating IT Service Management process runbooks and advanced runbooks to help you control every feature imaginable of System Center. If you want to save time and energy automating mission critical tasks with System Center 2012 Orchestrator, then this book is for you!

Publication date:
August 2013
Publisher
Packt
Pages
318
ISBN
9781849688505

 

Chapter 1. Unpacking System Center 2012 Orchestrator

In this chapter we will cover the following recipes:

  • Planning the Orchestrator deployment

  • Installing a single-server deployment

  • Installing the Management Server in a multiserver deployment

  • Installing the Runbook Server in a multiserver deployment

  • Installing the Orchestration Console and the Web Service server in a multiserver deployment

  • Installing the Runbook Designer in a multiserver deployment

 

Introduction


Microsoft System Center 2012 Orchestrator (SCORCH) is a process automation and multi-technology product connection toolkit. It delivers the following two key challenges of an organization:

  • Automation of manual repeatable tasks

  • Connecting multiple IT vendor products

The first common IT challenge, "automation of manual repeatable tasks" when coupled with supporting organization policies can significantly improve IT value and efficiency. The second challenge "connecting multiple IT vendor products", provides organizations with a single logical product (SCORCH) to interconnect and coordinate the activities between the typical multi-vendor technology investments.

In order to deliver the capabilities of SCORCH we must unpack the product "our toolbox" by planning our deployment (what is the size, type, and contents of the toolbox), and installing the product based on our agreed deployment plan. This chapter focuses on the activities you must perform to have a fully functional SCORCH installation.

Understanding SCORCH deployment components

The SCORCH architecture is made up of six types of components. The basic automated activity delivered by SCORCH is called a Runbook which is commonly known as a workflow in other products. The six components which make up the SCORCH product are listed and described in the following table and illustrated in figure following the table:

SCORCH Component

Description

Runbook Designer

The Runbook Designer is the tool for creating and editing Runbooks. Runbooks are stored in the Orchestration database. A sub-component of the Runbook Designer is the Runbook Tester, which is used to validate the execution of Runbooks.

Orchestration Database

The Orchestration database is a Microsoft SQL Server database which stores Runbooks, the status of Runbooks and security delegation configuration. The database also stores the log files and configuration of the SCORCH deployment.

Management Server

The Management Server is the core communication component of the SCORCH architecture and is responsible for coordinating the communication between the Runbook Designer and the Orchestration database. There is only one Management Server per SCORCH deployment.

Runbook Server

The Runbook Server is responsible for executing instances of Runbooks. When a Runbook is invoked, a copy of the Runbook instance is sent to its assigned Runbook Server and then it is executed (by default, this is the first installed Runbook Server which is assigned the Primary role).

Orchestrator Web service

The Orchestrator Web Service is the interface that enables applications to connect to SCORCH. Typical tasks performed through the Web Service are Runbook status views, start, and stop actions.

Orchestrator Browser Console

Orchestrator Browser Console is a Silverlight supported web browser which uses the Orchestrator Web Service to communicate with SCORCH.

The six parts of SCORCH are illustrated in the following figure:

For the smallest implementation all the components can be deployed to one server (physical or virtual). You have the option to scale out the deployment by using multiple servers to host one or more components of SCORCH. The deployment choice is determined by the planning activities you perform before invoking the installation of the product. The Planning the Orchestrator deployment recipe discusses the factors you must consider to assist with the deployment choice.

Tip

About the Management Server

At the time of writing, the current version of SCORCH supports only one instance of a Management Server per deployment. You can deploy multiple instances of the other parts of the product with a note that we are still dealing with just one database per Management Server. The database instance can be made highly available.

 

Planning the Orchestrator deployment


The installation of SCORCH is simple. You must plan the deployment appropriately according to your needs. This recipe discusses and provides steps on common planning tasks to be performed before inserting the DVD or mounting the ISO for organizations who have successfully deployed SCORCH.

Getting ready

The authors recommend you to review the latest information on SCORCH at http://technet.microsoft.com/en-us/library/hh420383.aspx as the requirements of the product and supported platforms are regularly updated by Microsoft.

How to do it...

There are three planning categories, people, process, and the technology (SCORCH product).

  1. Identify and agree on the roles and responsibilities of the SCORCH team. SCORCH deployments typically have three types of users; service accounts, Administrators, and operators.

    • Services accounts: They perform actions for the specific components of SCORCH

    • Administrators: They will typically perform all activities including, but not limited to, SCORCH installation, Runbook creation and management, and delegation of security to operators

    • Operators: They will typically use the SCORCH console and the Runbook Designer to create and manage Runbooks

  2. Identify and document initial prototype processes to be used as the first candidate for automation and testing. The types of processes for this purpose should be simple repeatable tasks that fall into an organizations required standard service requests. Good candidates are service request which do not require authorization and approval. An additional example category is Windows operating system services that can be stopped and started as a part of trouble shooting.

  3. Plan for the following technology requirements areas for SCORCH:

    • SCORCH deployment type

      Deployment type

      Description

      single server

      All SCORCH roles are installed on one physical or virtual machine.

      This scenario is typically implemented in test environments but is fully supported in production. This however becomes a single point of failure for highly automated environments.

      multi-server

      The SCORCH roles are separated and installed on one or more machines.

    • Minimum hardware requirements for each SCORCH component

      Component

      Requirements

      Management Server

      • Operating system: Windows Server 2008 R2 or Windows Server 2012*

      • 1 gigabyte (GB) of RAM, 2 GB or more recommended

      • 200 megabytes (MB) of available hard disk space

      • Dual-core Intel microprocessor, 2.1 gigahertz (GHz) or better

      • Microsoft .NET Framework 3.5 Service Pack 1

      Orchestration database

      • Database: Microsoft SQL Server 2008 R2 or SQL Server 2012

      • Collation: SQL_Latin1_General_CP1_CI_AS

      • Local or Remote (Basic Engine only)

      Runbook Server

      • Operating system: Windows Server 2008 R2 or Windows Server 2012*

      • 1 gigabyte (GB) of RAM minimum, 2 GB or more recommended

      • 200 megabytes (MB) of available hard disk space

      • Dual-core Intel microprocessor, 2.1 gigabyte (GHz) or better

      • Microsoft .NET Framework 3.5 Service Pack 1

      Orchestrator Console/Web Service

      • Operating system: Windows Server 2008 R2 or Windows Server 2012*

      • 1 gigabyte (GB) of RAM minimum, 2 GB or more recommended

      • 200 megabytes (MB) of available hard disk space

      • Dual-core Intel microprocessor, 2.1 gigahertz (GHz) or better

      • Microsoft .NET Framework 3.5 Service Pack 1

      • Web Service: Internet Information Services (IIS) 7.0 and enabled IIS role

      • Microsoft .NET Framework 3.5 Service Pack 1

      • Microsoft .NET Framework 4

      • Microsoft Silverlight 4**

      Orchestrator Runbook Designer

      • Operating system: Windows Server 2008 R2, Windows 7 (32/64 bit) or Windows Server 2012*

      • 1 gigabyte (GB) of RAM minimum, 2 GB or more recommended

      • 200 megabyte (MB) of available hard disk space

      • Dual-core Intel microprocessor, 2.1 gigabyte (GHz) or better

      • Microsoft .NET Framework 3.5 Service Pack 1

      Tip

      SCORCH 2012 SP1

      It is required only for the computer running the console in its web browser but not the Web Service server.

    • Services accounts and delegation groups

      Account/Group

      Type

      Notes

      Orchestrator management service

      Service account

      Create an Active Directory user account for this service. This is the main management server service account and it is granted log on as a service during the installation.

      Orchestrator Runbook monitor service

      Service account

      Typically this is the same account as the Orchestrator Management Service.

      Orchestrator Runbook service

      Service account

      Same user account as the Management and Runbook Server monitor service in a single deployment but can be different for multi-server deployments; Active Directory domain account recommended.

      Runbook authors (SCO_ADMINS)

      Group

      Create an Active Directory group. This group will have the equivalent access of full administration to the SCORCH deployment.

      Runbook operators (SCO_CON_USERS)

      Group

      Create an Active Directory group. This group will have the equivalent access of a Runbook operator to the SCORCH deployment.

      Installation user

      User

      The user with full administrative rights on the SCORCH servers is required to perform the installation and configuration of the SCORCH deployment.

    • Network Communication Ports

      Source

      Targeted computer

      Default port

      Configurable

      Runbook Designer

      Management Server

      135, 1024-65535

      Yes.

      Management Server, Runbook Server, and Web Service

      Orchestration database

      1433

      Yes; specified during the installation on the SCORCH supported version of Microsoft SQL Server. This is the case where the SQL Server instance is not using the default port.

      Client browser

      Orchestrator Web Service

      81

      Yes; during the SCORCH installation.

      Client browser

      Orchestration Console

      82

      Yes; during the SCORCH installation.

How it works...

The planning activities discussed are the minimum activities the authors recommend. The tasks performed at this stage will ensure that you ask for and plan for all your requirements before investing time in the actual installation. An additional benefit is identifying any people or budgetary risks before the deployment.

There's more...

There are two additional planning areas which are typically ignored in technology focused deployments. These areas are communication strategies and stakeholder management.

Communication strategy

One of the inaccurate myths of SCORCH is that it would automate the IT professional. SCORCH when implemented right would improve efficiency but will not replace people. On the contrary you need to communicate with the people who perform the manual tasks as they hold the key to how to best automate their efforts. Early engagement with all IT team members should be one of your key planning tasks.

Stakeholder management

Stakeholders are all users affected by the SCORCH deployment. An important category of stakeholders are the management team responsible for policy creation and enforcement. Automation without organization buy in may lead to conflicts at the political level of your organization. An example of such a scenario is the ability to create Active Directory user accounts with rights to specific organization areas and restricted resources.

 

Installing a single-server deployment


This recipe provides the steps required to install all the SCORCH roles on a single server. The single server deployment is appropriate for test and development environments. This deployment type will assist you with evaluation of the product, initial Runbook creation, and validation prior to deploying in your production environment. Though supported in production you must plan to implement the multi-server deployment to provide flexibility and availability.

Getting ready

You must plan to review the Planning the Orchestrator deployment recipe before performing the steps in this recipe. There are a number of dependencies discussed in the planning tasks which you must perform in order to be able to successfully complete the steps in this recipe.

The authors assume that you have access to all the installation media and the user account performing the installation, has administrative privileges on the server nominated for the SCORCH deployment.

How to do it...

The following figure provides a visual summary and order of the tasks you need to perform to complete this recipe:

The deployment will be implemented in an Active Directory environment and with the Windows Server 2012 operating system. Perform the following steps to deploy SCORCH on a single machine:

  1. In Active Directory create the required and recommended user accounts and groups. In this example we will create the following groups:

    • Users: SCO_MGTSVCA and SCO_RBSSVCA

    • Groups: SCO_ADMINS and SCO_CON_USERS

  2. Install a supported Windows Server operating system and join the server to the Active Directory domain in scope of the SCORCH deployment.

  3. Add the two services accounts and the SCORCH Administrators group to the local Administrators group on the SCORCH server.

  4. On the SCORCH server enable the following role and feature:

    • Role: Web Server (IIS) (default settings), note that the installation will enable this role for you if it is not found on the target server

    • Feature: .NET Framework 3.5 SP1, you must specify a source file for .NET Framework 3.5 SP1 in the case of Windows Server 2012 and ensure that the DVD for Windows Server 2012 is loaded

  5. Install .NET Framework 4 if the operating system version is lower than Windows Server 2012 (.NET Framework 4x is already part of Windows Server 2012).

  6. Optionally install Silverlight. After the SCORCH installation you will be prompted to install Silverlight if you run the console on the server.

  7. Install a supported version of Microsoft SQL Server. In our example we will install Microsoft SQL Server 2012 standard edition with Service Pack 1. The following are the minimum options required for the installation:

    • Instance features: database engine services

    • Share features: Management Tools—Basic

    • Collation: SQL_Latin1_General_CP1_CI_AS

    • Authentication Credentials: Windows Authentication (recommended)

  8. Insert or mount the SCORCH installation media on the server. Log on with a user account with administrative rights.

  9. Launch the installation using the SetupOrchestrator.exe file. Click on Install under the System Center 2012 Orchestrator Setup section on wizard page.

  10. On the Product Registration page enter your organization details and the product Key (though the product key can be entered post installation, it is a best practice to enter this during the installation to reduce the risk of product evaluation expiry after the default 180 day period). Click on Next.

  11. Review the Please read this License Terms page and accept to continue with the installation. Click on Next.

  12. On the Select features to install wizard page ensure all options are checked. Click on Next.

  13. On the Configure the service account page type the user account you created for the management server service account and password. Click on Test to verify the details. Click on Next.

  14. On the Configure the database server page type the server name and if applicable the instance of SQL where the Orchestration database will be created. Click on Test to verify the connection to the database server. Click on Next.

  15. On the Configure the database page, ensure that new database is selected and the default name is Orchestrator for the database. Click on Next.

  16. On the Configure Orchestrator users group page, click on Browse… and specify the Active Directory group you created for the SCORCH administrators role (SCO_ADMINS in our example). Click on Next.

  17. On the Configure the ports for the web services page leave the default options (81 and 82) or provide your custom options. Note that make sure you document the custom port if you change the default values. Click on Next.

  18. On the Select the installation location page, accept the selected installation location or specify a custom location. Click on Next.

  19. On the Microsoft Update page select your preferred option. Click on Next.

  20. On the Help improve Microsoft System Center Orchestrator page select your preferred options. Click on Next.

  21. Review the Installation summary page. Click on Install to start the installation.

  22. On successful installation you are presented with final configuration options as follows:

    • Launch Windows Update

    • Visit System Center Orchestrator Online

    • When Setup closes, start the Runbook Designer

This completes the installation steps.

How it works...

Installing SCORCH in single server deployment mode is very simple. The most important aspect is to plan and configure all the prerequisites before you start the actual installation.

The installation requires a number of options, which the wizard guides you throughout the process. The installation creates the Orchestration database and prepares it for use in your deployment. The account specified for the service account is granted the required permission in the database and on the local server.

The following screenshot shows the database permissions granted to the management server service account:

Tip

About service accounts

In our prerequisites we created two service accounts, one for the Management Service and the other for the Runbook service. In a single server deployment only one account is requested, which in our case is the management server service account. The Runbook Server service account will be used for additional Runbook Servers and is a best practice to separate the two accounts as they are granted different rights in the database. An additional benefit of using two or more accounts is to reduce the risk of a single point of failure for all service components.

There's more...

There is one additional configuration you must perform post installation on the Management Server.

Enabling network discovery is applicable to the Orchestrator database Runbook Designer role. Perform the following steps to enable network discovery:

  1. In control panel navigate to Network and Sharing | Change advanced sharing settings | Expand the Domain profile | Turn on network discovery.

  2. Click on Save changes.

Enabling network discovery enables auto-population of fields, which requires the selection of a computer name when creating Runbooks.

See also

The official online documentation is updated regularly and should be a point for reference at http://technet.microsoft.com/en-us/library/hh420371.aspx.

 

Installing the Management Server in a multiserver deployment


SCORCH features and components can be installed on a single server or across multiple servers. The multi-server deployment requires you to perform the installation in a specific order. The first server you must install is the Management Server which requires a supported instance of Microsoft SQL Server. This recipe provides the steps for installing the SCORCH Management Server.

Getting ready

You must plan to review the Planning the Orchestrator deployment recipe before performing the steps in this recipe. There are a number of dependencies in the Planning the Orchestrator deployment recipe, which you must perform in order to successfully complete the tasks in this recipe.

The authors assume that you have access to all the installation media and the user account performing the installation, has administrative privileges on the server nominated for the SCORCH deployment.

The example deployment in this recipe is based on the following configuration details:

  • Management Server and database server TLSCORCH01 on the same machine

  • SCORCH SP1

  • Microsoft SQL Server 2012

  • Service account created in Active Directory: SCO_MGTSVCA

  • Administrative users group created in Active Directory: SCO_ADMINS

How to do it...

The following figure provides a visual summary and order of the tasks you need to perform to complete this recipe:

The deployment will be implemented in an Active Directory environment and with the Windows Server 2012 operating system. Perform the following steps to deploy a SCORCH Management Server in a multi-server deployment scenario:

  1. Install a supported Windows Server operating system and join the server to the Active Directory domain in scope of the SCORCH deployment.

  2. Add the service accounts and the SCORCH Administrators group to the local administrators group on the SCORCH server.

  3. On the SCORCH server enable the following feature:

    • Feature: .NET Framework 3.5 SP1, you must specify a source files for .NET Framework 3.5 SP1 in the case of Windows Server 2012 ensure that the DVD for Windows Server 2012 is loaded

  4. Install .NET Framework 4 if the operating system version is lower than Windows Server 2012 (.NET Framework 4x is already part of Windows Server 2012).

  5. Install a supported version of Microsoft SQL Server. In our example we will install Microsoft SQL Server 2012 standard edition with Service Pack 1. The following are the minimum options required for the installation:

    • Instance features: Database engine services

    • Share Features: Management tools—Basic

    • Collation: SQL_Latin1_General_CP1_CI_AS

    • Authentication Credentials: Windows Authentication (recommended)

  6. Insert or mount the SCORCH installation media on the server. Log on with a user account with administrative rights.

  7. Launch the installation using the SetupOrchestrator.exe file.

  8. On the splash screen under Orchestrator click on Install under the System Center 2012 Orchestrator Setup section on wizard page.

  9. On the Product Registration page enter your organization details and the product key. Click on Next.

  10. Review the Please read this License Terms page and accept to continue with the installation. Click on Next.

  11. On the Select features to install wizard page uncheck all options (the only option checked should be the mandatory Management Server). Click on Next.

  12. On the Configure the service account page type the user account you created for the management server service account and password. Click on Test to verify the details. Click on Next.

  13. On the Configure the database server page type the server name and if applicable the instance of SQL where the Orchestration database will be created. Click on Next.

  14. On the Configure the database page, ensure that new database is selected and the default name Orchestrator for the database. Click on Next.

  15. On the Configure Orchestrator users group page, browse and specify the Active Directory group you created for the SCORCH administrators role. Click on Next.

  16. On the Select the installation location page, accept the selected installation location or specify a custom location. Click on Next.

  17. On the Microsoft Update page select your preferred option. Click on Next.

  18. On the Help improve Microsoft System Center Orchestrator page select your preferred options. Click on Next.

  19. Review the Installation summary page. Click on Install to start the installation.

  20. On successful installation you are presented with final configuration options as follows:

    • Launch Windows Update

    • Visit System Center Orchestrator Online

This completes the installation steps for the SCORCH Management Server in the multi-server deployment.

How it works...

The installation wizard guides you through the required settings. Once all the prerequisites are properly configured, the installation process creates the Orchestration database and installs the required program files for the Management Server feature.

The account specified for the service account is granted the required permission in the database. The following screenshot shows the database permissions granted to the management server service account:

See also

The How it works… section of the Installing a single server deployment recipe.

 

Installing the Runbook Server in a multiserver deployment


SCORCH features and components can be installed on a single server or across multiple servers. The multi-server deployment requires you to perform the installation in a specific order. The first server you must install is the Management Server which requires a supported instance of Microsoft SQL Server. This recipe discusses installation of the Runbook Server component. You need at least one Runbook Server in a multi-server deployment.

Getting ready

You must plan to review the Planning the Orchestrator deployment recipe before performing the steps in this recipe. There are a number of dependencies in the Planning the Orchestrator deployment recipe, which you must perform in order to successfully complete the tasks in this recipe.

The authors assume that you have access to all the installation media and the user account performing the installation, has administrative privileges on the server nominated for the SCORCH deployment. You must also install a Management Server before you can install the Runbook Server.

The example deployment in this recipe is based on the following configuration details:

  • Management Server and database server called TLSCORCH01 is already installed

  • SCORCH SP1

  • Service account created in Active Directory: SCO_RBSSVCA

How to do it...

The following figure provides a visual summary and order of the tasks you need to perform to complete this recipe:

The deployment will be implemented in an Active Directory environment with the Windows Server 2012 operating system. Perform the following steps to deploy SCORCH Runbook Server in a multi-server deployment:

  1. Install a supported windows server operating system and join the server to the Active Directory domain in scope of the SCORCH deployment.

  2. Add the service accounts and SCORCH Administrators group to the local Administrators group on the SCORCH Runbook Server.

  3. On the SCORCH server enable the following feature:

    • Feature: .NET Framework 3.5 SP1, you must specify a source files for .NET Framework 3.5 SP1 in the case of Windows server 2012 and ensure that the DVD for windows server 2012 is loaded

  4. Install .NET Framework 4 if the operating system version is lower than Windows Server 2012 (.NET Framework 4x is already part of Windows Server 2012).

  5. Insert or mount the SCORCH installation media on the Server. Log on with a user account with administrative rights.

  6. Launch the installation using the SetupOrchestrator.exe file.

  7. On the splash screen under Standalone installations. Click on Runbook Server.

  8. On the Product Registration page enter your organization details and the product key. Click on Next.

  9. Review the Please read this License Terms page and accept to continue with the installation. Click on Next.

  10. On the Configure the service account page type the user account you created for the runbook server service account and password (In our scenario SCO_RBSSVCA). Click on Test to verify the details. Click on Next.

  11. On the Configure the database server page type the server name and if applicable the instance of SQL where the Orchestration database is installed. Click on Next.

  12. On the Configure the database page, ensure that existing database is selected and the default name Orchestrator or your custom name for the database is selected. Click on Next.

  13. On the Select the installation location page, accept the selected installation location or specify a custom location. Click on Next.

  14. On the Microsoft Update page select your preferred option. Click on Next.

  15. On the Help improve Microsoft System Center Orchestrator page select your preferred options. Click on Next.

  16. Review the Installation summary page. Click on Install to start the installation.

  17. On successful installation you are presented with final configuration options as follows:

    • Launch Windows Update

    • Visit System Center Orchestrator Online

This completes the installation steps for the SCORCH Management Server in the multi-server deployment.

How it works...

The installation wizard guides you through the required settings. Once all the prerequisites are properly configured, the installation process installs the required program files for the Runbook Server feature.

The account specified for the service account is granted the required permission in the database. The following screenshot shows the database permissions granted to the runbook server service account:

See also

The How it works… sections of the following recipes provide additional relevant information:

  • The Installing a single-server deployment recipe

  • The Installing a Management Server in a multiserver deployment recipe

 

Installing the Orchestration Console and the Web Service server in a multi server deployment


SCORCH features and components can be installed on a single server or across multiple servers. The multi-server deployment requires you to perform the installation in a specific order. The first server you must install is the Management Server which requires a supported instance of Microsoft SQL Server. This recipe discusses installation of the Orchestration Console and Web Service server component. You need at least one Orchestration Console and Web Service server in a multi-server deployment.

Getting ready

You must plan to review the Planning the Orchestrator deployment recipe before performing the steps in this recipe. There are a number of dependencies in the Planning the Orchestrator deployment recipe, which you must perform in order to successfully complete the tasks in this recipe.

The authors assume you have access to all the installation media and the user account performing the installation, has administrative privileges on the server nominated for the SCORCH deployment. You must also install a Management Server before you can install the Orchestration Console and Web Service server.

The example deployment in this recipe is based on the following configuration details:

  • Management Server and database server called TLSCORCH01 is already installed

  • SCORCH SP1

  • Service account created in Active Directory: SCO_MGTSVCA

How to do it...

The following figure provides a visual summary and order of the tasks you need to perform to complete this recipe:

The deployment will be implemented in an Active Directory environment and with the Windows Server 2012 operating system. Perform the following steps to deploy the SCORCH Orchestration Console and Web Service in a multi-server deployment:

  1. Install a supported windows server operating system and join the server to the Active Directory domain in scope of the SCORCH deployment.

  2. Add the service accounts and SCORCH Administrators group to the local Administrators group on the SCORCH Orchestration Console and Web Service server.

  3. On the SCORCH Orchestration Console and Web Service server enable the following role and feature:

    • Role: Web Server (IIS) (default settings)

    • Feature: .NET Framework 3.5 SP1, you must specify a source files for .NET Framework 3.5 SP1 in the case of Windows Server 2012 and ensure that the DVD for Windows Server 2012 is loaded

  4. Install .NET Framework 4 if the operating system version is lower than Windows Server 2012 (.NET Framework 4x is already part of Windows Server 2012).

  5. Optionally install Silverlight. After the SCORCH installation you will be prompted to install Silverlight if you run the console on the server.

  6. Insert or mount the SCORCH installation media on the Server. Log on with a user account with administrative rights.

  7. Launch the installation using the SetupOrchestrator.exe file.

  8. On the splash screen under Standalone installations click on Orchestration Console and Web Service.

  9. On the Product Registration page enter your organization details and the product key. Click on Next.

  10. Review the Please read this License Terms page and accept to continue with the installation. Click on Next.

  11. On the Configure the service account page type the user account you created for the management server service account and password (In our scenario SCO_MGTSVCA). Click on Test to verify the details. Click on Next.

  12. On the Configure the database server page type the server name and if applicable, the instance of SQL where the Orchestration database is installed. Click on Next.

  13. On the Configure the database page, ensure that existing database is selected and the default name Orchestrator or your custom name for the database is selected. Click on Next.

  14. On the Configure the ports for the web services page leave the default options (81 and 82) or provide your custom options. Note that If you change these ports from their default, make sure you document the custom port options. Click on Next.

  15. On the Select the installation location page, accept the selected installation location or specify a custom location. Click on Next.

  16. On the Microsoft Update page select your preferred option. Click on Next.

  17. On the Help improve Microsoft System Center Orchestrator page select your preferred options. Click on Next.

  18. Review the Installation summary page. Click on Install to start the installation.

  19. On successful installation you are presented with final configuration options as follows:

    • Launch Windows Update

    • Visit System Center Orchestrator Online

This completes the installation steps for the SCORCH Orchestration Console and Web Service server in the multi-server deployment.

How it works...

The installation wizard guides you through the required settings. Once all the prerequisites are properly configured, the installation process installs the required program files for the Orchestration Console and Web Service feature.

The account specified for the service account is used to connect the Orchestration Console and Web Service to the specified SCORCH database.

The installation creates and configures two websites and their required settings in the local installation of the Internet Information Services (IIS).The following screenshot shows the two sites created by the installation wizard:

See also

The following recipes provide additional relevant information:

  • The Installing a single-server deployment recipe

  • The Installing a Management Server in a multiserver deployment recipe

  • The Installing a Runbook Server in a multiserver deployment recipe

 

Installing the Runbook Designer in a multiserver deployment


SCORCH features and components can be installed on a single server or across multiple servers. The multi-server deployment requires you to perform the installation in a specific order. The first server you must install is the Management Server which requires a supported instance of Microsoft SQL Server. This recipe discusses installation of the Runbook Designer component. You need at least one Runbook Designer in order to create and manage Runbooks.

Getting ready

You must plan to review the Planning the Orchestrator deployment recipe before performing the steps in this recipe. There are a number of dependencies in the Planning the Orchestrator deployment recipe, which you must perform in order to successfully complete the tasks in this recipe.

The authors assume that you have access to all the installation media and the user account performing the installation, has administrative privileges on the server or client nominated for the SCORCH deployment.

You must also optionally install a Management Server before you install the Runbook Designer server. Though the Runbook Designer can be installed without a Management Server present, you won't be able to use the Runbook Designer for SCORCH until a Management Server with a corresponding database is installed.

The example deployment in this recipe is based on the following configuration details:

  • Management Server and database server called TLSCORCH01 is already installed

  • SCORCH SP1

  • Operating system for the Runbook Designer: Windows 7

How to do it...

The following figure provides a visual summary and order of the tasks you need to perform to complete this recipe:

The deployment will be implemented in an Active Directory environment and with the Windows 7 operating system. Perform the following steps to deploy a SCORCH Runbook Designer in a multi-server deployment:

  1. Install a supported Runbook Designer operating system and join the client to the Active Directory domain in scope of the SCORCH deployment.

  2. On the SCORCH machine nominated for the Runbook Designer enable the following role and feature:

    • Feature: .NET Framework 3.5 SP1

  3. Optionally install Silverlight. After the SCORCH installation you will be prompted to install Silverlight if you run the console.

  4. Insert or mount the SCORCH installation media on the Runbook Designer nominated machine. Log on with a user account with administrative rights.

  5. Launch the installation using the SetupOrchestrator.exe file.

  6. On the splash screen under Standalone installations. Click on Runbook Designer.

  7. On the Product Registration page enter your organization details and the product key. Click on Next.

  8. Review the Please read this License Terms page and accept to continue with the installation. Click on Next.

  9. Verify there are no errors on the Prerequisites page. Click on Next.

  10. On the Select the installation location page, accept the selected installation location or specify a custom location. Click on Next.

  11. On the Microsoft Update page select your preferred option. Click on Next.

  12. On the Help improve Microsoft System Center Orchestrator page select your preferred options. Click on Next.

  13. Review the Installation summary page. Click on Install to start the installation.

  14. On successful installation you are presented with final configuration options as follows:

    • Launch Windows Update

    • Visit System Center Orchestrator Online

This completes the installation steps for the SCORCH Runbook Designer in the multi-server deployment.

How it works...

The installation wizard guides you through the required settings. Once all the prerequisites are properly configured, the installation process installs the required program files for the Runbook Designer.

The Runbook Designer is your interface to the SCORCH deployment for the purpose of creating and managing Runbooks.

There's more...

The Runbook Designer is similar to a standalone console and can be used to connect to any Management Server if the user running the designer has access rights delegated.

Connecting to the Management Server

When the Orchestrator Runbook Designer is launched for the first time, an attempt is made to connect to a Management Server on the machine. In our recipe we do not have the Management Server installed locally. To connect to the Management Server, for example TLSCORCH01, perform the following steps:

  1. Navigate to Start | All Programs | Microsoft System Center 2012 | Orchestrator | Runbook Designer (click on OK on the warning message if this is the first time you launch the Runbook Designer).

  2. Select Actions from the menu bar and click on Connect.

  3. Type the Management Server name in the Computer field to connect to the Management Server of the multi- server deployment SCORCH environment in scope.

Orchestration Console URL

The Runbook Designer has a short-cut option to connect to and launch the Web Service server console. You must configure the correct URL for the console by performing the following steps:

  1. Navigate to Start | All Programs | Microsoft System Center 2012 | Orchestrator | Runbook Designer.

  2. Select Options from the menu bar and click on Orchestration Console Configure. Type the URL of the web console with the port specified at the time of installation (port 82 by default).

  3. Test the console using the Orchestrator Console icon in the Runbook Designer console. Note that you will be prompted to install Silverlight if it is not already installed on the machine.

See also

The following recipes provide additional relevant information:

  • The Installing a single-server deployment recipe

  • The Installing the Management Server in a multiserver deployment recipe

  • The Installing the Runbook Server in a multiserver deployment recipe

  • The Installing the Orchestration Console and the Web Service server in a multiserver deployment recipe

About the Authors

  • Samuel Erskine

    Samuel Erskine is a Systems Management Sr Technical Specialist, Trainer and Author , focused on System Center and MS Cloud technologies. Sam is the content designer and lead author of three Microsoft System Center Cookbooks and co-author of two System Center Unleashed books. He’s also a Microsoft MCT , MVP and a regular speaker at community user groups and conferences worldwide.

    Browse publications by this author
  • Andreas Baumgarten

    Andreas Baumgarten is a Microsoft MVP and works as an IT Architect with the German IT service provider H&D International Group. He has been working as an IT professional for more than 20 years. Microsoft technologies have always accompanied him, and he can also look back on more than 14 years' experience as a Microsoft Certified Trainer.

    Since 2008, he has been responsible for the field of Microsoft System Center technology consulting and ever since has taken part in Microsoft System Center Service Manager (2010, 2012, 2012 R2 and 2016); additionally, he has participated in the Microsoft System Center Technology Adoption Program with H&D since many years.

    With his deep inside-technology know-how and his broad experience across the Microsoft System Center product family and IT management, he now designs and develops private and hybrid cloud solutions for customers all over Germany and Europe.

    In July 2017, he was awarded the Microsoft Most Valuable Professional (MVP) title for System Center Cloud and Datacenter Management for the sixth year in a row.

    Browse publications by this author
  • Steve Beaumont

    Steve Beaumont has worked for more years than he cares to admit within IT, starting with desktop support. He is now the Product Development Director of PowerONPlatforms and a Microsoft MVP within the Cloud and Datacenter Management area, where he helps organizations realize the benefits of the hybrid cloud. He is also a co-author of the Microsoft System Center 2012 Service Manager, Orchestrator and Operations Manager cookbooks.

    His passion for everything about System Center, Azure and IT systems management reflects through all areas of his work, presentation and day-to-day life in the form of new and innovative solutions brought to market by PowerONPlatforms.

    Browse publications by this author
Book Title
Unlock this book and the full library for FREE
Start free trial