Supported Configurations

  • Article

Applies To: Operations Manager 2007

The Windows Server Failover Cluster Management Pack for Microsoft System Center Operations Manager 2007 is supported on the following configurations:

  • Windows Server 2003 operating systems with Service Pack 1 (SP1) and Service Pack 2 (SP2) on 32-bit and 64-bit servers.

  • Windows Server 2003 R2 operating systems with Service Pack 1 (SP1) and Service Pack 2 (SP2) on 32-bit and 64-bit servers.

  • Windows Server 2008 Enterprise, Windows Server 2008 R2 Enterprise, Windows Server 2008 Datacenter, and Windows Server 2008 R2 Datacenter operating systems on 32-bit and 64-bit servers.

    • This management pack is also supported on the Server Core installation option of the Windows Server 2008 and Windows Server 2008 R2 operating systems.

Note

The specific Windows Server Failover Cluster Management Pack for Operations Manager 2007 is not supported on the Windows Server 2008 R2 Web and Standard operating systems because the Cluster service is not supported on these editions.

All support is subject to Microsoft’s overall support lifecycle (https://go.microsoft.com/fwlink/?Linkid=26134) and the Operations Manager 2007 SP1 Supported Configurations (https://go.microsoft.com/fwlink/?Linkid=90676) document.

This management pack supports monitoring of a maximum of 300 resource groups per monitored cluster. In Hyper-V clusters with more than 300 resource groups, it is strongly recommended that you also use the System Center Virtual Machine Manager Management Pack to complement the monitoring provided by the Cluster Management Pack.

The management pack is configured to check the health of clustered resource groups every five minutes. During this time, the CPU will briefly spike while the management pack communicates with the cluster service and calculates the health state of the monitored resource groups. The five minute polling interval can be changed for the Resource Group State monitor by using overrides, but an interval less than 60 seconds is not recommended, especially if you are monitoring many resource groups. In tests with 300 resource groups, CPU spikes that last for 2-3 seconds with an overall CPU utilization increase of less than 3% have been observed.

Resource monitoring is disabled by default because appropriate monitoring is provided by resource group monitoring. Enabling resource monitoring may impact agent CPU utilization on the cluster is the total number of monitored resources and resource groups exceeds 300. For more information on discovery defaults, see Discovery and Monitoring of Resources and Resource Groups.