70-247 Series: Part 9

Installing Orchestrator

In this blog post I will cover the steps required to install Orchestrator in a HA configuration. The following servers will be deployed:

  • ORCMGMT – Orchestrator Management Server
  • ORC1 – Runbook Server and Web Console Server
  • ORC2 – Runbook Server and Web Console Server

    The Web Console component can be load balanced, the Runbook server component does not require load-balancing.

    The steps I will complete to do this are:

    1. Create Orchestrator Database Instance (Already completed outside of this procedure, you can use an existing instance if you wish)
    2. Create Orchestrator Service Account
    3. Create Orchestrator Users Group
    4. Install Management Server
    5. Install prerequisites
    6. Run setup
    7. Install combined Runbook Server and Web Service
      1. Install prerequisites
      2. Install Runbook server
      3. Install Web console
    8. Repeat step 7 to install second Runbook Server and Web Service
    9. Verify Runbook Servers

    Alright, let’s get started.

    Create Service Account

    clip_image001

    No permissions are required, the logon as a service right is assigned by the Orchestrator installation wizard.

    Create Orchestrator Users Group

    clip_image002

    Install Orchestrator Management Server

    Install Pre-requisites

    The required prerequisites are:

  • .Net Framework 4.0
  • .Net Framework 3.5.1

    clip_image003

    Run Setup

    This server will serve as a Management server.

    clip_image004 clip_image005 clip_image006

    See below, only the Management server is selected. The other roles will be installed on separate servers and the web service will be load balanced.

    clip_image007

    clip_image008

    clip_image009

    clip_image010

    clip_image011

    clip_image012

    The remaining steps displayed below do not require any important configuration steps so I have reduced the size of the screenshots.

    clip_image013 clip_image014 clip_image015
    clip_image016 clip_image017  

    Install First Orchestrator Runbook Server and Web Service Server

    Install Prerequisites

    The required prerequisites are:

  • .Net Framework 4.0
  • .Net Framework 3.5.1 and IIS

    clip_image018

    Install Runbook Server

    clip_image019

    clip_image005[1] clip_image006[1] clip_image008[1]

     

    clip_image009[1]

    clip_image010[1]

    All future components added will use the existing database.

    clip_image020

     

    clip_image014[1] clip_image015[1] clip_image016[1]
    clip_image021 clip_image022  

    Install Web Service Server

    clip_image023

    clip_image005[2] clip_image006[2] clip_image008[2]

     

    clip_image009[2]

    clip_image010[2]

    clip_image020[1]

     

    clip_image013[1] clip_image014[2] clip_image016[2]
    clip_image024 clip_image025  

    Install Second Runbook Server and Web Service Server

    The process for installing the second server is identical to installing the first server.

    Verify Runbook Servers

    Once all the Runbook servers are installed, it's a good idea to verify them in the Runbook Designer. You can install the Runbook Designer on any Server or Client. In this instance, I have installed it on the Management Server and I will also install it on a client.

    clip_image026

    • Popular posts from this blog

    Get local computer UUID/GUID using Windows Powershell

    Use the following syntax to get the local computer's UUID/GUID using Windows Powershell: get-wmiobject Win32_ComputerSystemProduct  | Select-Object -ExpandProperty UUID Add -computername after the WMI class to find a remote computer's UUID, example: get-wmiobject Win32_ComputerSystemProduct -computername RANTPC | Select-Object -ExpandProperty UUID
    Read more

    gPLink and gPOptions

    gPLink is a property for sites, domains and organisational units that contains a prioritised list of GPOs linked to the node. gPOptions is a property that contains all Block Policy Inheritance settings for the node. To manage GPO links on a node, you must have read and write access to the gPLink and gPOptions properties.
    Read more

    PSLoggedOn Getting Started on Windows Server 2008 R2

    Image
    PSLoggedOn is a tool I downloaded to allow me to find out which computers a user is currently logged on to. Getting it up and running wasn’t exactly easy. I’m running a Windows Server 2008 R2 test environment. The first error I encountered was: Error browing network: The list of servers for this workgroup is not currently available. Note: I kept the spelling mistake from the error message to make it easier to find via search engines. To get past this error, you have to enable and start the “Computer Browser” service. Then I started getting the error telling me that the Administrator is not logged on. That’s simply not true because I am logged onto another server (Name: ELARA): I turned the firewall OFF OFF OFF (It is a test network after all). I enabled Network Discovery and to do that I went on a service starting frenzy: DNS Client, Function Discovery Resource Publication, SSDP Discovery, and UPnP Device Host, Computer Browser After all that, I ran the script against the se
    Read more