Kevin Holman's System Center Blog

Posts in this blog are provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified in the Terms of UseAre you interested in having a dedicated engineer that will be your Mic

OpsMgr 2007 R2 Core MP’s updated 6.1.7672.0

OpsMgr 2007 R2 Core MP’s updated 6.1.7672.0

  • Comments 10
  • Likes

 

Update 11/24/2010 – this MP has been superseded by a newer update:  http://blogs.technet.com/b/kevinholman/archive/2010/11/24/opsmgr-2007-r2-core-mp-s-updated-6-1-7695-0.aspx  This article is out of date.

 

 

 

The core MP’s have been updated on their regular schedule.  If you are running OpsMgr 2007 R2 – you should update these as soon as possible.

http://www.microsoft.com/downloads/details.aspx?FamilyID=61365290-3c38-4004-b717-e90bb0f6c148&displaylang=en

 

Microsoft.SystemCenter.2007.mp 6.1.7672.0
Microsoft.SystemCenter.OperationsManager.2007.mp 6.1.7672.0
Microsoft.SystemCenter.OperationsManager.AM.DR.2007.mp 6.1.7672.0
Microsoft.SystemCenter.OperationsManager.Reports.2007.mp 6.1.7672.0
ODR.mp 6.1.7672.0

 

I recommend you download and extract the MSI and import these manually – people who import from the catalog often don't get the new reports MP.

 

What's new and why do I need this?

(As always – read the guide – but here are some key highlights:)

1.  Added the Agent Counts By Date, Management Group and Version report, which compiles information on the Operations Manager agents deployed in your environment.  This will provide you a quick report to keep up with agents that need upgrades.

Capture

Keep in mind you also have a sort-able view in “Agents by Version” which will display major version and Cumulative Update status:

image

 

2.  Added monitoring of Operations database partitioning and grooming workflows.

image

 

The default for this monitor is after 2 days of grooming failures – to alert.  Consider setting this to 1 day, as a grooming failure can be a big deal.  Also – grooming occurs at 12:00am, and this monitor runs at 12:01.  As grooming normally completes quickly, but can often take several minutes to complete, consider changing this monitor to run at 1:00AM – to give time for grooming to complete, and alert you immediately after grooming if there is a failure.

 

3.  The criteria for the monitor “Processing Backlogged Events Taking a Long Time” has been updated to prevent the monitor from being reset when the agent is restarted.

This is important – as this monitor was often seen “flip-flopping” especially when you are also impacted by too many Healthservice restarts.

 

4.  BRAVO on this one

A series of rules which monitor failure of scripts, commands and WMI queries have been updated to make them less noisy and easier to understand. Each rule had its name updated to be more explanatory and the alert names generated by these rules were aligned to match the name of the rule so that lookups between alerts and the rules that raised them would be easier.

Consolidation has been added to all rules with a name that begins with “Workflow Runtime” so that alerts will only be raised for multiple occurrences.  This will result in MUCH quieter "generic "script and WMI failure alerts.

The rules were renamed as follows:  

Old name New name
Alert on Failure to Create Process for Batch Response    Workflow Initialization: Failed to start a process or script
Alert on Failed Batch Responses    Workflow Runtime: Failed to run a process or script
WMI Probe Module Runtime Failure    Workflow Runtime: Failed to run a WMI query
WMI Probe Module Initialization Failure    Workflow Initialization: Failed to start a workflow that queries WMI
WMI Event Module Runtime Failure    Workflow Runtime: Failed to run a WMI query for WMI events
WMI Event Module Initialization Failure Workflow Initialization: Failed to start a workflow that queries WMI for WMI events
WMI Raw Performance Counter Module Runtime Failure    Workflow Runtime: Failed to run a WMI query for performance data
WMI Raw Performance Counter Module Initialization Failure    Workflow Initialization: Failed to start a workflow that queries WMI for performance data
(new rule) Workflow Initialization: Failed to start a workflow that runs a process or script

 

5.  Added functionality for detecting and repairing duplicate relationships between agents and management servers.

This is a rare but very critical condition that we now monitor for.

 

6.  Changed the following view names:
•    Management Server State for Dashboard View is now Management Server State
•    Management Server State for State View is now Management Server State
•    AD based Agent Assignment Module Events for Dashboard View is now AD based Agent Assignment Module Events
•    AD based Agent Assignment Module Events for Event View is now AD based Agent Assignment Module Events

 

7.  Disabled the following rules:
•     “Collects data from the Processor\% Processor Time performance counter (Deprecated)”
•    “Collect Management Configuration Service Configuration Updated Events”
•    “Health Service Connector Bind Failure”

 

8.  Changed the following performance collection rules to ensure they write to both the operational database and the data warehouse database:
•    Collect System\System Uptime
•    Collect SDK Performance Data
•    Collects data from the Processor\% Processor Time performance counter (Deprecated)
•    Collects Operations Manager SDK Service\Client Connections

Comments
  • Hello Kevin,

    Great stuff again and again!!!

    The report?

    The first graph "Agent counts by version" is showing 530 for version 6.1.7221.0

    I am getting a second graph:"Agent counts by Management Group"

    I have two colors:

    - brown : 485

    - blue: 352

    but both color have the same label: SCOM-MED

    I have only one management group so I don't understand exactly what it shows...

    Why do I have this difference? What the numbers reflects? they do not match anything...

    Thanks,

    Dom

  • Operational Data Reporting Management Pack version 6.1.7676.0 has been released and is on the Catalog now.

  • Hello Kevin - Does OpsMgr 2007 R2 6.1.7672.0 take the place of the OpsMgr 2007 R2 Cumlative Update 2?

    Thanks,

    Brian.

  • Hi Brian -

    A CU and a Core MP update are two totally different things.  That's why both are listed on my hotfix page.

  • Kevin, when I go to import the new MP's I get a blue "I" next to all but reporting. Clicking on information icon and then Dependencies it has a small hammer next to my self created Mp's for various Monitors/rules I have created - such as 2003 MP overrides and the like.  I assume some part of the new MP's affect my override MP's. Any advice on troubleshooting potential issues?

  • Derek - that simply means you have some override MP's which reference this MP.  It means you have current overrides on those MP's for this one - or at one someone create an override or group which referenced an object in the MP you are importing.

    Totally normal.

  • Ok, thanks for your prompt response. I'll assume no issues and import said MP's tonight. Just wanted to make sure. I'm a paranoid Sysadmin... this is Production.

  • It seems as though the download link no longer works. I also cant download it from pinpoint because that download link no longer works. Downloading through the SCOM MP downloader fails. did they pull these MP's off?

  • @Adam - the links are down because there is a new core MP update coming very soon - so the old one has been pulled - stay tuned in the next couple of days.

  • Thanks Kevin. Great timing on todays article from your blog! I will download 6.1.7695.0 instead asap.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
Search Blogs