You can use the proxy agent utility to modify the initial configurations that are encrypted in the VRMAgent.exe.config file agent configuration file, or to change the machine deletion policy for virtualization platforms.

About this task

Configure the vSphere agent in preparation for creating and using vSphere endpoints to be used in vRealize Automation blueprints.

Note:

Some portions of the file are encrypted, while others are not. For example, the serviceConfiguration section of VRMAgent.exe.config is not encrypted.

Prerequisites

Log in as a system administrator to the machine where you installed the vSphere agent.

Procedure

  1. Open a Windows command console as an administrator.
  2. Go to the agents installation directory.

    For example, cd Program Files (x86)\VMware\vCAC\CD Agents\agent_name.

  3. (Optional) : Enter DynamicOps.Vrm.VRMencrypt.exe VRMAgent.exe.config get to view the current configuration settings.

    The following is an example of the output of the command:

    managementEndpointName: VCendpoint
    doDeletes: True
  4. (Optional) : Enter the set managementEndpointName command to change the name of the endpoint you configured at installation.

    For example, DynamicOps.Vrm.VRMencrypt.exe VRMAgent.exe.config set managementEndpointName My Endpoint.

    You change this property to rename the endpoint within vRealize Automation instead of changing endpoints.

  5. (Optional) : Enter the set doDeletes command to configure the virtual machine deletion policy.

    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) : Require a trusted certificate for the vSphere agent by setting the trustAllCertificates parameter to false using the following statement in the serviceConfiguration section of the VRMAgent.exe.config file:
    trustAllCertificates = "false"

    Because this setting is not encrypted, you cannot use the 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. Navigate to Start > Administrative Tools > Services and restart the vRealize Automation Agent – agentname 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.