A new Base OS MP Version 6.0.7026.0 has shipped. This management pack includes updated MP’s for Windows 2003 through Windows 2012 operating systems. This updated MP will import into OpsMgr 2007 or 2012 management groups.
Ok – so what’s new in this MP?
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.
These fixes address the majority of known issues discussed in my last article on the Base OS MP:
A note on Processor utilization monitoring and collection:
Distinct rules and monitors were created for Windows Server 2008, and 2008 R2. Server 2008 will monitor and collect “Processor\% Processor Time” while Server 2008 R2 will monitor and collect “Processor Information\% Processor Time”. Overrides were included in the MP to disable the “2008” rules and monitors for the 2008 R2 instances. If for some reason you prefer to collect and monitor "from “Processor” instead of “Processor Information”, for instance if this breaks some of your existing reports, it is very simple to just override those rules and monitors back to enabled. An unsealed override will always trump a sealed override.
Known Issues in this MP:
1. The knowledge for the 2008 and 2008 R2 Total CPU Utilization Percentage is incorrect – the monitor was updated to a default value of 3 samples but the knowledge still reflects 5 samples. This is still an issue (no biggie) The 2012 monitors use 5 samples by default with correct knowledge.
2. There are now collection rules for Cluster disks and CSV for free space (MB), free space (%), and total size (MB), If you want performance reports on other perfmon objects that are available in perfmon but not included in our MP, such as disk latency, idle time, etc., you will need to create these. Since this can be complicated to get it right – I wrote an article on how to do this correctly, and offer a sample MP for download: http://blogs.technet.com/b/kevinholman/archive/2012/09/27/opsmgr-authoring-performance-collection-rules-for-cluster-disks-the-right-way.aspx
3. The new monitor for Max Concurrent API has some issues and will generate a false alert in some cases. If you have servers where this is happening – disable this monitor and it will be addressed in the next release of the MP.