8.3 Installing Agents Remotely

After you install a QDB, management server, agent, and Control Center components, you can use Control Center to install more agents to remote Windows computers. If you use Control Center to deploy agents to remote computers, you must also deploy the AppManager for Microsoft Windows module to those computers. The module is not automatically deployed with the agent.

In Control Center, you will specify a user account to run the agent installation package. Ensure that the account has the required Group Policy object (GPO) setting. The account must be a member of the Replace a process level token policy, which determines the user accounts that can call the CreateProcessAsUser() application programming interface (API) so that one service can start another. By default, only local system accounts are members of the policy. You can edit the policy in the default domain controller GPO and in the local security policy of workstations and servers. The policy is located in the following path in the Microsoft Management Console:

Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment

For more information about installing agents to remote Windows computers, see the Control Center User Guide for AppManager, available on the AppManager Documentation page. For information about installing agents remotely on UNIX or Linux computers, see the AppManager for UNIX and Linux Servers Management Guide, available on the AppManager Modules Documentation page.

If you want to use Performance Monitor to monitor the operational health and performance of the agent, you must install the counters on the agent computer. For more information about installing the counters, see Installing Agent Performance Counters.