Logical Disk Free Space Monitor

Throughout my years working with MOM and Operations Manager 2007, periodically I hear complaints about Operations Manager not alerting on low disk space conditions, or that administrators are receiving false alerts.  Just about every time I’ve been called upon for this type of issue, it turned out to be thresholds not being adjusted properly, not that Operations Manager didn’t do it’s job correctly.

Before I get into this deeply, I want to iterate the importance of having a good disk free space monitoring definition in place.  I have seen so many companies struggle with disk free space monitoring, when they really don’t need to.  The problem almost always starts with not having a good discussion around your free space requirements, defining the thresholds for server roles and types, and then executing on the design.

This is a basic requirement for monitoring operational health of every server role in your infrastructure.  Whether we’re talking about file servers, database servers, web servers or application servers, it is a mistake to put this on the back-burner and not define your requirements as soon as possible for each server role.

Two types of monitoring

My standpoint from a disk space monitoring perspective is simple, and it is aligned with the intent and purpose of Operations Manager.  It’s two-fold.

Reactive and Proactive

Although it may seem elementary, let me explain the difference between reactive and proactive monitoring, and how it relates to the Logical Disk Free Space Monitor.

There are two scenarios when it comes to state changes in monitors, and each of these can be paired up with either reactive or proactive type monitoring.

Two-State Monitor = Reactive Only
This monitor has only two states.  Healthy is required for one of the states.  The other state can be warning or critical.  In my opinion, a two-state monitor almost always defines some type of reactive monitoring scenario.  In other words, a component being monitored by a two-state monitor is either healthy, or an administrator needs to take immediate action in order to correct the problem.  This is synonymous to ON and OFF.  There is no period of time where this component is in a degraded state, but still functioning, that allows an administrator to take remediation actions to correct the issue before it worsens.

Three-State Monitor = Reactive and Proactive
This monitor has three states.  Healthy, Warning and Critical.  The rules are similar to the Two-State monitor, as far as Healthy and Critical states are concerned.  However, there is an additional state that connotes a degraded condition.  In a degraded condition, the service or component is still functioning, but there are problems on the horizon if the administrator doesn’t plan to take remediation actions at the earliest convenience.

With this additional Warning (or degraded) state, we lend another type of monitoring to our operational monitoring; Proactive.  Although this borders on both Reactive and Proactive, this is still very much proactive, in my opinion, because the administrator is informed of a degraded condition before is turns critical.

How does this relate the Logical Disk Free Space monitor?  Well, this is a Three-State monitor.  Hence, we are provided with the best of both worlds from an operational standpoint.  Both Proactive and Reactive.

Another part of Proactive monitoring is provided by the reporting feature in Operations Manager.  This goes above and beyond the capabilities of having a monitor warn your staff of a degraded state.  This arms you with the capability to perform trend analysis of your applications and hardware, allowing your company to use this information for planning and provisioning resources in your infrastructure.

My argument

I have been in my share of arguments around monitoring disk space, usually relating to general recommendations for the threshold types used in this monitor.  One of the most heated arguments I’ve heard around these thresholds, is to only use one type of threshold; either the MB threshold or the Percentage threshold.  My argument has always been to use both these threshold types, and not to generalize an entire IT infrastructure based on a single threshold type.

By using only one threshold type, I don’t see how anyone could encompass the array of disk sizes and different types of server roles in the environment, and define a disk free space monitoring solution using only one threshold type.  In my opinion, using only one threshold type generalizes all the unique attributes that make up the infrastructure as a whole.  All I ask is that you read this article before making a decision as to how you’re going to use this monitor.

The problem

I’ve done my time going through the ranks of systems administration.  And this includes carrying a pager, and reacting to alerts from that pager, 24/7.  This being the case, I know one thing for sure.  And that is…

I do not want to be stirred out of a deep sleep, pulled away from my family or have my golf game interrupted, in order to check on an alert that was triggered, only to find there was plenty of free space on the server I was alert on.

Sound familiar?  I bet it does.

If you answer yes to any of the below questions, your reactive thresholds are not adjusted correctly.

1.  At the earliest convenience, do you adjust the threshold for that instance?  Or, just  disable monitoring for that drive and be done with it (I have seen this done).

2.  Do you have a routine down, and you know exactly when that alert will trigger, so you auto-respond to that alert without actually checking it?  Or have you started ignoring alerts altogether?

5.  Do you end up just checking on that server every day when you come in and when you leave, and see that it’s grown by 100MB each day, just waiting to bring it up in a meeting to allocate more drive space?

Whatever the case may be, you know that this drive is not in a critical state and there is no need to be alarmed yet.  Growth of that particular disk has always averaged around 100MB a day, and you know the SAN group will not allocate more space until it’s down to 10GB free.

Make your case

To the on-call admin wearing the pager, listen up.  I’m offering this argument to you, so you can then present your ideas to the operations monitoring group.

First thing you’ll want to do is download the Logical Disk Free Space Monitor Calculator (attached to bottom of article).  Also grab this query, to help map out what your current disk sizes look like.  A method I often use is, plug in the largest disk size, the smallest disk size, and the average disk size in the the calculator.  Then start playing with the thresholds in the calculator to determine your unique threshold requirements for both System and Non-System drives.

First things first.  How does the Logical Disk Free Space monitor work, when using both the MB and % threshold types?  Here’s how.

The moment BOTH thresholds are exceeded, the state of that monitor will change.

Some basics of the monitor.  This monitor is targeted to each type of Windows Server (2000, 2003 and 2008).  Just keep that in mind when adjusting thresholds.

This is a double-threshold, three-state monitor.  However, being that there two types of thresholds (MB and %), there is actually four thresholds that need to be set for this monitor.

Go ahead and open up the monitor properties and take a peak at the thresholds.  To do this, go to the Authoring space.


Click on Monitors, then click Scope.


Type Logical Disk in the Look for input box, and check all three targets (for each type).  Then click okay.


If you expand each of the types, as shown in the image below for 2003 type, you’ll find the monitor.  Do not confuse the Free Space monitor with the Availability monitor.

Open the properties of the monitor.


As you’ll see, these thresholds are also split into to types of drives; System and non-System.  This may sound confusing, but it’s really quite simple and there is good reason for it.  As you might expect, System type drives host the operating system.  Non-System type drives are all other drives.

And here are the tabs showing the properties of the monitor.


The reason for the two types of drives is because, drives that host the operating system are usually well-defined with specific volume sizes.  These drives usually do not fluctuate in free space.  And if they do, we monitor that.  But, the monitoring is generally much more strict and will match as closely as possible to a true warning or critical state for the operating system to function properly.

In other words, a System type drive with 500MB of free space is okay.  This drive doesn’t need to generate an alert unless it drops below, for example, 200MB.  That’s when we would actually do something to free up some space.  That’s when we need to be paged.  That truly warrants an alarm.

Out of the box, the System type drive thresholds are as follows.


Also by default, this monitor generates an alert when it changes to critical.  What this means to you, is you’ll see a state change in the Operations Console when the drive hosting the operating system drops below 200MB.  This state will persist, allowing you to catch this warning state in the console before it reaches critical state, or until someone moves some files off and creates more free space.

There is a state view specifically for monitoring Logical Disk free space in the Microsoft Windows Server node of the monitoring pane in the Operations Console.  You can also create a view in My Workspace to spot check a specific set of servers for drives in a Warning state once each day.  This is part of the proactive monitoring I mentioned.

So, when the drive hosting the operating system drops below 100MB, you’ll get a page and an alert in the Operations Console.  Again, this is when action must be taken with urgency.  Hence, critical or reactive.

Out of the box, the non-System type drive thresholds are as follows.


As far as non-System type drives, this is usually the tricky threshold that needs to be discussed with your operations team.  This is when you can put my disk space calculator to use.

I’m not going to get into semantics about all the different server roles and make recommendations for types of server roles.  I’ll just note that the type of server is an important factor in determining disk space monitoring requirements.  For instance, database servers will usually have different disk space monitoring thresholds than file servers.

I will, however, be using a file share server role in an example.  This is only to get you thinking in the right direction, and is not intended to be a recommendation.


The company has 40 Windows Server 2003 File Share Servers.  The majority of these servers have a 40GB system drive, hosting the operating system, with the exception of a handful of servers that were installed in 2003.  At the time, the standard build was a 20GB system drive.

For the file shares, most later model servers have one 800GB volume.  There are quite a few servers with two 300GB volumes.  Then there are a few older model servers, which have two or four 80GB volumes.

The questions that need to be answered are:

What is a warning state?
This is the state in which your administrators need to be informed of a degraded situation.  At this state of the monitor, there is time to take action to resolve the issue before it turns into a critical state.  In other words, this the proactive threshold.

What is a critical state?
This is the state in which your administrators need to be alerted of a critical situation.  In this state, an alert will be raised in the Operations Console and a page will be sent to your on-call administrator.  This state connotes an urgent issue, and action must be taken at once.  In other words, this is the reactive threshold.

These questions need to be answered for both types of drives.

System Drives

In your meeting with the operations monitoring team, these thresholds and state were discussed, and everyone agreed upon the following.  Regardless of the size of the system drive, 20GB or 40GB, and considering the operating system drive usually doesn’t fluctuate, and the fact that nobody should be storing data on those drives anyway, a warning should be raised when free space drops to 500MB.

This should give administrators adequate elbow room to proactively monitor for warning conditions and take remediation actions at the soonest opportunity.

Everyone also agreed that we only need an on-call admin to be paged if a drive hosting the operating system drops below 100MB.  This is considered critical, as this will affect operating system performance and render it unresponsive soon, and we want someone paged to move files off that drive immediately.

Using the calculator, you determine that the thresholds for the system drive should be adjusted as follows.


Note that only a single threshold needed to be adjusted.  The critical MB threshold, by default, meets our requirements.  And both the warning and critical % thresholds, by default, meet our requirements.  We need to create an override, for the file share servers, only for the warning MB threshold.

Here’s what it looks like in the calculator.


Remember, our decision was based on MB thresholds only.  We did not even care about % free space.

Given that 10% and 5%, for warning and critical, are well over our defined 500MB and 100MB, respectively, given our drive sizes, we don’t need to play with the % thresholds.  Technically, these % thresholds will be exceeded on our 40GB drives at 4GB and 2GB, for warning and critical.

Remember that both MB and % need to be exceeded, in order for a state change to occur.  So, again, we only need to create an override for the warning MB threshold.  And that override setting is 500MB.

Non-System Drives

Remember, most later model servers have one 800GB volume.  There are a few with two 300GB volumes.  Then there are a few older model servers, which have two or four 80GB volumes.

As I mentioned earlier, these non-system drives are usually a bit trickier to find a good balance.  This is because there is a vast difference in volume sizes, and we’re trying to wrap our heads around a happy medium.

In the meeting with the operations monitoring team, we discussed only using the % threshold, and setting it at 10% and 5% for warning and critical, respectively.  This didn’t go over very well.  Because, again, we don’t want to wake our on-call admin up in the middle of the night because there was only 40GB left on a file share.  That’s not exactly an urgent issue.  Plus, we already know about that server and we’re expecting addition drive space to be allocated on Wednesday.  We knew this because we saw the state change in the Operations Console when that volume dropped to 80GB two weeks ago.

We discussed only using the MB thresholds, adjusting them to 20GB and 4GB, for warning and critical, respectively.  This didn’t go over well, because we really don’t want to wake the on-call admin again when one of the smaller 80GB drives drops to 4GB free space.  These are not high volume drives, and when they are out of space we plan to move that data off to a larger volume anyway.

Rather than jumbling with these numbers, you break out the calculator, plug in the volume sizes (800, 300 and 80GB), and start plugging in some threshold values.  After a few iterations, everyone liked the following thresholds.


Notice in the middle columns in the calculator, that the 800GB drive changes state for both warning and critical on only the MB threshold value.  The 80GB drive changes state for both warning and critical on only the % threshold.  The 300GB actually will use the % threshold value for the warning state change, and the MB threshold value for the critical state change.

This is a great balance for these file share servers.  Each size volume has an adequate warning threshold, to allow plenty of time to proactively monitor these warning states and take action at the earliest convenience.

This also generates a critical state, subsequently generating an alert in the Operations Console and paging the on-call admin.  These are all truly critical states, that require immediate action.

This meets all our requirements to expedite warning and critical states appropriately.  And, most importantly, you’re on-call admin will appreciate that we have a good definition around monitoring disk space.  Now he’s taking these pages seriously, and isn’t bothered for non-critical conditions.

Using Views for Proactive Monitoring

With well defined thresholds around disk free space monitoring, allowing for ample time to take action without urgency, we can use the Logical Disk state view in the Operations Console to proactively monitor free disk space.  Checking this state view once per day will be a part of the daily routine.

You can find this state view here.


What we’re looking for here are servers in a warning state.  If you have hundred, or thousands of servers, you can make this easier to look at by sort by the State column header.

If you want a more targeted view, containing only file share servers in a warning state, you can create a new state view in My Workspace.  Here’s an example of such view.


So, not only are we monitoring for reactive conditions, we are also proactively monitoring disk space by means of establishing well defined thresholds for the Logical Disk Free Space monitor.

Again, as I mentioned earlier, another important piece of proactive monitoring is the report feature in Operations Manager.  We can take proactive measures much further by using the reporting component.  This will give us even richer information, like trend analysis for future planning and provisioning of resources.

I hope now you have a good understanding of how this monitor works.  Along with the given example, and the free space calculator, you should now be armed and ready to tackle these disk free space alerts that have been so troubling for so many…especially for those on-call administrators.

SCOM Remote Maintenance Mode Scheduler 2.0

SCOM Remote Maintenance Mode Scheduler is a GUI based tool that lets administrators easily schedule maintenance mode for a server or group of servers inside System Center Operations Manager 2007.


Download for R2: SCOMRemoteScheduler2.0_R2.zip

Download for SP1: SCOMRemoteScheduler2.0.zip

Instructions:  SCOMRemoteMaintenanceModeScheduler2.0.pdf

New Features in version 2.0 include

  • Ability to schedule a daily maintenance mode.
  • New Show Scheduled Tasks Dialog.
  • Added feature to see all details for scheduled jobs.
  • Added feature to delete scheduled jobs
  • Fixed Minor bugs

Here is what the new Show Scheduled Tasks Dialog looks like

Installing System Center Operations Manager 2007 R2(SCOM)

In this blog post, I will go over the steps to install System Center Operations Manager (SCOM) 2007 R2 and the recent release of the SQL Server 2008 R2 Management Pack (MP) on a bare bones Windows Server 2008 R2 Hyper-V virtual machine.  I’ll include where you can download the various software components (free & evaluation copies). My goal is to make operational DBAs familiar with SCOM 2007 and the various MPs that are available to help you better manage large number of server instances.

This blog post is part of the series of posts that I’m using to prepare for my SQL PASS 2010 session on the SQL MP.

Installing SCOM 2007 R2 and the SQL Server 2008 R2 MP

I’m starting with a Windows Server 2008 R2 Hyper-V image with 4GB of RAM and 1 virtual CPU. This configuration is the minimum recommended configuration for all of the SCOM 2007 R2 features.

Step 0 – Download and install updates

There is always something out there that needs to get updated after installing Windows Server 2008 R2. Be sure to check for updates as part of your Initial Configuration Tasks as shown below.

01 - Check for Updates

Generally, you will need to reboot after this step to make sure Windows Server 2008 R2 didn’t have more updates that require a reboot. Just reboot to be on the safe side.

Step 1 – Add the IIS Role

After the reboot, you will need to add the IIS role to your server. Just click on the “Add roles” command shown above in the “Customize This Server” section of the Initial Configuration Tasks dialog. This will launch the Add Roles Wizard. At this point, I’m assuming you are logged into the server with a Windows login that is a system administrator for the machine.

Just click Next past the introduction page.  You will then select the Web Server (IIS) role as shown below.

02 - Select Web Server (IIS) role

Then click Next. The wizard will then take you to the “Introduction to Web Server (IIS)” page. You are welcome to read the page and click on the hyperlinks to read more about IIS, but we are focusing our attention on getting SCOM up and running.  So, click Next to move along.

The Role Services dialog is the tricky one since you need just about all of the services selected to pass the prerequisite checks for SCOM. So, select all of the check boxes to be on the safe side. At some point, I’ll follow up with a blog post on what you can disable. See below for what the Role Services page should look like before selecting the Next command.

03 - Select all of the IIS services

Once you have selected every service – click Next to go to the Confirmation page and then click Install. With any luck, you should get to the Results page indicating “Installation succeeded”.

04 - IIS Installation Success

Go ahead and click the close button for the Add Roles wizard.  Time for a quick test to see if IIS installed. go ahead and launch IE 8. If you are running with Enhanced Security Configuration, we’ll deal with that in a moment since you’ll need to download more software from the web.

In the IE8 address bar, type http://localhost. If all went well, you should see the following:

05 - Localhost works

Go ahead and close the browser for now. You can also close the Initial Configuration Tasks dialog and you might want to check the box that says, “Do not show this window at login”.

As soon as the dialog closes, Windows Server 2008 R2 launches the Server Manager. At this point, let’s reconfigure “Configure IE ESC” so that you can browse the web without the annoying prompts. NOTE: It is Microsoft’s recommendation to have this feature on for production servers,, but we are just trying to get things spun up the first time with ease. So, be sure to turn ESC back on once everything is running well for you.

Go ahead and click on the Configure IE ESC link as shown below.

06 - Turn off ESC

Then select Off for both Administrators and Users as shown below and click OK.

06 - Turn off ESC dialog

Step 1.5 – Installing AJAX

There is one more add-on that you must install called ASP.NET AJAX 1.0 that you can download from here. It’s also listed in the download links below. Just click on the Download button on the web site and run through the installation taking all of the defaults.

Step 2 – Installing SQL Server 2008 R2

I’m taking a gamble here since support for using SQL Server 2008 R2 was just announced on September 25, 2010 as part of a “FAST PUBLUSH” knowledge base article – see Support for System Center Operations Manager 2007 R2 that runs on a SQL Server 2008 R2 database. You don’t really need to check out KB Article 2425714 since I’ll guide you through the basics later on.

I’ll assume that you have access to the installation files for SQL Server 2008 R2. Check out the download links at the end of this posting for getting an evaluation copy. I recommend going with an Enterprise SKU since it has some cool features like row level compression for your database tables that can save you up to 20% or more disk space with a little more overhead on CPU. There are other great scalability features you can check out at the MSDN article titled Features Supported by the Editions of SQL Server 2008 R2.

Go to your installation folder and the click on Setup.exe. This displays the SQL Server Installation Center as shown below. You’ll want to select the Installation page.

07 - Sql Installation start

Then select the hyperlink for New installation or add features to an existing installation as shown below.

08 - New Install

I’m not going to run through all of the installation screens, but here are the basics to get you up and running. To keep things simple, I’ll assume you will use a Windows domain account with system administration permissions for all of the SQL Server services. I know this is not recommended, and you can change to lower privileged accounts once everything is working.

  1. On the Setup Role page, select the SQL Server Feature Installation option.
  2. On the Features Selection page, click Select All – maybe unclick SQL Server Books Online – since the topics will point to the web based topics by default.
  3. On the Instance Configuration page, select the Default instance.
  4. On the Service Accounts page, click on the “Use the same account for all SQL Server services” button and then enter in the Windows account that has system administration privileges. Yes – I did it again – you should really use a low privileged account, but this is a test environment.  Make sure to set the Startup Type for SQL Server Agent to Automatic as well.  DO NOT CHANGE THE Collation for the server. SCOM requires the use of SQL_Latin1_General_CP1_CI_AS.
  5. On the Database Engine Configuration page, be sure to click “Add Current User” for the admin account. Like a good DBA, be sure to change your data directories off the C: drive.
  6. On the Analysis Services Configuration page, click “Add Current user” and change the Data Directories as needed.
  7. On the Reporting Services Configuration page, select the top option for “Install the native mode default configuration”.
  8. You should be all set for installing SQL Server 2008 R2

With any luck, setup would have gone without a hitch and you can close down the SQL Server Installation Center dialog.

Step 3 – Install Microsoft Office 2010

If you want to author your own Management Packs, you need to install as a minimum Microsoft Word. SCOM 2007 R2 will work with older versions of MS Word, but this is a new box, so you might as well install all of Office. At least, you no longer need Outlook to send emails with SQL Server. NOTE: You will need to install the 32-bit version of Office for this all to work correctly. SCOM uses the Visual Studio Tools for Office runtime which is a 32 bit tool and only works with 32 bit versions of Office at the time of this blog posting.

Go ahead and just install with the default “Big Button” install option – Install Now.

Step 4 – Install SCOM 2007 R2

Note – Before you do anything, make sure you didn’t skip Step 1.5 above. If you forgot, the installation process will politely remind you that you needed to install the ASP.NET AJAX component.

Go to your installation location for System Center Operations Manager R2 release and run OPSMGR2007R2SEL.exe from your local disk. This file is a self extracting zip file with all the components needed to install SCOM 2007 R2.

When you run the .exe file, you should see the following message box kicking off the installation process.

09 - Running the SCOM installer for R2

Followed by the WinZip Self-Extractor UI.

10- Unzip the files

Click the Unzip bottom. At the end of the unzipping process, you should get a message box indicating that 243 file(s) unzipped successfully. Once you click OK, the System Center operations Manager 2007 R2 Setup will be displayed. You may find it hidden behind another window.  It looks like this:

15 - Browse the CD

Click on the Browse this CD because we need to “manually” run the DBCreateWizard command that is located in the SupportTools\AMD64 folder as shown below.

16 - DBCreateWizard exe

Here are the relevant instructions from the the article “Support for System Center Operations Manager 2007 R2 that runs on a SQL Server 2008 R2 database”.

Step 4.1 – How to use the DBCreateWizard tool to install the OperationsManager database

Note You must run the DBCreateWizard tool on the server that is running SQL Server 2008 R2.

  1. Open the <InstallationMedia>\SupportTools\AMD64 folder
    Note <InstallationMedia> represents installation media of System Center Operations Manager 2007 R2.
  2. Double-click the DBCreateWizard.exe file to start the Database Configuration Wizard.
    Note You may receive an error message when you start the wizard.
    For more information, click the following article number to view the article in the Microsoft Knowledge Base:938997 (http://support.microsoft.com/kb/938997/ ) Operations Manager 2007 Support Tools requirements
  3. On the Welcome page, click Next.
  4. On the Database Information page, perform the following operations:
    • Under Database Type, select Operations Manager Database.
    • Under Full Database Instance Name, select the instance of SQL Server where you want the database to be installed.
      Note An instance of SQL Server has the name of <ServerName>\<InstanceName>. The default instance has the name of <ServerName>.
    • Leave the Create New Database option selected.
    • Leave the SQL Port box blank.
      Note If you do not provide a port, the Database Configuration Wizard uses the port 1433 to connect to SQL Server. However, if the instance of SQL Server that you specify uses a port other than 1433 for connection, you must specify the port in the SQL Port box.
    • By default, the database name is OperationsManager under Database Name.
    • By default, the database size is 500 megabyte (MB) under Database Size.
  5. Click Next.
  6. On the Management Grouppage, perform the following operations:
    • Under Management Group name, specify a name for the management group.
    • By default, the BUILTIN\Administrators user group is specified under Configuration Administrator. If you want to specify a different user group, follow these steps: (NOTE: I just went with BUILTIN\Administrators)
      1. Click Browse.
      2. In the Select Group dialog box, click Locations.
      3. In the Locations dialog box, select the domain that contains the user group that you want to specify, and then click OK.
      4. Under Enter the object name to select, type the user group, and then click Check Names.
      5. If the name that you typed becomes underlined, click OK.

      For more information, see the “Before you Start” section of the following Microsoft TechNet website:http://technet.microsoft.com/en-us/library/dd789046.aspx (http://technet.microsoft.com/en-us/library/dd789046.aspx)

  7. On the Error Reporting page, optionally indicate whether you want to send error reports to Microsoft, and then click Next.
  8. On the Summary page, review the configuration summary shown below, and then click Finish

17 DBWizard Summary screen

If everything went according to plan, you will get a message box indicating that the “Database created successfully” and click OK.

Step 4.2 – How to use the DBCreateWizard tool to install the OperationsManagerDW database

Note You must run the DBCreateWizard tool on the server that is running SQL Server 2008 R2.

  1. Open the <InstallationMedia>\SupportTools\AMD64 folder
    Note <InstallationMedia> represents installation media of System Center Operations Manager 2007 R2.
  2. Double-click the DBCreateWizard.exe file to start the Database Configuration Wizard.
    Note You may receive an error message when you start the wizard.
    For more information, click the following article number to view the article in the Microsoft Knowledge Base:938997 (http://support.microsoft.com/kb/938997/ ) Operations Manager 2007 Support Tools requirements
  3. On the Welcome page, click Next.
  4. On the Database Information page, perform the following operations:
    • Under Database Type, select Operations Manager Data Warehouse Database.
    • Under Full Database Instance Name, select the instance of SQL Server where you want the database to be installed.
      Note An instance of SQL Server has the name of <ServerName>\<InstanceName>. The default instance has the name of <ServerName>.
    • Leave the Create New Database option selected.
    • Leave the SQL Port box blank.
      Note If you do not provide a port, the Database Configuration Wizard uses the port 1433 to connect to SQL Server. However, if the instance of SQL Server that you specify uses a port other than 1433 for connection, you must specify the port in the SQL Port box.
    • By default, the database name is OperationsManagerDW under Database Name.
    • By default, the database size is 500 megabyte (MB) under Database Size.
  5. Click Next.
  6. On the Summary page, review the configuration summary, and then click Finish.

Step 4.3 – Now it’s time to install SCOM 2007 R2

11 - SCOM Install

  1. Click on the Hyperlink to “Install Operations manager 2007 R2”. Then, click Next on the welcome page.
  2. Accept the license terms and click Next.
  3. Type in a User Name and Organization and click Next.

Now comes the tricky part because we don’t want to install the Database components at this time as per the article “Support for System Center Operations Manager 2007 R2 that runs on a SQL Server 2008 R2 database”. This article neglects to tell you how not to install the Database components. Starting from the figure below:

12 - SCOM Components start

Click on the icon drop down control next to the word Database as highlighted above.

13 - SCOM Components Dont install database

Choose the command “This component will not be available.”. Once you’ve selected the command, the dialog should look like this:

14 - SCOM DB deselected

  • Enter in the name of your SQL Server into the dialog below and click Next.
    20 Enter in name of SC DB Instance
  • Enter in your Domain account name in the dialog below and press Next
    21 - Enter Domain name
  • Enter in your domain name again for the SDK and Config Service Account and click Next.
    22 - Enter Domain name SDK and Config Account
  • For the Web Console Authentication Configuration, choose the first option “Use Windows Authentication (Recommended)” and click Next.
  • For the Customer Experience Improvement Program, chose the first option “Join the Customer Experience Improvement Program (Recommended). By doing this, we can see how you are using the product to determine if we are firing too many false alerts, or that you are not using certain reports, etc. This will help the product teams make rational decisions on feature enhancements based on your input. Click Next to continue. Then, click Install.

If life is treating you fairly, the installation should complete and display the following dialog.

23 - Backup the Encription Key

You don’t want to Start the Console quite yet, but you do want to backup the Encryption Key when you Finish the wizard. just follow the steps for backing up the key to a box off-site from the original machine.  The instructions in the wizard are straightforward.

Step 4.3 – How to install System Center Operations Manager 2007 R2 Reporting

Note You must follow these steps on the SQL Server Reporting Services server.

  1. Open Computer Management.
  2. In the Computer Management MMC snap-in, expand System Tools, expand Local Users and Groups, and then click Groups.
  3. Locate the following group:
  4. Rename the group to the following by removing “_50” from the group name:
    18 Altering RS Group Name
  5. Install System Center Operations Manager 2007 R2 Reporting.
    For more information, see the following Microsoft TechNet Website: http://technet.microsoft.com/en-us/library/bb432143.aspx24 - Install Reporting

    Important When you install System Center Operations Manager 2007 R2 Reporting, you should not install the Data Warehouse component. See below image for not installing the DW component.
    19 - Don't install DW

    The installation process is very similar to installing the main SCOM 2007 tools, so I’ll skip the dialogs. Again, when you get to the “Operational Data Reports” wizard page, please select Yes, send operational data reports to Microsoft.

  6. After you install System Center Operations Manager 2007 R2 Reporting, rename SQLServerReportServerUser$<hostname>$MSSRS10.<SQLInstanceName> back to original name SQLServerReportServerUser$<hostname>$MSSRS10_50.<SQLInstanceName>
    25 Change back the RS group name

Supported configurations for System Center Operations Manager 2007 R2
For more information about supported configurations for Operations Manager 2007 R2 that runs on a SQL Server 2008 R2 database, visit the following Microsoft Website: http://technet.microsoft.com/en-us/library/bb309428.aspx

You can now Exit the SCOM 2007 R2 installation program

Step 5 – Install the SQL Server Monitoring Management Pack

Go to the download center for the free SQL Server MP at http://www.microsoft.com/downloads/en/details.aspx?FamilyID=8c0f970e-c653-4c15-9e51-6a6cadfca363&displaylang=en

  1. Go ahead and download the SQLServerMPGuide.doc file for detailed information regarding the MP.
  2. Click Download for the SQLServerMP.msi file and then run it in place – or save it to your Downloads folder and then run the MSI.
  3. For the installation folder, leave it to the default location under the Program Files (x86) folder structure. Also, select to Install the MP for Everyone.
  4. Click Install to download the files.

The files are simply downloaded to the install location, you now need to import the MP files into the SCOM Operations Console.

  1. Go to the Start menu, locate the Operations Console, and click on the command. If all the stars aligned, you should see a screen that looks like this for Monitoring when you select Windows Computers in the Monitoring tree.
    30 SCOM Console with Windows Computers selected
  2. Now, select the Administration workspace item and then highlight the Management Packs node in the tree as shown below:
    31 Ready to Import SQL MP
  3. Now choose the Import Management Packs… command as shown above.  In the Select Management Packs dialog, click on the + Add button and choose Add from disk … as shown below.
    32 Add MP from Disk
  4. Go ahead and click Yes to search the web for dependencies, but they are all in download location C:\Program Files (x86)\System Center Management Packs\SQLServerMP. press Ctrl+A to select all files in the dialog and click Open. Then, click the Install button.
  5. You will see two Discovery and Monitoring packs for SQL 2005 and SQL 2008. SQL Server 2008 covers both 2008 and 2008 R2 release.
  6. Once the import is complete, press the Close command.
  7. Now click back to the Monitoring workspace and then expand the Microsoft SQL Server node and select Computers as shown below. You might have to click inside the detail area and press F5 to see your SCOM SQL instance.
    34 SQL Instance in SCOM conside
  8. To Add and new instance to monitor, select the Administration tab and click Discover Wizard… hyperlink as shown below.
    33 Discovery Wizard
  9. Select the Windows computers option and click Next.
  10. Choose the Advanced discovery option and det the Computer and Device Classes to Servers only and click Next..
  11. Choose the Browse for option for the Discovery Method and type in the computer name you want to add in the dialog area.  You can also browse for computers.
  12. Use your admin Windows account for the Administration Account and click Discover.
  13. Check the FQDN for the SQL machine that you want to discover and click Next.
  14. Chose the Other action for the Agent Action Account and type in your Windows credentials, then click Finish. This will display the Agent Management Task Status. Wait for this to finish.  You should see a dialog like this completing the addition of the new box. SCOM will attempt to enumerate all of the SQL Server instances on the box. Then click Close.
    35 Discovery complete
  15. If you go have to Monitoring and click on Windows Computers, you should now wee two box names. When you go to SQL Computers, you should see two instances as well.


Software Evaluation Download Sites

Are the “go to” links to download evaluation copies of the software described  in this blog post.

Looking Forward to SQL PASS

As I continue to prepare for my SQL PASS session on the new SCOM MP for SQL Server, I’ll continue blogging – especially examples with using the new SQL Server 2008 R2 Monitoring MP.  I will also cover how the data collection with SCOM 2007 R2 can be used in conjunction with the SQL Server 2008 Data Collector and Management Data Warehouse and the SQL Server 2008 R2 manageability tools.

Please feel free to add a comment to the blog post and don’t forget to rate it!

%d bloggers like this: