Changes in This Update

  • Article

Applies To: Operations Manager 2007 R2

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

  • Added the “Agents by Health State” report which will list all agents, management servers, gateway servers and the root management server grouped by their current health state (i.e. unavailable, error, warning or success). For more information, see Appendix: Reports.

  • Added the “An alert subscription has been automatically disabled due to invalid configuration” rule to generate an alert when an alert subscription is disabled due to invalid configuration, such as when the account that created the subscription being deleted.

  • Added the “WMI Service Availability” aggregate monitor and the “Windows Management Instrumentation Service” unit monitor to monitor the state of the Windows Management Instrumentation (WMI) service (winmgmt) on agents. By default, the unit monitor samples the WMI service every 125 seconds and generates an alert when the WMI service is not running for 3 consecutive samples. These settings can be changed by using overrides.

  • Added rules to that can be enabled in place of monitors that require manual reset of the health state. For more information, see Manual Reset Monitors.

  • Updated product knowledge for some workflows.

  • Changed the "Computer Verification: Verification Error" event collection rule to be disabled by default. The alert from this rule would only be generated when running the discovery wizard, when the user would directly observe that one or more computer verifications failed. The alert is an unnecessary duplication.

  • Change the “Collect Configuration Parse Error Events” rule to be disabled by default.

  • Changed the parameter used for alert suppression for the following rules:

    • Alert generation was temporarily suspended due to too many alerts

    • Workflow Runtime: Failed to access a Windows event log

    • Workflow Initialization: Failed to initialize access to an event log

    • An error occurred during computer verification from the discovery wizard

    • A generic error occurred during computer verification from the discovery wizard

  • Removed alerting from the “Data Integrity” aggregate monitor and added alerting to its unit monitors:

    • Repeated Event Raised

    • Spoofed Data Check

    • Root Connector Data Validity Check

The Operational Data Reporting Management Pack has not changed in this release. The version number of the Operational Data Reporting Management Pack was updated to keep the versions the same across all of the management packs in this package.

Changes in July 2010 Release

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.1.7672.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 Version 6.1.7672.0

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

  • Added the Agent Counts By Date, Management Group and Version report, which compiles information on the Operations Manager agents deployed in your environment. For more information, see Appendix: Reports.

  • Added monitoring of Operations database partitioning and grooming workflows. For more information, see “Monitoring routine database maintenance” in Key Monitoring Scenarios.

  • Added functionality for detecting and repairing duplicate relationships between agents and management servers. For more information, see “Monitoring duplicate relationships between agents and management servers” in Key Monitoring Scenarios.

  • Fixed display strings and product knowledge for various rules and monitors.

  • 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

  • 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

  • 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”

  • Fixed an issue with the display of reports when the time format is set to other than EN-US.

  • Fixed an issue with “Critical Parameter Replacement Failure During Alert Creation” failing to generate an alert.

  • Disabled the “Collect Performance Data Source Module Events” event collection rule and hid the corresponding view, “Performance Data Source Module Events”. The rule collected a significant amount of data which can result in performance problems. The most important events associated with this rule are monitored by the alert-generating rule, “Performance Data Source Module could not find a performance counter”.

  • 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.

  • 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. 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

  • 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.

Changes in Version 6.1.7599.0

Version 6.1.7599.0 of the Operations Manager Management Pack included the following changes:

  • Added functionality that monitors data volume by management pack, workflow, and instance. For details, see the “Analyzing data volume” scenario in Key Monitoring Scenarios.

  • Added monitoring of agent version and compatibility of agent and operating system. For details, see the “Monitoring agent version and architecture mismatch” scenario in Key Monitoring Scenarios.

  • Added monitoring of CPU use by agents and related processes. For details, see the “Monitoring CPU utilization” scenario in Key Monitoring Scenarios.

  • This release of the Operations Manager Management Pack also includes an updated version of the Operational Data Reports Management Pack, 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.

  • Added or updated product knowledge, descriptions, display names, and alert details.

  • Changed the Critical Parameter Replacement Failure During Alert Creation rule to disabled by default because is not actionable; review the product knowledge before enabling this rule.

  • Updated criteria to only show active alerts in the “AD based Agent Assignment Module Alerts” view, which is part of the “AD-based Agent Assignment Module Events Dashboard” view.

  • Aligned monitor states with alert severity for following monitors:

    • Run As Account/Password Expiration Check

    • Alert Subscription Acknowledgement Running Slow

    • Alert Subscription Query Performance Monitor

    • Processing Backlogged Events Taking a Long Time

    • Communication Certificate Expiration Check

  • Enabled auto-resolution for the Run As Account/Password Expiration Check monitor.

  • All monitors have been made public so users can add custom diagnostics and recoveries.

  • Updated the Collects Opsmgr SDK Service\Client Connections rule to sample data every 900 seconds (previously was 300 seconds).

  • Changed the interval for Sql Broker Availability Monitor Type from 10 seconds to 3600 seconds.

  • Renamed the "Health Service Configuration" view folder to "Run As Configuration" to more accurately reflect the folder's new (revised) purpose.

  • Disabled the following event collection rules and removed the associated views because they caused a large amount of data collection that was of limited use to customers:

    • Collect Health Service Configuration Updated Events

    • Collect Management Configuration Service Configuration Updated Events

    • Collect Run As Account Failure Events

    • Collect IIS Discovery Probe Module Events

  • Tuned alert suppression for following rules to reduce alert volumes:

    • Scheduler Condition Module Initialization Failure

    • Scheduler Data Source Module Initialization Failure

    • Timer Condition Module Initialization Failure

  • Fixed bug with the Run As Account(s) Expiring Soon monitor that was preventing state changes and causing event 11903.

Changes in Version 6.1.7533.0

Version 6.1.7533.0 of the Operations Manager Management Pack included the following changes:

  • Changed the time-out value to 1 minute for recovery tasks associated with the following monitors:

    • Health Service Handle Count Threshold

    • Health Service Private Bytes Threshold

    • Monitoring Host Handle Count Threshold

    • Monitoring Host Private Bytes Threshold

  • Changed the threshold values for the Health Service Handle Count Thresholds and Monitoring Host Handle Count Thresholds monitors to 10,000 on management servers and 6,000 on agents.

  • Changed the threshold values for the Health Service Private Bytes Threshold and Monitoring Host Private Bytes Threshold monitors to 1500 MB on management servers and 300 MB on agents.

  • 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 monitors listed below have been updated so that the value of the sample must exceed the threshold for a specific number of consecutive samples, as opposed to the average of the samples over the consecutive samples. This will increase the accuracy of the monitors by handling periodic spikes in resource utilization better:

    • Health Service Handle Count Threshold

    • Health Service Private Bytes Threshold

    • Monitoring Host Handle Count Threshold

    • Monitoring Host Private Bytes Threshold

  • Updated the knowledge for the rule “Data Access Service Spn Registration” significantly.

  • Fixed the configuration of the rule “IIS Discovery Probe Module Execution Failure” to so that the parameter replacement will now work correctly for alert suppression and generating the details of the alert’s description.

Changes in Version 6.1.7221.0

The release of version 6.1.7221.0 of the Operations Manager Management Pack included the following changes:

  • Added rules and monitors to support Operations Manager 2007 R2 features.

  • Added content to knowledge and descriptions.

  • Fixed a problem with discovery of Windows computers that resulted in multiple IP addresses.

  • Updated rules and monitors to ensure that, on multi-homed agents, data is sent only to the appropriate management group.

  • Updated the Discover Windows Computer Properties discovery to support computers in workgroups.

  • Added the /admin switch to tasks that use Remote Desktop, to enable compatibility with Windows Server 2008 and Windows Vista SP1.

  • Reenabled rollup of state from computers to computer groups. For details, see the Knowledge Base article 967537 (https://go.microsoft.com/fwlink/?LinkId=146985).

  • Provided additional error handling in the Discover Health Service Properties discovery.

  • Changed the severity of the alert generated by Data Access Service SPN Registration rule to “critical” to better reflect the importance of the issue.

  • Changed the RunAs Authorization Check to ensure it is not auto-resolved when the health service is restarted.

  • Added a monitor targeting the Health Service class that provides a warning when the authentication certificate is within 2 weeks of expiration.

  • Changed the Log Distributed Workflow Test Event rule time-out from 30 seconds to 300 seconds.

  • Modified the information displayed in the agent updates list to improve readability.

  • Fixed the Configuration Service monitor to generate alerts correctly on clustered root management servers.

  • Fixed a problem in which the agent version was incorrectly discovered on the Operations Manager Reporting server.

  • Fixed the Remote Desktop task for the Health Service Watcher so that it contacts the correct targeted computer.

  • Corrected the knowledge associated with the SDK Spn Registration rule so that it refers correctly to MSOMSdkSvc.

  • Added collection rules to the baseline health model for events related to self-tuning thresholds and baselines.

  • Fixed the Discover Windows Server Properties script to work on Windows 2000 Server. For details, see problem 2 in the Knowledge Base article 951979 (https://go.microsoft.com/fwlink/?LinkId=146986).

  • Changed the behavior of the Operational Database Space Free (%) monitor to more accurately calculate free space.

  • Changed the default sort behavior for Operations Manager -> Notifications -> All Events view.

  • Expanded the scope of the Health Manager events view and added supporting collection rules.

  • Improved the monitoring for “Product Evaluation Has Expired” by changing from rules to monitors with timer reset.

  • Changed the name of the Monitoring Host Events view to Monitoring Host Crash Events to reflect the events collected more accurately.

  • Added monitoring for WMI query failures by capturing WMI event 10457 from source Health Service modules.

  • Fixed a problem with Health Service restart.