Configure the vSphere agent in preparation for creating and using vSphere endpoints within vRealize Automation blueprints.

Before you begin

Using an account with administrator privileges, log in to the IaaS Windows server where you installed the vSphere agent.

About this task

You use the proxy agent utility to modify encrypted portions of the agent configuration file, or to change the machine deletion policy for virtualization platforms. Only part of the VRMAgent.exe.config agent configuration file is encrypted. For example, the serviceConfiguration section is unencrypted.

Procedure

  1. Open a Windows command prompt as an administrator.
  2. Change to the agent installation folder, where agent-name is the folder containing the vSphere agent.

    cd %SystemDrive%\Program Files (x86)\VMware\vCAC\Agents\agent-name

  3. (Optional) : To view the current configuration settings, enter the following command.

    DynamicOps.Vrm.VRMencrypt.exe VRMAgent.exe.config get

    The following is an example of the command output.

    managementEndpointName: VCendpoint
    doDeletes: True

  4. (Optional) : To change the name of the endpoint that you configured at installation, use the following command.

    set managementEndpointName

    For example: DynamicOps.Vrm.VRMencrypt.exe VRMAgent.exe.config set managementEndpointName my-endpoint

    You use this process to rename the endpoint within vRealize Automation, instead of changing endpoints.

  5. (Optional) : To configure the virtual machine deletion policy, use the following command.

    set doDeletes

    For example: DynamicOps.Vrm.VRMencrypt.exe VRMAgent.exe.config set doDeletes false

    Option

    Description

    true

    (Default) Delete virtual machines destroyed in vRealize Automation from vCenter Server.

    false

    Move virtual machines destroyed in vRealize Automation to the VRMDeleted directory in vCenter Server.

  6. (Optional) : To require a trusted certificate for the vSphere agent, modify VRMAgent.exe.config in a text editor.

    In the serviceConfiguration section, set the trustAllCertificates parameter to false.

    trustAllCertificates = "false"

    Because the setting is unencrypted, you do not use a DynamicOps.Vrm.VRMencrypt.exe VRMAgent.exe.config set trustAllCertificates false command.

    Option

    Description

    true

    (Default) The vSphere agent does not require a trusted certificate from vCenter Server.

    false

    The vSphere agent requires a trusted certificate from vCenter Server.

  7. Open Administrative Tools > Services and restart the vRealize Automation Agent – agent-name service.

What to do next

For high-availability, you can install and configure a redundant agent for your endpoint. Install each redundant agent on a separate server, but name and configure the agents identically.