View RSS Feed


System Centre Operations Manager 2007 on Server 2008 R2 with SQL Cluster 2008 R2

Rate this Entry
by , 8th January 2012 at 03:18 PM (8522 Views)
Ok – so, most of you know I love System Centre products – and after getting SCCM (System Centre Configuration Manger) setup nicely (I will blog on this, as lots of people seem to have a problem getting this up and running in less than a day) – it was time to play with its partner in crime SCOM (System Centre Operations Manager).

What exactly is Operations Manager? Well, it revolves around an agent on the computer to be monitored. The agent watches that computer, grabbing and collating all the information about its inner workings - including the Windows Event Log. It can be set to look for specific events or alerts generated by the applications executing on the monitored computer. Upon alert occurrence and detection, the agent forwards the alert to a central SCOM server. This SCOM server application maintains a database that includes a history of alerts. The SCOM server applies filtering rules to alerts as they arrive; a rule can trigger some notification to a human, such as an e-mail, generate a network support ticket (it can feed to System Centre Service Manager – I will write about that at some point!), or basically any other action you want it to.

When you deploy software with SCCM, you may have seen the dialog about “Generating MOM alert”. Not surprisingly being part of the same suite of products – you can read and query the software installs that you request completion of. In fact most actions that you can complete in SCCM have the option of generating information for SCOM.

SCOM uses management packs (MP) to keep tabs on machines. MPs to refer to a set of filtering rules specific to some monitored application. Obviously Microsoft make management packages available for their products (Exchange, Sharepoint and the usual suspects) - and also SCOM also provides for authoring custom management packs. A lot of other vendors have now started doing MPs too.

Now that’s our overview done, lets get to the nitty gritty of installing this beast. think!
I would recommend that SCOM sits on its own dedicated server – it an get quite busy depending on the size of your network! So, it was time to quickly build another VM on my Hyper V Platform.

As the whole network is only 6 months old, it is all Server 2008 R2 – and the SQL Platform is at 2008 R2 as well.

Problem number one – although SQL Server 2008 R2 has been out and about now for over a year, can cannot do a straight install. Irritatingly, the installer logic will fail to see either a local, remote or clustered SQL 2008 R2 system. Grrrr!

Cue some jumping through hoops. I will assume you’ve got your SQL all set up already; and just a quick hint - if you need SCOM 2007 R2 reporting, don't forget install SSRS. You will want it, and anyway – most other database backend products want Reporting Services anyway.

Database setup
On your SQL Server, find and run DBCreatWizard.exe tool from the SCOM R2 install media – it hides in SupportTools > AMD64. This will launch the Database configuration wizard. Hit next, and then under Database Information , you can select database type , now we need create Operations Manager Database firstly, fill in SQL Port and Database Name and size (leave as default to be honest). Your instance and the data file locations should be picked automatically according to your SQL setup.


After that you can choose the Management Group name , and permissions to run and administer SCOM. I would set your MG name to your domain or something descriptive rather than the default. Another heads up – set your administrators to Domain Admins, (or another group preferably) which has your technicians in it.


You will then get the usual summary screen to hit next to, and hopefully all being well you will get the “Database created successfully” popup.

Now, you need to run the tool again to create the Operations Manager DW database. Everything is as before, except on the Database Information screen, change the Database type in the top drop down.


The usual amount of next-ing, and finally - you can see the databases in SQL Studio.


Actual application setup
You are now good to go with installing the actual SCOM 2007 R2 management system. Of course – all we have done so far is make a blank set of databases. So – obviously, we need to choose Custom setup (we’ve done part of it right!), and make sure you don’t choose the Database item.


That will install all the managementy kind of stuff for you – and it will take it a little while. Another pointer – that Management Group name you chose in the Database setup; make sure you use the same name (but you knew that right!?)!

Next step…install SCOM 2007 R2 Reporting, and I’m afraid there’s some more hoops.

On the SQL Server Reporting Services server, rename the local group SQLServerReportServerUser$<hostname>$MSSRS10_50.<S QLInstanceName> to SQLServerReportServerUser$<hostname>$MSSRS10.<SQLI nstanceName>

And, as per the main management install, when you install System Center Operations Manager 2007 R2 Reporting, you need to choose Custom. Do not install the Data Warehouse component!

Once the install has completed, rename the local group SQLServerReportServerUser$<hostname>$MSSRS10.<SQLI nstanceName> back to original name SQLServerReportServerUser$<hostname>$MSSRS10_50.<S QLInstanceName>

Looking for the official Microsoft article – well that’s here (


  1. RabbieBurns's Avatar
    Ive got SCOM set up and the agent deployed to a couple of servers..

    Is there any chance you could do a follow up post as to how I actually use SCOM please


Total Trackbacks 0
Trackback URL: