Install agents remotely


If you have the correct permissions and network access to remote nodes, you can install agents onto the nodes from the console. To remotely install agents, the management server requires the credentials of a user who has administrative access to the node. The following table shows the specific permissions required, according to the node's operating system, and the type of agent.

  HTTPS agent DCE agent
Windows operating systems
  • Write access to the admin$ share (the user must be part of the local administrators group)
  • Read access to the registry
  • Permission to log on as a service (this is only required if you select User/Password in the Set Credentials list)
  • Write access to the registry
  • Write access to the admin$ share (the user must be part of the local administrators group)
  • Write access to the Program Files folder
  • Permission to create DCOM (Distributed Component Object Model) connections
UNIX or Linux operating systems
  • Permission to log in to SSH on the node for file transfers and to execute installation commands
  • Not applicable. Only manual installation is possible.

Remote agent installation is supported from management servers that belong to an Active Directory domain. If your management server is in a Windows workgroup environment, install agents manually instead.

To install agents remotely

  1. Optional. For up-to-date information on supported agent platforms, see the support matrix at HP Software Support Online.

  2. Open the Agent installation dialog box if it is not already open. Click for details.

    You can open the Agent installation dialog box in the following ways:

    • Create new nodes in the Configure managed nodes dialog box. The Agent installation dialog box opens after you click OK. (See Create new nodes.)
    • Right-click a node in the Configure managed nodes dialog box, and then click Run agent installation. (See Configure managed nodes.)
    • Deploy policies to nodes on which no agent is current installed. (See Policy deployment.)
    • Deploy the agent package to nodes on which no agent is currently installed. (See Deploy deployment package.)
  3. Optional. In the list of nodes, select or clear the Deploy check box to indicate the nodes that you want to install the agent on.

    If you select the Deploy check box for nodes that have a UNIX or Linux operating system, the Credentials dialog box appears. Type the Username of a user who has permission to install software on the node. Type the password in Password and Repeat Password.

  4. Optional. Specify the credentials that the management server uses to deploy the agent. Right-click a node in the list, and then click Set Credentials. Click one of the following commands:
  5. Optional. Select or clear the Run prerequisites check automatically during job execution check box. If a node does not meet any of the prerequisites, the agent installation fails for that node. If you are sure that the nodes meet all prerequisites, you can clear this check box so that the agent installation jobs complete more quickly. (This check box is dimmed if an administrator disables all prerequisite checking using the Server Configuration dialog.)
  6. Click OK. The management server creates an agent installation job for each of the nodes that you selected. To view the progress of these jobs, click Deployment jobs in the console tree. If an agent installation job fails, right-click the job, and then click Error description.

Note NOTE:
The management server does not create a deployment job if the agent package is already in the node's package inventory. If a node's package inventory contains the agent package, but you are sure that the agent is not actually installed on a node, you can force the management server to remove the agent package from the inventory in the Uninstall package from... dialog. For more information, see Remove package from node.

Related Topics: