A WordPress.com site dedicated to System Center and Cloud Management

Posts tagged ‘System Center Orchestrator’

SCORCH Technical Preview in a LAB – Installation Guide (Install Orchestrator)

Install System Center Orchestrator Technical Preview

In my Lab example, I am using the following:

  • Windows Server Technical Preview
  • SQL Server 2014
  • Web Server (IIS)

These have been setup as per my previous guides for the OS and SQL setup.

IMPORTANT: In order to evaluate the System Center Technical Preview, you MUST be using the Windows Server Technical Preview, and SQL Server 2014; as per the following TechNet article: http://technet.microsoft.com/en-us/library/dn806369.aspx.


Install SCORCH

Start by copying the EXE file into the SCORCH VM. As of this writing, the Technical Preview EXE is labelled as “en_system_center_technical_preview_orchestrator_x86_x64_5650402.exe“.

Start by running the EXE. On the Directory screen, choose the location to extract the installation files, then click OK.

SCORCH vNext - 01 - Extract Directory

On the Extraction Complete dialog, click OK.

SCORCH vNext - 02 - Extract Complete

Once the files are extracted, start the installation by running SetupOrchestrator.exe.

On the splash screen click the Install link.

SCORCH vNext - 03 - Splash Screen

On the Product Registration screen, fill in the Name, Organization and Product Key fields, and click Next.

SCORCH vNext - 04 - Product Registration

Read and accept the License Terms, and then click Next.

SCORCH vNext - 05 - License Terms

On the Select Features screen, select what you want to install. In this lab example, we are installing all features onto the same server.

SCORCH vNext - 06 - Select Features

On the Prerequisites screen, if you are missing .NET and/or IIS, the installer can take care of it all for you. Just select the “Activate .NET and IIS features/roles” option, then click Next.

SCORCH vNext - 07 - Prerequisites

Once all the prerequisites are installed, click Next.

SCORCH vNext - 08 - Prerequisites Installed

Next you need to provide a Service Account for running the Runbooks, and accessing remote systems. Note that the account must have “Log on as a service” rights. Enter the account details, and then click the Test button.

Once the credentials have been tested successfully, you will be able to click Next.

SCORCH vNext - 09 - Service Account

Now you need to configure the database. Provide the server and instance, and click the Test Database Connection button.

Only once the database connection has been successfully tested will you be able to click the Next button.

SCORCH vNext - 10 - Database Server

Now you can also specify the database name. In this lab example we will accept the defaults and click Next.

SCORCH vNext - 11 - Configure Database

Now we need to configure the Orchestrator User Group. This group will have Administrative access to Orchestrator. You can locate and use an existing Security Group from Active Directory. Specify a User Group and click Next.

SCORCH vNext - 12 - Users Group

On the Web Services screen, you have the opportunity to change the ports used. For this lab example we will accept the defaults and click Next.

SCORCH vNext - 13 - Web Services

You can also change the installation location. For example, if you have a dedicated drive in the server for the Operating System, and a second drive for the middleware. Make the appropriate modifications if applicable, and then click Next.

SCORCH vNext - 14 - Installation Location

Just as in System Center 2012, you can use Microsoft Update to find updates for the product. In a Production environment, you would probably not want to do this, since there will more than likely be Change Management controls around updating/patching. In this lab example, I am not going to enable Microsoft Updates for the product, so that in the future I will be able to document the update/upgrade process in detail.

SCORCH vNext - 15 - Microsoft Update

Next, you can choose if you want to participate in the CEIP program. In a Production environment, this will probably not be accepted, as there may be some concern over private/personal data. In a lab/non-production environment though, I would personally choose to be a part of the program, because the information collected by Microsoft aids them in improving the product. If no one was willing to participate, then there would be no improvements.

SCORCH vNext - 16 - CEIP

Finally, review the information on the Summary screen, and click Install.

SCORCH vNext - 17 - Summary

Once the installation is complete, you can select/de-select any of the listed checkboxes, and then click Close.

SCORCH vNext - 18 - Setup Complete

Congratulations, you have now successfully installed the System Center Orchestrator Technical Preview.

As you can see from the About screen, the version of SCORCH, even though it shows “System Center 2012 R2”, the version is: 7.2.503.0 (whereas the actual 2012 R2 product is version

SCORCH vNext - 19 - About

At this point, I haven’t noticed anything new/different with the product. However, as the product is updated, I will keep you informed of any interesting and important changes.


For further information about the System Center Technical Preview, here is the link to the Features Removed In System Center Technical Preview, and the Release Notes For System Center Technical Preview.

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

In our previous post (ITQ’s End User Portal for System Center Orchestrator (EUPSCO) – Part 4: Database), we covered setting up/preparing the Prerequisites. In this post we follow Damian Flynn’s steps on the Portal Installation.

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


Portal Installation

Now that we have everything setup, we can now perform the installation of the End User Portal.

Start by downloading the latest copy of the End User Portal from the ITQ website (http://www.eupsco.nl/Downloads). At of the time of this writing, the latest version is Version 1.33 build 20130722.1 Released on
Monday July 22 2013. The files are contained within a .ZIP file.

Portal Download

After you have downloaded the files, extract them to a general location. I have extracted my to \Downloads\EUPSCO_201307221. Since we are performing this installation on the same server that Orchestrator is installed on, Internet Information Services (IIS) is already installed. We could use the “Default Website”, however, for purpose of demonstration, we will create a new IIS Website for the End User Portal.

Start by launching Internet Information Services (IIS) Manager.

Launch IIS Manager

In the Connections Pane, expand the Server and select Application Pools.

Connections - Application Pools

Right-click on Application Pools and choose Add Application Pool.

Add Application Pool

On the Add Application Pool dialog, provide a name for the pool. In my lab example, I am using EUPSCO. Ensure that the .NET CLR Version is set to v4.0.xxxxx, then click OK to create the new Application Pool.

Add Application Pool

In the details view, you should see our newly created Application Pool.

Application Pools - Newly Created App Pool

Right-click our newly created Application Pool and select Advanced Settings.

Application Pool - Advanced Settings

On the Advanced Settings dialog, find the Identity property and select it.

Advanced Settings - Identity

Click on the “…” button to display the Application Pool Identity dialog. Select the Custom Account option, and click the Set button.

Application Pool Identity - Custom Account - Set

In the Set Credentials dialog, provide the details for the Service Account we created, then click OK. Be sure to include DOMAIN\UserName. In my lab example, this is SC\EUPSCO_AppPool.

Set Credentials

Click OK to close the Application Pool Identity dialog, and OK again to close the Advanced Settings dialog.

Back in Internet Information Services (IIS) Manager within the Connections Pane, right-click on Sites and select Add Website.

Sites - Add Website

On the New Website dialog, provide a name for the new website. In my lab example, I used “EUPSCO”. Then click the Select… button for the Application Pool.

Add Website - Site Name

On the Select Application Pool dialog, choose the Application Pool that we previously created from the drop-down list, then click OK.

Select Application Pool

Back on the Add Website dialog, provide the Physical Path to the extracted files you downloaded. In my lab example, even though I extracted the .ZIP file to the \Downloads\ folder, I also copied the extracted files to the default Internet Information Services (IIS) directory; namely C:\inetpub\wwwroot\. Click OK to finish creating the new website.

Add Website - Physical Path

In the Connections pane, select the newly created website. In the Features View pane double-click on Authentication.

Website - Features View - Authentication

On the Authentication settings, set all Authentication Methods to Disabled, and set Windows Authentication to Enabled.

Website - Features View - Authentication Settings

We now have the Website configuration completed. We still have some Application Settings to configure to connect it to Active Directory for authentication, connect it to the Orchestrator Web Service, and to connect it to the database that we created.

In our next post, we will discuss the Portal Configuration required.

Tag Cloud

%d bloggers like this: