| « Windows cannot bind to domain. (Invalid Credentials). Group Policy processing aborted. | Updates to the Exchange Management Packs for Operations Manager 2007 » |
Failover Clustering Management Pack updated
Windows 2008, SCOM, SQL, Exchange, System Center
A fresh update to the Windows Failover Clustering Management Pack has been released.
Some of the major updates in this release are
- Support for discovery and monitoring of Windows Server 2008 R2 clusters and functionality such as Cluster Shared Volumes
- MP scalability improvements (the MP supports monitoring of 300 resource groups per cluster)
- Noise reduction, for example clustered resources are no longer discovered and monitored by default (resource groups are monitored by default)
And from the MP guide a bit more information:
· Added support for discovery and monitoring of Windows Server 2008 R2 clusters.
· Disabled discovery and monitoring of resources by default.
· Discovers and monitors cluster shared volume resources only on Windows Server 2008 R2 clusters.
· Limited discovery of resource groups to a maximum of 300 resource groups per cluster.
· Disabled discovery of clustered objects on an Operations Manager root management server (RMS) cluster running Operations Manager 2007 R2.
· Fixed an issue where the DiscoverClustering.vbs script would fail to submit discovery data when there were WMI provider issues on the cluster node.
· Updated display strings and knowledge in the management pack.
· Updated discoveries to run every 4 hours.
· Updated the MAC Address property for the network adapter to use hyphens instead of colons.
· Disabled the Windows Time Service monitor for Windows Server 2008 and Windows Server 2008 R2 clusters because the cluster service has no dependency on the Time service.
· Disabled the WMI service monitor for all operating system versions of the management pack because the cluster service has no dependency on the WMI service.
· Added a Sync Time parameter to the discoveries and monitors for resources and resource groups to ensure that these do not run simultaneously or immediately after an agent is restarted.
· Disabled the following rules on Windows Server 2003, Windows Server 2008 and Windows Server 2008 R2 clusters, which would cause discovery to instantly run when cluster properties changed:
· Cluster object property changed
· Cluster object added
· Cluster object removed
· Cluster object changed property value
· Cluster object space changed due some addition
· Cluster object space changed due some deletion
. Cluster changes are now discovered on a schedule (by default, every 4 hours).
Comment feed for this post
This is because Cluster Shared Volume is a feature introduced with Windows server 2008 R2 and did not exist in Windows 2003 yet.
Hope you can help me out with this problem. My business user require file count monitoring. There’s already a “File System Management Pack” that can do this. It works only on Folder Share created local (c:\) on any Operating System. The issue is my business user system is on a Cluster File Server running Windows Server 2003 Enterprise x32. The File System Management Pack will not see any shares created on “Cluster Volume”. After reading the guild for Microsoft Windows Server Cluster Ver: 6.0.6720.0 MP, I setup File Cluster running Windows Server 2008 R2 and share the folder on the “Cluster Volume”, it works. The guild specify it will only discover Cluster Share Volume on Windows Server 2008 R2. I also override the “Discover Cluster Share Volume on Windows Server 2003”, but this feature is not working. Is there any way to getting Folder Share discover on Cluster Volume on Windows Server 2003? Do you have any suggestion to making this work?