2.8 Permissions for Running Knowledge Scripts

AppManager for Microsoft SharePoint Server requires that the NetIQ AppManager Client Resource Monitor (netiqmc) and the NetIQ AppManager Client Communication Manager (netiqccm) agent services use one of the following account types:

  • Agent User account

  • Domain account

  • Farm setup account (the user account used to set up the SharePoint server)

2.8.1 Changing Account Types of Agent Services

You can change the account type for the netiqmc and netiqccm agent services. If you use the farm setup account, you do not need to do any additional configuration for the account type.

For information about creating an Agent User account and a Domain account, see Section 2.8.2, Creating an Agent User Account and Section 2.8.3, Creating a Domain Account.

To change the account type of the agent services:

  1. Start the Services Administrative Tool. To do this, you can open the Administrative Tools folder in the Control Panel.

  2. Right-click the NetIQ AppManager Client Communication Manager (netiqccm) service in the list of services, and select Properties.

  3. On the Logon tab, specify the appropriate account to use.

  4. Click OK.

  5. Repeat Step 2 through Step 4 for the NetIQ AppManager Client Resource Monitor (netiqmc) service.

  6. Restart both services.

2.8.2 Creating an Agent User Account

You can create a new local user called Agent User for the netiqmc and netiqccm agent services.

To create the Agent User:

  1. Create a new local user named Agent User on the agent computer, and give the Agent User local administrator permissions for that computer.

  2. Repeat Step 1 for each SharePoint server in the farm.

  3. On the SQL Server computer, create a new local user named Agent User, and give the Agent User normal user permissions (non-administrator).

  4. On the SQL Server computer, add Agent User to the database logins.

  5. On the SharePoint configuration database, add Agent User to the Users, and add the following Role memberships:

    • db_datareader

    • db_denydatawriter

    • SharePoint_Shell_Access (SharePoint Server 2010 and later.)

    • WSS_Content_Application_Pools (needed to run stored procedures, or sprocs)

  6. For each SharePoint content database, add Agent User to the list of Users.

  7. (Conditional) If you are running SharePoint Server 2010 or later, for the logging database, give Agent User the following Role memberships (this allows the WebPagePerf Knowledge Script to run):

    • db_denydatawriter

    • db_owner

  8. For each SharePoint content database, give Agent User the following Role memberships:

    • db_denydatawriter

    • db_owner

  9. (Conditional) If you are running SharePoint Server 2010 or later, set up the account as a site collection administrator by running the following command: Set-SPSite -Identity "SiteCollectionURL" -SecondaryOwnerAlias "ComputerName\Username"

  10. Repeat Step 9 for all site collections.

2.8.3 Creating a Domain Account

If you are running SharePoint Server 2010 or later, you can create a new domain account for the netiqmc and netiqccm agent services.

To create the domain account:

  1. Click Start > Programs > Administrative Tools > Active Directory Users and Computers.

  2. Create a new domain account, such as MyDomain\SharePoint, and give the new domain account administrator permissions for each SharePoint server in the farm.

    NOTE:You do not need grant any permissions on the SQL server computer.

  3. Log on to any SharePoint server with the farm setup account (the user account used to set up the SharePoint server).

  4. Open the SharePoint Management shell.

  5. At the Windows PowerShell command prompt, type the following commands to assign the account to the SharePoint_Shell_Access role on the SharePoint content databases, and to make the account a member of the WSS_ADMIN_WPG local group on all servers in the farm:

    • $db = get-SPContentDatabase "ContentDBName"

    • Add-SPShellAdmin -Username "Domain\Username" -database $db

  6. Set up the account as a site collection administrator by running the following command: Set-SPSite -Identity "SiteCollectionURL" -SecondaryOwnerAlias "Domain\Username"

  7. Repeat Step 6 for all site collections.

  8. For the logging database, give Agent User the following Role memberships (this allows the WebPagePerf Knowledge Script to run):

    • db_denydatawriter

    • db_owner