For those that want to see what can be monitored with the upcoming SharePoint 2016 there is now a management pack to monitor the SharePoint Server 2016 IT Preview:
Features:
Health monitoring of SharePoint Server 2016 IT Preview
Monitors Events and Services and alerts when service outages are detected
Monitors Performance and warns users when SharePoint performance is at risk
Forwards users to up-to-date TechNet knowledge articles
Version 6.0.7297.0 of the Windows server management pack has been released and in available for download here.
Updates in this version:
In 2008, 2012 platforms, the “Logical Disk Free Space (%) Low” monitor do not alert as expected when free space is 0%. With this fix, this monitor will alert when free space is 0%
In all platforms, logical disks are un-discovered if we configure them as Asymmetric storage on Failover Cluster. With this fix, this issue will be resolved
The Windows Server OS Management pack collects logical disk size is megabytes. During discovery this value used to be assigned to integer property. When logical disk size is significantly large (for example, when disk is of several petabytes), in megabytes format it goes out of boundaries of integer type. As a result the workflow fails while trying to insert discovery data. To support large logical disk another double properties was introduced, since double type has much more wide values range. Old integer property with constant “-1” value is preserved for upgrade compatibility and marked as DEPRECETED
“Volume Mount Points on Dynamic Disks” aren’t discovered by Microsoft Windows Server 2012 Discovery MP. With this fix, this issue will be resolved
MP has been modified to not discover System Reserved volumes on Windows Server 2012 to ensure it is consistent with the rest of the OS versions
This is a preview release for Windows Server 2016 Technical Preview Management Packs. The following components of Windows Server 2016 Technical Preview can be monitoring:
A new version of the Exchange 2013 MP has been released version 15.0.666.19 is available for download here.
Fixes in this version:
Fixed a bug that was unable to run Exchange 2013 performance reports when the console is running on a locale different from EN-US.
Exception: System.ArgumentNullException: Value cannot be null. Parameter name: GroupList
Fixed a bug that was causing the collection of Synthetic mailbox performance count data to fail when there are more than 2 management servers. Event 102 is logged on the management servers with the below exception.
Exception: System.Runtime.Serialization.SerializationException: Type ‘System.Object[]’ with data contract name ‘ArrayOfanyType:http://schemas.microsoft.com/2003/10/Serialization/Arrays’ is not expected.
This situation will occur when you try and remove a management pack that utilities a Run As account. You’ll get an error that the management pack is dependent on Microsoft.SystemCenter.SecureReferenceOverride and removing that can be a little bit painful.
Anyone one who has ever removed a management pack with a dependency knows the old method of exporting the management pack, removing the offending refference and importing it back again. The steps for Microsoft.SystemCenter.SecureReferenceOverride are slightly different but the principle is the same.
1. First you need to remove the Run AS account from the Run As Profile
2. Export the Microsoft.SystemCenter.SecureReferenceOverride management pack
3. Edit the management pack and remove the references as you would with any other dependency
4. Increment the management pack version
5. Re import the management pack
Here is a nice method from Matthew Long which uses powershell and doesn’t require any XML editing.
The below is copied for my records, original posting here
Open a powershell session with the Operations Manager module/snappin loaded.
Now we can view the referenced management packs by typing $MP.References
From the list of items in the Key column, note down the alias of your MP you wish to delete. If you are having trouble finding it, the Value column will list the full ID of the MP.
Now that we know the MP alias, we can remove it from the Secure Reference MP by typing $MP.References.Remove(“yourMPAliasGoesHere“)
Now we can verify the MP is valid by entering $MP.Verify() to ensure there are no orphaned overrides, etc.
Finally, we can save our changes by typing: $MP.AcceptChanges()