ITQ’s End User Portal for System Center Orchestrator (EUPSCO) – Part 2: Prerequisites

In our previous post (ITQ’s End User Portal for System Center Orchestrator (EUPSCO) – Part 1: Introduction), we were introduced to the ITQ End User Portal for System Center Orchestrator. In this post we follow Damian Flynn’s steps on the Prerequisites.

The following is a re-write (to accommodate screenshots) from Damian Flynn’s article, with the addition of screenshots by me.

 

EUPSCO Prerequisites

Prior to installing the End User Portal, we need to install some prerequisites. It is important to note that the End User Portal does not have an installer, so manual steps are required.

In my installation example, I am using a dedicated server joined to my domain, that is also running all Orchestrator features (Management Server, Runbook Server, Orchestrator Console and Web Service, and Runbook Designer) including the SQL Server that is running the Orchestrator database. Basically, it’s a completely self-contained server.

Though it is not required to utilize the same SQL Server, or same SQL Instance, or even the same server that Orchestrator is installed on; it’s the simplest way to have a self-contained method for delivering self-service utilizing Orchestrator Runbooks.

According to the ITQ forum, here are the various system requirements:

Web Server

  • CPU: 2 Core (minimum) @ 2.5 GHz
  • RAM: 2 GB (minimum)
  • OS: Windows 7 x64, or Windows 2008 R2 x64 or later
  • Other:
    • Internet Information Services (IIS) 7 (or later)
    • .NET Framework 4.5

Database Server

  • CPU: 2 Core (minimum) @ 2.5 GHz
  • RAM: 2 GB (minimum)
  • Other:
    • SQL Server 2008 Express (or better)

To start the installation (in my example on Windows Server 2012 R2), we need to install the .NET Framework 4.5. On Windows Server 2012 R2, this is included as a feature. We also need to install the Web Server (IIS) Role to host the Portal. To do this simply, we can use PowerShell.

Start by launching an Administrative PowerShell console by right-clicking on PowerShell and choose “Run As Administrator“.

PowerShell - RunAs Admin

In the command prompt, type: Import-Model ServerManager and then press Enter.

PowerShell - Import-Module ServerManager

After the ServerManager module has been imported, type the following command as one line, then press Enter. The installation will begin immediately.

Add-WindowsFeature Web-Default-Doc, Web-Dir-Browsing, Web-Http-Errors, Web-Static-Content, Web-Http-Redirect, Web-Http-Logging, Web-Stat-Compression, Web-Dyn-Compression, Web-Basic-Auth, Web-Digest-Auth, Web-Windows-Auth, Web-Net-Ext45, Web-ASP-Net45, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Mgmt-Console

PowerShell - WebServer Installation

Once the installation is complete, close the PowerShell command window.

PowerShell - WebServer Installation Complete

This will complete the installation of all prerequisites required. For reference, here is a list of the Features that are installed. Pay specific attention to the Features that are highlighted.

PowerShell - All Installed Features

In our next post, we will discuss the Service Accounts required.

%d bloggers like this: