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

Archive for the ‘SCORCH (Orchestrator)’ Category

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 7: EUPSCO First Launch

In our previous post (ITQ’s End User Portal for System Center Orchestrator (EUPSCO) – Part 6: Portal Configuration), we covered the post-install Portal Configuration. In this post we follow Damian Flynn’s steps on the First Launch.

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


System Center 2012 R2 – Orchestrator: EUPSCO First Launch

Now that the installation and configuration is completed, we can now check/test the website to ensure everything is working.

If you created a new Website in Internet Information Services (IIS), you may have to start the website (as it is Stopped by default). Launch the Internet Information Services (IIS) Manager, expand ServerName > Sites, and select the website. Then right-click on the website and select Manage Website > Start.

EUPSCO - Manage Website - Start

One the website has been started, open a browser and navigate to the site. In my lab example this is http://EUPSCO/. You can also use http://localhost/.

EUPSCO Home Page

It may take a few minutes to load the site the first time, because Internet Information Services (IIS) needs to compile the code before loading it.

A few final notes.

You may be prompted to authenticate (login) to the site, as it is not listed in the Trusted Sites list. Also, by default the Domain Administrator is the administrator account for the portal. If you want to change this, open the Web.Config file and look for the key entry labelled “AdminUserIDs”.

WebConfig - AdminUserIDs

That’s it for this post series. In the future I will post articles about creating Orchestrator Runbooks.

Feel free to comment, rate the article, or contact me with requests for future articles.

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

In our previous post (ITQ’s End User Portal for System Center Orchestrator (EUPSCO) – Part 5: Portal Installation), we covered the installation of the End User Portal. In this post we follow Damian Flynn’s steps on the post-installation Portal Configuration.

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


Portal Configuration

To perform the Portal Configurations, launch Windows Explorer and navigate to the location containing the extracted website files. Locate the Web.Config file.

WebConfig File

Open the Web.config file in a suitable editor (i.e. Notepad).

WebConfig File - Open In Editor

Search the Web.Config file for a key entry labelled “DomainSearchRoot“. Change this entry from “DC=test,DC=local”, to match your Active Directory domain. In my lab example, my domain is called “SC.LAB“, so my key entry is “DC=SC,DC=LAB“.


Next search the Web.C0nfig file for a key entry labelled “OrchestratorServiceURL“. Change this entry from “http://%5BSCO SERVERNAME]:81/Orchestrator2012/orchestrator.svc”, to match your Orchestrator Web Service URL. In my lab example, this is “http://EUPSCO.SC.LAB:81/Orchestrator2012/Orchestrator.svc“.

Orchestrator Web Service URL

Finally, search the Web.Config file for a key entry labelled “Database” within the ConnetionString code section. We need to change the DataSource and InitialCatalog references to connect to the database we created previously. In my lab example, the DataSource is EUPSCO.SC.LAB.

IMPORTANT: If you are using a Named SQL Server Instance, then your DataSource should be “ServerName.DOMAIN\InstanceName“. Since I created a Named SQL Instance in my lab, instead of using the default instance, my DataSource is “EUPSCO.SC.LAB\EUPSCO“.

Database ConnectionString

In our next post, we will discuss the End User Portal First Launch and what to expect.

Tag Cloud

%d bloggers like this: