Other Requirements

Applies To: Operations Manager 2007, Operations Manager 2007 R2, SQL Server

To run the SQL Management Studio task and the SQL Profiler task, you must have installed SQL Server Management Studio and SQL Server Profiler on all Operations Manager computers where these tasks will be used.

If you try to run one of these tasks without the appropriate features installed, you will receive the error message "The system cannot find the file specified."

You do not need SQL Server Management Studio or SQL Server Profiler for discovery and monitoring.

Configuration for Monitoring Clustered Resources

To monitor clustered resources, perform the following tasks:

  1. Install the Operations Manager agent on each physical node of the cluster.

  2. Enable the Agent Proxy setting on all agents that are installed on servers that are members of the cluster. For instructions, see the procedure that follows this list.

  3. Associate the Windows Cluster Action Account Run As profile with an account that has administrator permissions for the cluster, such as the Cluster service account that is created when you configure the cluster. If the Default Action Account Run As profile for cluster nodes is associated with Local System or with another account that has administrator permissions for the cluster, then no additional associations are required. For instructions on associating an account with a profile, see How to Change the Run As Account Associated with a Run As Profile in Operations Manager 2007.


All agents on clustered nodes need to be running Operations Manager 2007 R2, or Operations Manager 2007 SP1 with the update installed from Knowledge Base article 959865, Issues that are resolved by the Operations Manager Module rollup update for System Center Operations Manager 2007 Service Pack 1. For more information, see “Rules and monitors that are based on events from the event log do not work reliably on clustered installations of SQL” in Appendix: Known Issues and Troubleshooting.

To enable the Agent Proxy setting

  1. Open the Operations console and click the Administration button.

  2. In the Administrator pane, click Agent Managed.

  3. Double-click an agent in the list.

  4. On the Security tab, select Allow this agent to act as a proxy and discover managed objects on other computers.

  5. Repeat steps 3 through 4 for each agent that is installed on a clustered server.

After discovery occurs, each physical node of the cluster is displayed in the Operations console in the Agent Managed pane; the cluster and each named application instance are displayed in the Agentless Managed pane.


Having a SQL Server cluster resource group that contains more than one network name resource might mean that the clustered SQL Server resource is not monitored. For more information, see Knowledge Base article 919594.

To ensure proper monitoring of cluster resources, when you add a resource to a cluster, do not change the name that is assigned to the resource in the Cluster Administrator user interface by default.