Skip to content

SCOM 2012 – Basic Installation

February 18, 2012

Time for me to run the installation for SCOM 2012 RC. In this test setup i want to start with two servers. One dedicated Database and another for as the Management Server with the Operations Console and the Web Console. I will do the reporting in another article.

Preperation for all (in my case two) role servers:

  1. Prepaire and install the servers which can be physical or virtual with Windows 2008 R2 SP1 and the latest updates.
  2. Add the .NET 3.5.1 Feature
  3. Install .NET 4.0
  4. Install Report Viewer Controls with SP1 ( )
  5. Add the servers to the domain

Creating AD accounts:

Account name Description Membership
<domain>\OM_AAA Agent Action Account <domain>\OMAdmins
<domain>\OM_DAS Config and Data Access Service Account <domain>\OMAdmins
<domain>\OM_DRA Data Reader account
<domain>\OM_DWA Data Writer account
<domain>\OMAdmins Global security group for the Admins Local administrators on all (both) servers
<domain>\SRV_SQL SQL Service Account Local administrators on the dedicated SQL server

Install and Configure the dedicated SQL server:

I will not describe the installations details on the SQL server but only mention the settings required by SCOM 2012. I will install SQL 2008 R2 + SP1 + CU4. So after starting the SQL installation:

  1. Install Database Engine Services and the Full-text search features. These are required. I added the complete management tools too, but this is optional.
  2. Make sure the collation is SQL_Latin1_General_CP1_CI_AS. Please notice that if you’re system language is NOT set to en-usthis might no be the default! In my case i had to change this during the installation:
  3. Use the created SRV_SQL account for running ALL the SQL services.

Install and configure the Management Server with the Management Console and the Web Console

  1. Install IIS with the following additional roles (Needed for the Web Console):
    • IIS 6 Metabase compatibility
    • .NET
    • ASP .NET (include the required)
    •  Windows Authentication
    • Static content
    • Default document
    • Directory browsing
    • HTTP logging
    • HTTP Errors
    • Request Monitor
    • Static content compression
    • IIS Management console
    • CGI
  2. Configure the ISAPI and GCI restrections on the IIS managment console:
  3.  Run the setup.exe from the installation source and follow the screens 😉

I will ignore these warnings because in this test i am using a VM on Hyper-V with dynamic memory. The server has enough!

Before running the next screen make sure the firewall on the database server is correcly configured. For this test i disabeled it.

The domain accounts are created and do not have any additional memberships.

And this is it. Other onfiguration options will be covered in upcomming articles!


From → System Center

Leave a Comment

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: