How to Install Microsoft SCOM 2012 R2

This tutorial will go through the steps of installing Microsoft System Centre Operations Manager 2012R2 ( also known as Microsoft SCOM 2012R2 ). SCOM is used to monitor the health and performance of servers and applications in Microsoft Windows environments.

I recommend using Windows Server 2012R2 and above. If your company is ready for Windows 2016, then I would highly recommend using Windows Server 2016 as the server to install SCOM. This will give your installation longer support life without having to worry about doing a server migration down the track.

For this tutorial, I am using SCOM 2012R2 because I will also have another tutorial on upgrading 2012R2 to SCOM 2016.

Insert or mount the SCOM 2012R2 media. Double click the mounted media.

Select Download the latest updates to the setup program and click Install.

Select all the features and click Next.

You can change the installation location or accept the defaults and click Next.

The Setup wizard cannot continue because we didn’t meet the prerequisites.

Back in the Prerequisites window, we can click the drop down arrow on the right side of the error message to find out what is required to be done to resolve the issue.

In most server installations, the following prerequisites are unlikely to have already been installed.

Report Viewer controls are not installed.

Web Server (IIS) Support role service is not installed

The IIS6 Metabase Compatibility role service is not installed

The ASP.NET role service is not installed.

The Windows Authentication service role is not installed.

The Static Content role service is not installed.

The Default Document role service is not installed.

The Directory Browsing role service is not installed.

The HTTP Logging role service is not installed.

The Request Monitor role service is not installed.

The Request Filtering role service is not installed.

The Static Content Compression role service is not installed.

The IIS Management Console role service is not installed.

The ISAPI and CGI Restrictions are disabled or missing.

The ASP.NET 4.x handler is not registered with IIS.

The HTTP Activation role services is not installed for the .NET Framework 4.x role

Installing most of the prerequisites can be done via Server Manager. In Windows 2016, you can start up Server Manager by firstly clicking the Windows icon on the bottom left corner of the screen. This will bring up the start menu.

Locate and click on the Server Manager icon.

Click on Add roles and features

Click Next

Select Role-based or feature-based installation, then click Next

Select Select a server from the server pool and highlight the server listed, click Next

Locate Web Server (IIS) in the list and select it.

It will prompt with a window asking to Add features that are required for Web Server (IIS)? Make sure Include management tools (if applicable) is selected and click Add Features.

You will see a tick next to Web Server (IIS). Click Next

Click Next

Click Next

Make sure the following Role Services are selected as they are also prerequisites. Then scroll down for more options to select.

Make sure IIS Management Console and IIS 6 Metabase Compatability is selected, then click Next.

Click Install

After the above prerequisite installation, we will go through the SCOM installation steps again.

We can see that the following roles and features are still needed to be added.

Report Viewer controls are not installed.

The ASP.NET role service is not installed.

The Windows Authentication service role is not installed.

The Request Monitor role service is not installed.

The ISAPI and CGI Restrictions are disabled or missing.

The ASP.NET 4.x handler is not registered with IIS.

The HTTP Activation role services is not installed for the .NET Framework 4.x role

In Server Manager, repeat the steps that we have used previously to add the missing pre-requisites as listed above (and in your own installation), except for the Report Viewer controls. Report Viewer controls needs to be downloaded and installed manually.

The link to download the Report View Controls is below. It was given to use in the Prerequisites screen for the Report Viewer Controls missing error :

http://www.microsoft.com/en-au/download/details.aspx?id=29065

Download it and just double-click on it to start the installation.

The Report Viewer Controls also need prerequisites.

We need to get the Microsoft System CLR Types for SQL Server 2012

Go to the following link:

http://www.microsoft.com/en-au/download/details.aspx?id=29065

Scroll down until you see the Microsoft System CLR Types for SQL Server 2012 section. Download the x64 Package (64 bit version) since our SCOM installation is 64 bit.

Install CLR Types package that was downloaded

We can now try to install the Report Viewer Controls again

That should be it for the prerequisites!

Double click on the installer and select Install

For our tutorial, we will select all the features and click on Next

In this tutorial, leave the location as below and click Next

Click Next

Enter a name for the Management group

Select I have read.. and click on Next

Enter the name of the SQL Server that will store the operational database. A SQL Server has already been installed on this server so I will just use localhost for the server name, and I will accept all the other default settings

Then click Next

Put the name of the SQL server that will store the warehouse database. A SQL Server has already been installed on this server, so I will use localhost for the server name and accept all the other default settings.

In the dropdown box, select the available SQL Server instance to host SQL Server Reporting Services (SSRS). In this tutorial, SCOM is the name of SQL Server instance, which in my case is also the server we are currently installing the SCOM application on. In production environments, the SQL Server is usually on a separate machine to the application server.

Choose Default Web Site, then click Next

Select Use Mixed Authentication, then click Next

The best practice is to create a DOMAIN account for each of the SCOM services to use.

The Management Server action account should have its own account, and the same goes for the Data Reader account, and Data Writer account.

The permissions that are required for those accounts are provided in the following TechNet article.

https://technet.microsoft.com/en-us/library/hh457003(v=sc.12).aspx

If you were to use an account that was a domain administrator, you will get a warning as shown in the below screen shots.

In this tutorial, I created an account called SCOMADMIN. I will use it for all the services for the sake of simplicity. However, as mentioned above, you should create different accounts for the different services below.

Select No to all the following options and click Next

Click Install

The installation completed successfully, with just a warning about the Management Server license. You can scroll down to see the results of the other features that were installed.

Select Start the Operations console when the wizard closes and click Close.

The SCOM Management Console

The SCOM installation itself is straight forward. However, we needed to have all the prerequisites installed including a SQL Server.