A system administrator must install at least one vCloud Automation Center EPI agent to manage interaction with HP Server Automation. The agent can be installed anywhere, including the vCloud Automation Center server or the HP Server Automation server, as long as the agent can communicate with both servers.

Verify that the HP Server Automation PowerShell Snap-in is installed on the same host as your EPI agent. If the EPI agent is installed before the snap-in, then the agent service must be restarted after the snap-in is installed. See Install the HP Server Automation PowerShell Snap-In.

The agent must be installed on Windows Server 2008 SP1, Windows Server 2008 SP2 (32 or 64-bit), Windows Server 2008 R2 system, or Windows 2012 with .NET 4.5.

The credentials of the agent must have administrative access to all HP Server Automation hosts with which the agent will interact.

Install the IaaS components, including the Manager Service and Website.

See Installation and Configuration for complete information about installing vCloud Automation Center agents.

Log in to the vCloud Automation Center console as a system administrator.


Select Custom Install and Proxy Agent on the Installation Type page.


Accept the root install location or click Change and select an installation path.


Click Next.


Type the user name and password for the Windows services user with sysadmin privileges on the installation machine.


Click Next.


Select EPI Power Shell from the Agent type list.


Type a unique identifier for this agent in the Agent name text box.

If you plan to use the migration tool, this name must exactly match the name you used in your vCloud Automation Center 5.2.1 or 5.2.2 version. Maintain a record of the name, credentials, and platform instance for each agent. This information is required for adding hosts in the future. Agent names cannot be duplicated unless the agent configurations are identical.


Type the fully qualified domain name and port number, if you are not using the default 443 port, of the machine where you installed the Manager Service component.

For example, hostname.domain.name:444


Type the fully qualified domain name and the port number, if you are not using the default 443 port, of the machine where you installed the Manager Website component.

For example, hostname.domain.name:444


Click Test to verify connectivity to each host.


Click Opsware in EPI Type.


Type the fully qualified domain name of the managed server in the EPI Server text box.

Optionally, you can leave this blank to let the agent interact with multiple hosts.

The HP Server Automation server with which the agent interacts when provisioning a machine by using HP Server Automation depends on the value of the required custom property, EPI.Server.Name, in the blueprint.

Therefore, if you install a dedicated EPI agent by specifying an HP Server Automation server name during installation, only machines whose EPI.Server.Name property exactly matches the server name configured for the agent can be provisioned by that server.

If you install a general EPI agent by not specifying an HP Server Automation server name during installation, a machine can be provisioned by any server specified in the blueprint EPI.Server.Name property, that is assuming the agent can contact that server.


If no matching agent can be found, or there are no agents with unspecified server values, Opsware provisioning will wait until a suitable agent is found.


Click Add.


Click Next.


Click Install to begin the installation.

After several minutes a success message appears.


Click Next.


Click Finish.

Determine the type of integration method to use. See Integrating HP Server Automation.