SCO features and components can be installed on a single server or across multiple servers. The multiserver 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 the installation of the Runbook Server component. You need at least one Runbook Server in a multiserver deployment.

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 SCO 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 SVTGSCO01 is already installed
• The service account created in Active Directory: SCO_RBSSVCA

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 2016 operating system. Perform the following steps to deploy SCO Runbook Server in a multiserver deployment:

1. Install a supported Windows Server operating system, and join the server to the Active Directory domain in the scope of the SCO deployment.
2. Add the service accounts and SCO administrators group to the local administrator's group on the SCO Runbook Server.
3. On the SCO server, enable the .NET Framework 3.5 SP1 feature.
4. Insert or mount the SCO installation media on the server. Login with a user account with administrative rights.
5. Launch the installation using the SetupOrchestrator.exe file.

6. Turn on the splash screen under Standalone installations. Click on Runbook Server.
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 click accept to continue with the installation. Click on Next.
9. 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.
10. 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.
11. On the Configure the database page, ensure that Existing database is selected and the default name is Orchestrator , or your custom name for the database is selected. Click on Next.
12. On the Select the installation location page, accept the selected installation location or specify a custom location. Click on Next.
13. On the Microsoft Update page, select your preferred option. Click on Next.
14. On the Help improve Microsoft System Center Orchestrator page, select your preferred options. Click on Next.
15. Review the Installation summary page. Click on Install to start the installation.
16. On the 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 SCO Management Server in the multiserver deployment.

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:

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

• Installing a single server deployment recipe
• Installing a Management Server in a multiserver deployment recipe