System Center Operations Manager by Jonathan Hambrook

July 31, 2007

Back at work…

Filed under: News — opsmgr @ 9:50 pm

So I have been putting in some long hours and even a lot of hard work on my vineyard and the other day passed out at work and ended up in Hospital but I am back. I will however be slowing down a little.

On the other hand I have my new Brown Zune! This is a great day for me as i can finaly pass on my 60Gb iPod Photo which has disapointed me for some time.

For all of you that have posted comment sorry for delay but you should see or have recieved a replay by now. I am always happy to reply to any comments posted.


July 19, 2007

Want to ‘Design a new report’ in SCOM 2007?

Filed under: Microsoft, SCOM 2007 — opsmgr @ 3:59 pm

Most have you will have clicked on the ‘Design a new report’ button and found that there were ‘No Data Sources available’.
Design a new report

Here is how you can setup this feature for SCOM 2007.


1. Open SQL Server Business Intelligence Development Studio
2. Click File -> New -> Project
3. Select Report Model Project
4. Fill in a Name and Location
5. Click OK
New Project


1. In Solution Explorer, right-click Data Sources, Click Add New Data Source
Solution Explorer

2. Click Next on the Welcome Screen
3. Click New
4. Fill in the connection to the SQL Server and Instance (ie: SERVER\INSTANCE) to your SCOM Database
5. Select the Database you want to interact with. (ie: OperationsManagerDW)
DNR Connection Manager

6. Click OK
7. Click Finish

You will now see the Data Source under Solution Explorer


1. In Solution Explorer, right-click Data Sources, Click Add New Data Source View
2. Click Next
3. Select the data source from the Relational data souces: panel
4. Click Next
5. This is the part where you need to think, You will need to select the tables and views you want to include in the model. If you not sure and just want to play around you can however I would not suggest it… but you can sellect all the tables, however leave the views out as they can cause issues.
6. Click Next
7. Click Finish

You will now see the Data Source View under Solution Explorer
Solution Explorer 2


1. In Solution Explorer, right-click Data Sources, Click Add New Report
2. Click Next
3. Select the Data Source and Click Next
4. Select the Model Rules and Language (If unsure, keep the defaults) Click Next
5. Select Update model statistics before generating and Click Next
6. Type in a name Name and Click Run

Note: This may take some time depending on the number of Tables and Views selected when creating the Data Source View.

7. Click Finish
8. Under Solution Explorer Right-Click the new Report Model and selct Deploy
Solution Explorer 3

9. Exit SQL Server Business Intelligence Development Studio and Save.


1. Open System Center Operations Manager Console
2. In Report Click Design new report
3. Report Builder will launch and you will see a Data Source
4. Highlight it and Select a Report Layout Click OK
Microsoft Report Builder


July 18, 2007

Issue with changing ‘Default Action Account’ for a Server

Filed under: Issues, SCOM 2007 — opsmgr @ 3:44 pm


If you are looking at changing the ‘Default Action Account’ Rus-As Accounts for a server, even if you use an account with the right access you may find that the server greys out.

My findings have found this is more common on Domain Controllers or Servers in OU with blocked Group Policy (If you are using Group Policies to determine access). Meaning that the account setup when you installed the agent doesnt have the access to make changes to the Health Service setup.


Use HSLockdown to add the Action Account to the Health Service. You can do this using the command:

c:\”Program Files\System Center Operations Manager 2007″\
hslockdown “Management Group” /A “DOMAIN\USER NAME”

Note: I put in the exclimation marks (“) just to point out if you use spaces they will be required to run any commands.

July 17, 2007

OpsMgr 2007 MOM 2005 Backward Compatibility Updated

Filed under: Microsoft, SCOM 2007 — opsmgr @ 11:39 am

The MOM 2005 Backwards Compatibility MP has been updated to version 6.0.5000.12 and System Center Internal Library MP updated to verison 6.0.5000.16.

You can download it from:

July 12, 2007

Error: Replication Monitoring – Access Denied

Filed under: Errors, Microsoft, SCOM 2007 — opsmgr @ 5:38 pm

So you have followed the Active Directory Management Pack Guide for Operations Manager 2007 to the letter and you get Access Denied errors. You also get the same error in Event Veiwer as seen in the Screen Shot:
AD Replication Monitoring Error

Here are some things you will also need to check above an beyound the supplied documentation.

Container Permissions
1. On page 9 of the AD MP Guide it mentions that you need to create the MomLatencyMonitors container. I have found that in a heavely locked down environment you will need to add Read/Write permission to this container. (DC=Domain, DC=com). The permission need to be of the account specified under the ‘Configure an Account for Replication Monitoring’ of Page 9 of the AD MP Guide.

2. Also you may like to check the ForestDNSZones as well. This can be done via ADSI Edit by connecting to DC=ForestDNSZones, DC=Domain, DC=com. You will see MOMLatencyMonitors, right click and select security.

Agent Permissions
If you deployed all your agents using Local as per the following screenshot:
Agent Install Local System
You will also find you will have some issues as the Health Service will start with Local System, which is fine but the Agent Action Account will also be specified as account to do all the processing by that agent. This is fine for all other servers if you require it but you will need do the following on the Domain Controllers

1. Add/Remove Programs
2. Select the System Center Operations Manager Agent and click Change
3. Select Modify
4. Select Modify Management Group
5. Click Next on the next 2 screens until you get to the Ready to Install screen
6. Click Back
7. Specify a Domain Account. (See the deployment Guide page 31 for the permission of the Agent Action Account)
8. Click Next then Install

By doing the above steps, The Service will still start with the Local System Account but will do all its proccessing using the Domain Agent Action Account. You should now be able to restart the Health Service and your permissions issues should go away.

I do however recommend that all Agents be deployed using a domain Agent Action Account.

Issue with creating new Performance Rules and Reporting on them.

Filed under: Issues, Microsoft, SCOM 2007 — opsmgr @ 2:36 pm


If you recall I blogged on this issue earlier and said I would investigate more. As a recap you can check out the screenshots to see the issue:
MOM UI Error 2 MOM UI Error

Basicly, you will see the something like MomUIGeneratedRule with a series of characters after it.


This happens when you create a custom performance counter in a Management Pack that is not the “Default Management Pack“.

I have heard that MS are working on this and have been able to replicate the issue, we should see a fix soon so check back as I will be moniroting this one closely.

July 9, 2007

Monitoring SNMP v1 devices with SCOM

Filed under: Microsoft, News, SCOM 2007 — opsmgr @ 7:45 pm

I have seen this posted on other blogs, and have also been waiting for this for some time. Microsoft have got a Hotfix out for SCOM to monitor devices using SNMP v1. The artical/hotfix isnt accessable on Microsoft Public site so you will ring up there support and request KB 989364 with the downloadable about 60Mb.

I am starting my testing on some old NT4 legacy servers as well as some ancient network devices that always seem to be lieing around in a big data centre.

NOTE: I have been told that the KB Article will be unavailable until some more testing have been performed. If you are looking for it, unfortunaly its not quite ready yet… but soon 🙂

July 5, 2007

Interesting Issue with Reports…

Filed under: Issues, Microsoft, SCOM 2007 — opsmgr @ 8:21 pm

Well today I found an interesting issue with the intedgrated Reports. You can rplicate this by doing the following:
1. Open System Center Operation Manager Console
2. Goto [-] Microsoft Windows Server [+] Windows Server State
3. Select a Server
4. In the Actions panel select one of the Performance History Reports
5. In the Report Details choose a date spanning months. (ie: 20th June to 10th July)

Now at first glance I thought I was missing data but then quickly realised what I was seeing was the correct data, just not in the expected display. Have a look at what I saw:

Wrapping SCOM Report

If you look closely you will see I have asked for a report to start on the 20th June and to run untill the 4th of July.

What I get however is the first 4 days of July before the last 10 days of June… I have posted this to MS and am awaiting a responce, however I would guess there is an issue with date formating issue, as in Australia we use DD/MM/YYYY.

UPDATE: MS have been able to replicate this and are working on some re-engineering of the Reports, could be hotfix or part of SP1.

Operations Manager 2007 Backup and Recovery Guide Released

Filed under: Microsoft, SCOM 2007 — opsmgr @ 3:56 pm

The Operations Manager 2007 Backup and Recovery Guide is now available for download from Microsoft. To get your copy go to you will find all Microsoft documentation there.

July 3, 2007

Error: Access to the registry key ‘Global’ is denied.

Filed under: Errors, Issues, Microsoft, SCOM 2007 — opsmgr @ 9:01 pm

I noticed this Error in a few blogs and thought I would have a crack at it and I was able to recreate it in my lab.

Access to registry key Global is denied

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[UnauthorizedAccessException: Access to the registry key 'Global' is denied.]
Microsoft.Win32.RegistryKey.Win32Error(Int32 errorCode, String str) +2116595
Microsoft.Win32.RegistryKey.InternalGetValue(String name, Object defaultValue, Boolean doNotExpand, Boolean checkSecurity) +2779509
Microsoft.Win32.RegistryKey.GetValue(String name) +29
System.Diagnostics.PerformanceMonitor.GetData(String item) +96
System.Diagnostics.PerformanceCounterLib.GetPerformanceData(String item) +147
System.Diagnostics.PerformanceCounterLib.get_CategoryTable() +82
System.Diagnostics.PerformanceCounterLib.CategoryExists(String machine, String category) +65
System.Diagnostics.PerformanceCounterCategory.Exists(String categoryName, String machineName) +125
System.Diagnostics.PerformanceCounterCategory.Exists(String categoryName) +9
Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.Counters.BuildPerformanceCounter(DalCounter counterName, String instanceName) +302
Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.Counters..ctor() +197
Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.DataAbstractionFactory..ctor() +24
Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.DataAbstractionFactory..cctor() +20[TypeInitializationException: The type initializer for 'Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.DataAbstractionFactory' threw an exception.]
Microsoft.EnterpriseManagement.OperationsManager.DataAbstractionLayer.DataAbstractionFactory.GetInstance(IDataAbstractionBuilder builder) +0
Microsoft.EnterpriseManagement.OperationsManager.WebConsole.WebDalWrapper.get_OpsSdkWrapper() +37
BaseWebConsolePage.get_OpsSdkWrapper() +210
login.Page_Unload(Object sender, EventArgs e) +22

You will also get this error in the Event log on the Web Console server (Click to view full size):
Event 10

This is what I did to create the Issue and further down is the workaround which is a common fix for this issue in some other Blogs and also with other errors Microsoft have in their Knowledge Base that arn’t specific to SCOM.

To set the scene this is what I set out to achive. I wanted to create a New Monitoring Diagram View to display a couple of intranet sites that I want to monitor from all our national offices and unlike the Web Application State view I only wanted to see the Websites status ie: Health or Critical etc.

I order to do this I would have to do the following, create new Groups, new Monitor, new Management Pack, new View and to then restrict access to only show the one new View in the Web Console for a few people.

1. Created the Management Pack

2. Created the Web Application monitor for the sites

3. Created a Group and then added 2 other Groups as Child Groups. (One for each Application and added the appropriate Web Application to each group)

4. Created the new Monitor to report the status of the 2 Child Groups

5. Created the Custom Diagram View showing the Primary Group and the 2 Child Group.

6. Under Adminitriation I created a new Read-Only Operator, New user Role.

7. Added the Domain Users (Same Domain as SCOM is in) that would have access to this group and also specified that all they could see was the 3 new groups I had created and the new view as well as the Web Applications State view. (Now this is where I think I need to look further to see whats happening.)

8. I then accessed the Web Console and got the above error.

9. Applied the resolution: Added all the users from the new ‘User Role’ to the local Performance Monitor Users group on the server that runs the Web Console. (I however didnt add them to the local Users group as this is inherited by the Domain Users group. If this isn’t the case for you then you should make sure those users are also added to this group)

10. Closed all IE browser and Performed an IISReset (run from cmd)

11. Logged back on and EVERYTHING was working great. Here is what I saw for reference.
Monitoring View

July 2, 2007

SQL 2000 showing as ‘Not monitored’

Filed under: Microsoft, SCOM 2007 — opsmgr @ 10:13 pm

A common question asked in a lot of forums is why is SQL 2000 showing as ‘Not monitored’ even though I have the Management Pack installed.

SQL 2000 Not Monitored

Well as it says, its not being monitored. This doesn’t mean that you can’t it is simply that the rule that is used to monitor this object is currently not enabled. A quick one for all the newbies to SCOM, you aren’t just able to find the rule and click enable like in MOM 2005. However I would suggest you plan this as the design in SCOM 07 is to have you create overrides. This will require the use of a Management Pack which out of the box there is just the one that you can use which is the ‘Default Management Pack’.

Here is a quick step by step on how to enable the SQL 2000 Monitoring. Note: This can be used for any MP but SQL seems to be the most commonly asked as most of us would assume installing the MP would just work.

1. Open the Operations Manager Console and go to Authoring

2. Select Monitors under Management Pack Objects

3. To make it easy to locate the right Monitor change the scope to look at just SQL 2000 DB Engine

4. Expand Availability

SQL 2000 DB Availability

5. Right click on the SQL DB Engine Service Health Rollup and select Overrides -> Override the Monitor -> For all object type: SQL 2000 DB Engine. (You will notice that enable is greyed out, this because this MP is locked. We will be creating an override in a new MP. Also not the light greyed area in the above screen-shot, this is due to the the fact I used the search feature to find the exact Rule quickly using the word Health so each Rule with Health in it shows in Black.)

6. As per the screen shot, Tick the Override box next to Parameter you want to change and in the Override Setting change the field to the appropriate setting. For full functionality you can tick them all and if that’s too much you can scale back.

7. Select the Management Pack you would like to create this override in, I have an SQL Override Management Pack where I store all the SQL Overrides in. This I find makes it easy to track down in the feature, you are also then able to run a report against that Management Pack to get a list off the rules it contains.

SQL 2000 Override Settings

8. Click OK. In most cases you will need wait for the Agents to update but if you are impatient, just stop and restart the Health Service on the SQL 2000 server you are monitoring.

SQL 2000 DB Availablity OK

Create a free website or blog at