Installation of Microsoft System Center Operations Manager SP1 Including Pre-Requisites

SCOM_LogoI have been meaning to write up some stuff about the Microsoft System Center range of products for some time now and with larger deployments around the Core Infrastructure Products such as Lync 2013, Exchange 2013 etc. I now have to take quite an interest, especially in System Center Operations Manager.

I spend quite a lot of time working with Lync Server at present and with SCOM support Lync 2013 from a monitoring point of view you may see that I start to post more around this software package and potentially other System Center Products.

This post will cover the initial installation of SCOM generally covering the pre-requisites and then at a later date I will go through how to configure various parts, I have installed the Management Server & Operations Console using Microsoft SQL Server 2012 Back-end Database Server. I will cover the installation of the Web Console & Reporting Server in a later post.

My Lab environment consists of the following servers:

Primary Domain Controller: VN-DC-01 (Server 2012)
SQL Database Server: VN-SQL-01 (Server 2008R2 with SQL 2012)
SCOM Server: VN-SCOM (Server 2012 / SCOM 2012 SP1)

Domain Suffix: virtualnetwork.local

The following information is relating to Installing SCOM 2012 SP1 on a Windows Server 2012. Once you have joined your server to your domain, installed updates to the latest release we need to prepare the SCOM Server with various pre-requites which I always choose to install using powershell and so you need to launch a powershell prompt, and import the Server Manager module

Import-Module ServerManager

and then run the following:

Add-WindowsFeature NET-Framework-Core,Web-WebServer,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Asp-Net,Web-Http-Logging,Web-Request-Monitor,Web-Windows-Auth,Web-Filtering,Web-Stat-Compression,Web-Mgmt-Console,Web-Metabase -Source D:sourcessxs

*Ensure to change D:sourcessxs to the location of your Server 2012 Media

Microsoft Core XML Services (MSXML) version: Microsoft Core XML Services 6.0 (Download)

Before I continue it is important to mention a few points regarding SQL Server Feature Requirements. It is important to remember that SQL Server collation settings for all databases must be one of the following: SQL_Latin1_General_CP1_CI_AS, French_CI_AS, Cyrillic_General_CI_AS, Chinese_PRC_CI_AS, Japanese_CI_AS, Traditional_Spanish_CI_AS, or Latin1_General_CI_AS. No other collation settings are supported and that The db_owner role for the operational database must be a domain account. If you set the SQL Server Authentication to Mixed mode, and then try to add a local SQL Server login on the operational database, the Data Access service will not be able to start and ensure that the following features are installed

  • Database Engine Services
  • Full-Text Semantic Extractions for Search
  • Reporting Services - Native (for Operations Manager Reporting)
  • Documentation Components
  • Management Tools - Basic
  • Management Tools - Complete

Once you have a prepared SQL Server, I would Reboot the SCOM Server, and then insert the SCOM Installation Media

When you are presented with the System Center Operations Manager SplashScreen, Select Install







On the next screen you need to select which features you wish to install, in this case we are just going to go ahead and install the Management Server & Operations Console we will cover the other two features at a later date using a separate server.







Click Next, and then you will be asked to specify an installation option and as this is a brand new management server we will need to specify a new management group. I have chosen VN-MGMT-GRP







We now need to specify the SQL Instance information in order to setup the Operational Database (insure that you have the required SQL features installed otherwise it will fail)









Click on Next, and then you will need to specify the Data Warehouse Database (again insure that you have the required SQL Features installed otherwise it will fail)







Click Next, the next screen will ask you to configure Operation Manager Accounts, You can use a single AD User Account for relevant roles or you can specify alternative but in this lab environment i have chosen to use the same one. It is recommended that the user account used does not have any elevated rights such as Domain Administrator.










Once this has been completed, the next screen will ask you to go ahead and complete the installation task, once completed you should be presented with the following screen







Start the Operations Console, and there you go that's the Management Server & Operations Console Installed.








I hope that helps, in the next post's I will go through

  • Installation of Web Console & Reporting Server
  • General Configuration of SCOM



Skip to main content