Changes in This Update

更新日期: 2010年8月

適用於: Operations Manager 2007

The July 2010 release contains an updated version of the Operational Data Reporting Management Pack. The Operations Manager Management Pack has not changed; the latest version of the Operations Manager Management Pack is still 6.0.6709.0.

Version 6.1. 7676.0 of the Operational Data Reporting Management Pack was updated to fix an issue where the Management Packs ODR report would fail to submit data.

Changes in February 2010 Release

The February 2010 release of the Operations Manager Management Pack included an updated version of the Operational Data Reporting Management Pack (ODR.MP version 6.1.7599.0), which is installed with Operations Manager. The Operational Data Reporting Management Pack gathers information and sends reports to Microsoft on a weekly basis (if you select to send reports). Microsoft uses these reports to improve the quality of its management packs and Operations Manager 2007. Participation in the program is strictly voluntary. For more information, see Appendix: Operational Data Reporting Management Pack.

No changes have been made to the Operations Manager Management Pack. After you download the management packs, you should only import the Operational Data Reporting Management Pack.

Changes in Version 6.0.6709.0

Version 6.0.6709.0 of the Operations Manager Management Pack for Operations Manager 2007 includes the following changes:

  • Updated the layout and default filters and sort order for a number of views.

  • Fixed an issue that was previously preventing all rules related to agentless exception monitoring from generating alerts.

  • Added display names, descriptions, and product knowledge where missing.

  • Added the rule “Collects Opsmgr SDK Service\Client Connections” to collect the number of connected clients for a given management group. This data is shown in the view “Console and SDK Connection Count” under the folder “Operations Manager\Management Server Performance”.

  • Updated a number of monitors and rules to ensure that data is reported to the correct management group for multihomed agents.

  • The following rules and monitors are now disabled by default as they are generally not actionable:

    • A GroupPopulator module unloaded due to an unrecoverable error

    • Health Service Cannot Find Management Group

    • Data Validity Check

    • Root Connector Data Validity Check

  • Added event collection rule for events 5400, 5401, 5402, 5404 5405, and 5500.

  • Updated the alert suppression criteria for the rule “Alert on Dropped MultiInstance Performance Module” in order to significantly reduce the alert volumes generated by this rule and make it easier to identify the root cause.

  • The implementation that triggers the “Restart Health Service” recovery was changed to be driven by monitors as opposed to rules, to address a number of shortcomings in the previous design.

  • Changed the default severity and priority of alerts raised by the “SDK Spn Registration” rule from “warning” to “critical” and updated the knowledge for the rule significantly.

  • Fixed an issue in which the “RunAs Authorization Check” alert could be incorrectly auto-resolved.

  • Added the “Communication Certificate Expiration Check” monitor to monitor certificate expiration for untrusted domain endpoints (agents, gateways, servers) and alert before the certificate expires.

  • Added event details to the “Secure Storage Configuration Check” monitor alert.

  • Changed the time-out value of the “Log Distributed Workflow Test Event” to 300 seconds.

  • Fixed an issue with the “Management Configuration Service - Windows Service State” monitor so that it will properly generate alerts for the state of the “OpsMgr Config Service” on a clustered root management server.

  • Fixed the “Operational Database Space Free (%)” monitor to compute free space based on maximum data file size, rather than maximum data and log file sizes combined.

  • Updated the workflows that drive the state of the “Computer Not Reachable” monitor to handle the condition when the computer’s name does not resolve.

  • Added additional criteria to the rule “WMI Raw Performance Counter Module Execution Failure” to account for some event IDs that were not being detected.

  • Removed criteria from the rule “Performance Data Source Module could not find a performance counter” to avoid generating alerts on warning events.

社群新增項目

顯示: