How to install SCOM 2012 R2

Today i will post a article to describe the procedure to be followed if you want to install System Center Operations Manager 2012 R2 in an high availability environment.

SCOM 2012 R2 will be install on 3 Management Servers and database will be install on SQL 2012 SP1 cluster.

OpsMgr 2012 R2 allow you to monitor all of your servers, applications, devices, etc

You can install SCOM on physical servers or virtual machines. Both are supported by Microsoft. My installation will be perform using 5 VMs.

You can find on this link more informations and all requirements about SCOM 2012 R2 :

http://technet.microsoft.com/en-us/library/dn249696.aspx

Here you will find the way to use SQL Server 2012 Always On with Operations Manager :

http://technet.microsoft.com/library/jj899851.aspx

The following article will describe a SCOM installation to monitor 400 clients. If you want to define the good size for your project, you can use this link to define it :

http://download.microsoft.com/download/C/A/6/CA60425C-950B-456E-986C-C5F2FCD5668D/System%20Center%202012%20Operations%20Manager%20Sizing%20Helper%20Tool%20v1.xls

Design

As you can see, we have a SQL Cluster where databases will be stored on storage array using iSCSI.

For performance reasons, you need to store your dabatases on a directly attached drive. It's recommended if you install SQL on virtual machines like me.

Reporting feature will be install on SQL server.

Account

• SCOM Action Account
• SCOM  Data Access Service
• SCOM  Data Reader
• SCOM  Data Warehouse Write Service
• SQL Service Account

Create a domain group with all SCOM account and add this group to the local administrators in all servers.

Server

• Install Windows 2012 R2 on all servers.
• On SCOM server, install Microsoft System CLR Types for SQL server 2012 and Report View controls
• On SQL server, these products will be install with SQL installation. Check that after the installation.
• Install all windows updates
• Install .NET Framework 4.5
• Install .NET Framework 3.5 on SQL Servers. You need 2012 R2 sources to install this feature.
• Install IIS on the MS server that will provide Web Console feature
• Static Content 
• Default Document 
• Directory Browsing 
• HTTP Errors 
• HTTP Logging 
• Request Monitor 
• Request Filtering
• Static Content Compression
• Web Server (IIS) Support
• IIS 6 Metabase Compatibility
• ASP.NET (both the 2.0 and 4.0 versions of ASP.NET are required)
• Windows Authentication

Cluster

For SQL cluster, you must use SQL 2012 SP1 Enterprise edition. You can't activate Always On feature with Standard Edition.

Add Failover Clustering feature on both servers. Add the storage (mount point) for databases using iSCSI. Add all necessary components to install a cluster.

I created a LUN of 200 Go for database. They will grow up automatically.

In Failover Cluster Manager, select Create Cluster to create a new cluster. Follow all steps.

All steps will not be describe here.

SQL

To get high availability, we need a SQL Cluster. But you can just install one SQL Server and reduce the complexity.

Install Microsoft SQL Server 2012 SP1 on both servers.

Select all of this features.

• Database Engine Services
• Full-Text
• Reporting Services

Provide an instance name

Add your SQL account that you have created before.

Select Automatic for all services.

In Collation settings, select SQL collation, used for backwards compatibility. 

Select SQL_Latin1_general_CP1_CI_AS.

Follow the next steps and put all logs and others in the virtual disk attach on your server.

Create a listener like server role on your cluster. Configure Always On feature with your DBA admin.

SCOM

Management Server

Install SCOM on each server that will be part of your MS pool. Don’t forget to install SQLSysClrTypes and ReportViewer if it not installed yet. Without that, the installation will fail.

Select all of these features without Reporting server. This feature will be install later.

Enter a name for the Management group.

Specify the listener or the SQL server with instance name.

Select a size for database. It will grow automatically. Here, 10 Go to start.

Specify where you want to store your Log and Data. Here, it will be store in mount volume attached to storage array.

Perform the same thing for OperationsManagerDW

Enter credentials account created before.

ü  DOMAIN\OPSMGRAct

ü  DOMAIN\OPSMGRSDK

ü  DOMAIN\OPSMGRDataR

ü  DOMAIN\OPSMGRDataW

When setup is completed, apply all rollup regarding SCOM 2012 R2 that you can find on technet.

Secondary Management Server

It's recommended to have at leat 2 MS for high availability. You can install more MS if you want steer data between MS.

Select Management server and Operations Console. 

Select Add a Management server to an existing management group.

Enter the listener for SQL Always On installation or enter SQL server where database is install. 

Enter your credentials accounts 

When it's done, apply all updates and rollups.

Reporting Server

You can install the Reporting server where SQL product is installed like on the design above.

 Select Reporting server

 Provide your Management server

 Select the SQL Server instance.

Enter the Data Reader account that will be used for Reporting server.

Conclusion

SCOM 2012 R2 is now install in high availabilty. Don't forget to add your global admin group on Security settings.

Now you can add agents to monitor your servers. You can also add Management Pack to get some alerts.

You can find severals MP on Microsoft website.