OpsMgr 2007 R2 MP version 6.1.7599.0 is Released!

OpsMgr 2007 R2 MP version 6.1.7599.0 is Released!

  • Comments 9
  • Likes

The System Center Operations Manager team has released its second quarterly update of the OpsMgr 2007 R2 MP to the catalog.  You can download the MP from this pageThis package (Version 6.1.7599.0) is specific to OpsMgr 2007 R2 and will not import on product versions prior to that.

We’ve packed a ton of new features into this release and a full change log is provided in the management pack guide.  At the bottom of this post is a quick run-down of the new features in this release.

Also, to help people get familiar with all of the new features and changes going into our MP, I’ll be posting a new article every couple of weeks to this blog.  Each post will highlight a specific feature added in the most recent release with the goal of giving every one of our readers insight into how we saw the feature being used.

Feedback or inquiries is welcome through our forums or our public Microsoft Connect site for OpsMgr.

Enjoy!
-Cory Delamarter

Identify data volume drivers: How often have you asked the question, “Where is all of this data coming from” and had to run SQL queries to figure it out?  This is an important question to be able to answer, especially when evaluating new MPs or troubleshooting environmental issues.  This release introduces the first set of reports designed specifically for management of Operations Manager and they are aimed at helping you answer that question.  The reports give you a simple way to review data volumes broken down by management pack, workflows and instances.  Use these reports to better understand the amount of data going through your infrastructure and identify places where tuning needs to be done.

Monitor agent processor time: The OpsMgr MP has provided monitoring for the memory utilization of the OpsMgr agent for some time now, and we even provided a significant update to that functionality in our last release.  With this release we have added a new rule, monitor, task and view all focused on monitoring and showing the total percentage of processor time our agent and its child processes are using.

·         The monitor “Agent processor utilization” will detect if our agent and its child processes are taking up excessive CPU utilization over a number of consecutive samples.  The knowledge provides troubleshooting steps and points out a number of patches which could be applied to address the problem.

·         The rule “Collect agent processor utilization” samples the agent processor utilization and stores it so that users can analyze utilization over time.  This fills a major gap in the OpsMgr troubleshooting toolkit.

·         The task “Get the agent processor utilization” uses the same logic as the monitor and collection rule to sample the agent processor utilization and reports back the average, maximum and minimum value sampled over a number of samples.

·         The view “Agent Processor Utilization” view within the new “Agent Performance” view, allows you to review the performance data being collected so you can see what processor utilization has been over the span of the data available in your operational database.  Simply open the “Agent Performance” view, click on the “Agent Processor Utilization” tile in the view and then select the agents for which you want to see utilization.

Audit agent versions: The “Agent Version Monitor” runs on each agented system and checks the agent’s version against a “desired agent version”.  If the version is below the desired version then the agent’s configuration state will change to warning, allowing you to easily identify which agents in your environment need to be upgraded.  The desired agent version can be configured by override so that you can dictate which systems need to be running which agent version.

Detect agent architecture mismatch: 32bit agents which are installed on 64bit operating systems can result in a lot of problems and in some cases are unable to collect all of the monitoring data that they need to.  The new monitor “Agent and OS architecture are the same” detects if any of your 64bit systems have a 32bit agent installed on them so that you can easily identify those systems and reinstall the correct version of the agent.  If you have any systems where this configuration is required, you can disable this monitor via override.

Review OpsMgr performance data more easily:  The OpsMgr agent performance views have been consolidated into a single dashboard view, which includes a new view for the agent processor utilization.  This allows users to review all relevant performance data in one screen, and avoids the confusion from axis scaling, caused by having different data series shown on the same chart.

Improve your knowledge: We continue to invest in tons of new and improved knowledge.  In this release we’ve added up updated over 20 articles with more complete information on how to troubleshoot problems and the true impact of the issues.

Operations Data Reporting: The easiest way for you to give feedback on management packs is by enabling the Operational Data Reporting (ODR) capabilities built into OpsMgr 2007.  By doing this you send anonymous data about how MPs are behaving in your environment back to Microsoft.  We in turn summarize this into reports that we share with all teams that develop management packs so they can see which rules and monitor are driving our users' workloads.  In order to increase awareness, and to set the stage for future updates in this MP, we're including this MP in the OpsMgr MP package from this point forward.  If you're considering this but you're concerned about what data this would send to Microsoft, you can learn more in two ways.  First, you can import the ODR MP without enabling the feature and run the reports directly.  What you see in the reports is what would be sent.  Second, you can review the privacy statement.

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

    Thanks Thanks Thanks - this is so good!

    This is what I have been dreaming about. It's a great help.

    br

    Lars

  • Hi,

    after upgrading from 6.1.7533 to 7.1.7599 the "Run As Configuration" (Health Service Configuration) view disapeared .

    i noticed the renamed folder just after the upgrade.

    now i cant re-import the MP.

    is there any thing i can do to solve it ?

  • Good work! But PLEASE get rid of PinPoint!! It's VERY hard to find the correct MP on there. Very bone-headed move.

  • I know it's not the right place to comment but I will second yngdiego777 "But PLEASE get rid of PinPoint!! It's VERY hard to find the correct MP on there. Very bone-headed move."

    I could not agree more. Who on earth dreampt up that site and tested signing it off as improvment . Awful truly awful.

  • ++ to PinPoint behing an absolutely horrible website for the MP catalog. :(

  • good work,

    one extra monitor would be nice to:

    - The agent send Queue % monitor for the Gateways targets.

    Michel

  • Thanks for the update, it's really useful. But I found a problem: when run the Data volume by Management Pack and Data volume by Workflows and Instance, onlye the Unsealed Management Packs appear at the Management Packs section.

    Anyone with this issue? I've reviewed the documentation but none is wirte about this.

    Thanks - Ivan

  • Thanks to everyone for the comments and the call outs along the way.

    Kobi - Thanks for bringing this apperant ommission to our attention.  I've started a new thread on this for clarification and further discussion at http://social.technet.microsoft.com/Forums/en-US/operationsmanagermgmtpacks/thread/38fd43e0-3577-487a-96ec-46333e3eba2c.

    Michel - Thanks for the suggestion.  Please go to http://connect.microsoft.com/opsmgr and submit this idea as feedback.

    Ivan - This is a bug in the new reports that we discovered only after the MP was released.  There is a workaround discussed at http://social.technet.microsoft.com/Forums/en-US/operationsmanagermgmtpacks/thread/9fb3e839-1318-4671-a8cf-0941eb88b542.  We are in the process of validating the fix for this and will release the updated reports soon.

    As to the comments on PinPoint, we are very sympathetic to the impact that this is having and we are working with the PinPoint team on this.  Please feel free to participate in the discussions on this in the forums or submit your feedback via our connect site.

  • Works like a charm. Thanks and waiting for the official fix.