Export (0) Print
Expand All

Changes in This Update

Updated: June 24, 2013

Applies To: Operations Manager 2007, System Center 2012 - Operations Manager, System Center 2012 R2 Operations Manager, System Center 2012 SP1 - Operations Manager, Windows Server 2012, Windows Server 2012 R2

The October 2013 update (version 6.0.7061.0) of the Windows Server Operating System Management Pack included the following changes:

  • Fixed Windows Server 2012 R2 Beta Monitoring bugs for final release.

Changes in Version 6.0.7043.0

The June 2013 update (version 6.0.7043.0) of the Windows Server Operating System Beta Management Pack included the following changes:

  • Added support for Windows Server 2012 R2 monitoring.

  • Added filter to discovery for Windows Server 2012 and Windows Server 2012 R2.

  • Fixed MaxConcurrentAPI issues.

  • Changed Cluster Discovery to only discover volumes and resource type “Physical Disk”.

  • Added performance rules and reports for Windows Server 2012 R2 that target Windows Server 2012 R2 Operating System.

Changes in Version 6.0.7026.0

The April 2013 update (version 6.0.7026.0) of the Windows Server Operating System Management Pack contains the following changes:

  • Fixed a bug in Microsoft.Windows.Server.2008.Monitoring.mp where the performance information for Processor was not getting collected.

  • Made monitoring of Cluster Shared Volume consistent with monitoring of Logical Disks by adding performance collection rules. (“Cluster Shared Volume - Free space / MB”,”Cluster Shared Volume - Total size / MB”,”Cluster Shared Volume - Free space / %”,”Cluster Disk - Total size / MB”,”Cluster Disk - Free space / MB”,”Cluster Disk - Free space / %”).

  • Fixed bug in Microsoft.Windows.Server.ClusterSharedVolumeMonitoring.mp where the Cluster disks running on Windows Server 2008 (non R2) were not discovered.

  • Fixed bug Cluster Disk Free Space Percent and Cluster Disk Free Space MB' monitors generate alerts with bad descriptions when the volume label of a cluster disk is empty.

Added feature to raise event when NTLM requests time out and customers are unable to use mailboxes, outlook stops responding, due to the low default value for Max Concurrent API registry Key (HLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters), which is a ceiling for the maximum NTLM or Kerberos PAC password validations a server can take care of at a time. It uses the “Netlogon” performance counter to check for the issue.

Changes in Version 6.0.6989.0

The September 2012 update (version 6.0.6989.0) of the Windows Server Operating System Management Pack included the following changes:

  • Introduced support for Windows Server 2012

  • Added monitoring for NTFS events to check if they are corrupted or unavailable

  • Disabled monitoring of Event 55 in Windows 2012 as this event can be raised even if there is no corruption. Event 55 has been replaced with Event 98.

  • Update rules and monitors for Counter Processor Information in the 2008 Management Pack to fix the issue of renaming “Processor” to “Processor Information”.

  • Updated Cluster disk monitoring to fix the warning 999 and the Script error generated when a cluster disk is removed.

Changes in Version 6.0.6972.0

Unless explicitly noted, these updates apply to all operating system versions supported by this Monitoring Pack:

  • Updated the Cluster shared volume disk monitors so that alert severity corresponds to the monitor state.

  • Fixed an issue where the performance by utilization report would fail to deploy with the message “too many arguments specified”.

  • Updated the knowledge for the available MB monitor to refer to the Available MB counter.

  • Added discovery and monitoring of clustered disks for Windows Server 2008 and above clusters.

  • Added views for clustered disks.

  • Aligned disk monitoring so that all disks (Logical Disks, Cluster Shared Volumes, Clustered disks) now have the same basic set of monitors.

    • There are now separate monitors that measure available MB and %Free disk space for any disk (Logical Disk, Cluster Shared Volume, or Clustered disk).

      noteNote
      These monitors are disabled by default for Logical Disks, so you will need to enable them.

    • Updated display strings for all disks to be consistent, regardless of the disk type.

    • The monitors generate alerts when they are in an error state. A warning state does not create an alert.

    • The monitors have a roll-up monitor that also reflects disk state. This monitor does not alert by default. If you want to alert on both warning and error states, you can have the unit monitors alert on warning state and the roll-up monitor alert on error state.

  • Fixed an issue where network adapter monitoring caused high CPU utilization on servers with multiple NICs.

  • Updated the Total CPU Utilization Percentage monitor to run every 5 minutes and alert if it is three consecutive samples above the threshold.

  • Updated the properties of the Operating System instances so that the path includes the server name it applies to so that this name will show up in alerts.

  • Disabled the network bandwidth utilization monitors for Windows Server 2003.

  • Updated the Cluster Shared Volume monitoring scripts so they do not log informational events.

  • Quorum disks are now discovered by default.

  • Mount point discovery is now disabled by default.

noteNote
This version of the Management Pack consolidates disk monitoring for all types of disks as mentioned above. However, for Logical Disks, the previous Logical Disk Free Space monitor, which uses a combination of Available MB and %Free space, is still enabled. If you prefer to use the new monitors (Disk Free Space (MB) Low Disk Free Space (%) Low), you must disable the Logical Disk Free Space monitor before enabling the new monitors.

The default thresholds for the Available MB monitor are not changed, the warning threshold (which will not alert) is 500MB and the error threshold (which will alert) is 300MB. This will cause alerts to be generated for small disk volumes. Before enabling the new monitors, it is recommended to create a group of these small disks (using the disk size properties as criteria for the group), and overriding the threshold for available MB.

Changes in Version 6.0.6958.0

The October 2011 release (version 6.0.6958.0) of the System Center Management Pack for the Windows Server Operating System includes the following changes:

  • Disabled BPA Rules by default

  • Added appropriate SQL Stored Procedures credentials

  • Updated Knowledge of Logical Disks

  • Updated Overrides for Logical Disks

noteNote
The Microsoft.Windows.Server.Reports Management Pack will only import on systems that use SQL Server 2008 as the Database and is not currently supported on SQL Server 2005.

Changes in Version 6.0.6957.0

The September 2011 release (version 6.0.6957.0) of the System Center Management Pack for the Windows Server Operating System includes the following changes:

  • Optimized operating system performance collection rules.

  • Added two new operating system-specific reports:

    • Performance by System

    • Performance by Utilization

  • Added support for the Server Manager Best Practices Analyzer (BPA). The monitoring pack now collects BPA results from monitored servers and returns the BPA state to Operations Manager.

  • Added support to discover and monitor Cluster Shared Volumes (CSV).

  • Modified collection rules to include the latest service packs and hotfixes.

  • Changed the threshold for the “Average Disk Seconds Per Read”, “Average Disk Seconds Per Transfer”, and “Average Disk Seconds Per Write” monitors to 0.04.

  • Added new monitors for “Disk $ Idle Time” and “Current Disk Queue Length”.

  • Changed the monitor types for disk performance from Average Samples to Consecutive Samples to reduce noise and improve collected data.

  • “Logical Disk Availability Monitor” has been renamed to “File System Error or Corruption”.

Changes in Version 6.0.6794.0

The March 2010 release (version 6.0.6794.0) of the Windows Server Operating System Management Pack includes the following change:

  • Updated the script used in the “Discover Windows 2008 Servers” discovery to prevent it from failing completely on computers running Windows Server 2008 R2 when an attempt to query the Win32_PowerPlan class fails.

Changes in Version 6.0.6667.0

The September 2009 release (version 6.0.6667.0) of the Windows Server Operating System Management Pack includes the following changes:

  • Support for Windows Server 2008 R2, including new classes to represent Windows Server 2008 R2 systems specifically.

  • The intervals for some discoveries have been changed to reduce CPU usage. For details, see Objects the System Center Management Pack for Windows Server Operating System Discovers.

  • Added Logical Disk Fragmentation Level monitors for Windows Server 2003 and Windows Server 2008.

  • Disabled the following rules and monitors for Windows Server 2008 because the events needed are in Windows Server 2003 only.

    • Duplicate computer name was detected

    • Windows Activation State

    • Disk Group Failed

    • Disk Group Auto Import Failed

    • Volume Not Started

    • Run WMIAdap

  • Fixed the summary details for the Performance History (Percent Processor Time) report to indicate that the object type is Windows Server 2003 operating system rather than Windows Server 2003 processor.

  • Fixed the Performance History (Percent Interrupt Time) report to use a rule that targets the operating system rather than the processor.

  • Changed the data source for discoveries from System.Scheduler to System.Discovery.Scheduler to avoid performance issues.

  • Changed the Logical Disk Availability monitor to use a Run As profile with administrative privileges to enable it to run in a low-privilege environment.

  • Modified logical disk discovery to exclude hidden mount points, because numerous rules use performance counters that are not applicable to mount points. (A hidden mount point is a mount point with no drive letter or drive path.)

  • Fixed an issue in which an alert could be generated for Windows Activation too early.

  • Addressed an issue that was causing some discoveries to not show up correctly in the authoring section of the console.

  • Improved the product knowledge for the alert generated by the A Service is Misconfigured rule.

  • Fixed issue in which logical disk health check could have performance problems when run against clustered servers.

  • Fixed links to views in product knowledge articles.

  • Added Active Alerts views for Windows Server 2003 and Windows Server 2008.

  • Added retry logic to the "Probe Module: Is Feature Installed" module to avoid failures due to periodic time-outs.

  • Added a new integer property named "Size (MBytes) (Numeric)" to the Logical Disk class and updated the existing property "Size (Bytes) (String)" to clarify that it is a string. The new property can now be used in formulas and views as expected.

Changes in Version 6.0.6321.5

The October 2008 release (version 6.0.6321.5) of the Windows Server Operating System Management Pack includes the following changes:

  • Various scripts were updated to prevent issues with locale specific number formatting.

Changes in Version 6.0.6278.22

The July 2008 update (version 6.0.6278.22) of the Windows Server Operating System Management Pack included the following changes:

  • Introduced support for Windows Server 2008.

  • Added version specific notations to the names of the performance collection rules to reduce ambiguity, specifically when searching for rules by name.

  • Added a new task to leverage the new “Admin” switch of the remote desktop connection tool. More detail is provided in the “Troubleshooting” section.

  • Updated the logical drive discoveries to omit mapped network drives.

  • Addressed an issue with the Logical Disk Free Space to prevent it from looking like the thresholds were set incorrectly.

  • The state of the configuration of a server now reflects the state of its operating system as well.

  • Fixed an issue with the Server Service Configuration Health monitor which prevented it from ever generating an alert.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft