UPDATE: MP for monitoring cluster services (MSCS) finally web-released!

  • Article

I made a mistake in my post announcing web release of management packs for monitoring of Failover Clusters. I posted incorrect requirements to meet prior importing management packs. I will correct that information now, especially for OpsMgr 2007 SP1 RC build.

These requirements must be met based on the version of System Center Operations Manager 2007 used:

· All OpsMgr 2007 releases:

Enable the Agent Proxy on all agents which are installed on cluster nodes if it was not enabled already. Then import the Windows Server 2003 Base Operating System Management Pack

· OpsMgr 2007 RTM (version 06.0.5000.0000):

QFE needs to be applied and Microsoft.Windows.Cluster.Library management pack needs to be imported immediately after binaries on cluster nodes changed. This is required due to dependency on cluster user profile in the case action account has no access to cluster administration and profile needs to be manually populated to allow monitoring of MSCS as well as hot fix required for WMI event provider used with cluster infrastructure monitoring.

· OpsMgr 2007 SP1 RC (version 06.0.6246.0000):

No special requirements for runtime are required. But it is required to import Microsoft.Windows.Cluster.Library from QFE (also attached to web released package). This makes sure you can simply follow steps to download files and successfully import management packs.

· OpsMgr 2007 SP1 RTM (version 06.0.6278.0000):

No special requirements are to be met. All referenced management packs are at their latest version. Simply follow steps to download management pack files and import all except Microsoft.Windows.Cluster.Library.

 

Update on new web release:

Bunch of major issues were reported so far as part of the feedback.

1. Offline resource causes critical state set for resource group, while it is only partially online and should have been set to warning.(link)

2. Unable to discover and monitor resource group or resource when special character is present in the name.(link)

3. Full disk notification is too aggressive and causes a flood of alerts to be raised.(link)

Those were addressed already and new web-release will happen shortly. It will also integrate couple of changes necessary for monitoring of Windows 2008 Failover Cluster (coming to web release later).