Run As Profiles

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

When the SQL Server Core Library Management Pack is first imported, it creates three new Run As profiles:

• SQL Server Default Action Account

• SQL Server Discovery Account

  This profile is associated with all discoveries.

• SQL Server Monitoring Account

  This profile is associated with all monitors and tasks.

By default, all discoveries, monitors, and tasks defined in the SQL Server management packs default to using the accounts defined in the “Default Action Account” Run As profile. If the default action account for a given system does not have the necessary permissions to discover or monitor the instance of SQL Server, then those systems can be bound to more specific credentials in the SQL Server Run As profiles, which do have access.

The following steps help you configure Run As profiles for SQL Server:

To configure Run As profiles

1. Identify the names of the target computers where the default action account has insufficient rights to monitor SQL Server.

2. For each system, create or use an existing set of credentials that have at least the SQL Server privileges discussed in the Low-Privilege Environments section of this management pack guide.

3. For each set of credentials identified in step 2, make sure a corresponding Run As account exists in the management group. Create the Run As account if necessary.

4. Set up the mappings between the targets and the Run As accounts on the Run As Accounts tab of each of the Run As profiles. Use the following table to identify mappings.

   Run As Profile	Targets
   SQL Server Discovery Account	Classes: Windows Server SQL Server 2005 DB Engine SQL Server 2008 DB Engine SQL Server 2012 DB Engine SQL Server 2005 Agent SQL Server 2008 Agent SQL Server 2012 Agent SQL Server 2008 Mirroring DB SQL Server 2008 Mirroring Witness Groups: SQL 2005 Computers SQL 2008 Computers SQL 2012 Computers SQL Server 2008 Mirroring Group SQL 2005 DB Engine Group SQL 2008 DB Engine Group SQL 2008 R2 DB Engine Group SQL 2012 DB Engine Group
   SQL Server Monitoring Account	Classes: SQL Server 2005 DB Engine SQL Server 2008 DB Engine SQL Server 2012 DB Engine SQL Server 2005 DB SQL Server 2008 DB SQL Server 2012 DB SQL Server 2005 DB File SQL Server 2008 DB File SQL Server 2012 DB File SQL Server 2005 DB Log File SQL Server 2008 DB Log File SQL Server 2012 DB Log File SQL Server 2005 Agent SQL Server 2008 Agent SQL Server 2012 Agent SQL Server 2005 Agent Job SQL Server 2008 Agent Job SQL Server 2012 Agent Job SQL Server 2005 DB File Group SQL Server 2008 DB File Group SQL Server 2012 DB File Group SQL Server 2005 Analysis Services SQL Server 2008 Analysis Services SQL Server 2012 Analysis Services SQL Server 2005 Integration Services SQL Server 2008 Integration Services SQL Server 2012 Integration Services Groups: SQL 2005 DB Engine Group SQL 2008 DB Engine Group SQL 2008 R2 DB Engine Group SQL 2012 DB Engine Group
   SQL Server Default Action Account	Classes: SQL Server 2005 DB Engine SQL Server 2008 DB Engine SQL Server 2012 DB Engine SQL Server 2005 Agent SQL Server 2008 Agent SQL Server 2012 Agent SQL Server 2005 Analysis Services SQL Server 2008 Analysis Services SQL Server 2012 Analysis Services SQL Server 2005 Integration Services SQL Server 2008 Integration Services SQL Server 2012 Integration Services SQL Server 2005 DB SQL Server 2008 DB SQL Server 2012 DB SQL Server 2005 Reporting Services SQL Server 2008 Reporting Services SQL Server 2012 Reporting Services SQL Server 2005 Agent Job SQL Server 2005 Agent Job SQL Server 2008 Agent Job SQL Server 2012 Agent Job Groups: SQL 2005 DB Engine Group SQL 2008 DB Engine Group SQL 2008 R2 DB Engine Group SQL 2012 DB Engine Group

For more information, see Run As Profiles and Run As Accounts in Operations Manager 2007 and the Low-Privilege Environments section.