Configure the vSphere agent in preparation for creating and using vSphere endpoints within vRealize Automation blueprints.
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.
Using an account with administrator privileges, log in to the IaaS Windows server where you installed the vSphere agent.
- Open a Windows command prompt as an administrator.
- 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
- (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
- (Optional) To change the name of the endpoint that you configured at installation, use the following command.
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.
- (Optional) To configure the virtual machine deletion policy, use the following command.
DynamicOps.Vrm.VRMencrypt.exe VRMAgent.exe.config set doDeletes false
(Default) Delete virtual machines destroyed in vRealize Automation from vCenter Server.
Move virtual machines destroyed in vRealize Automation to the VRMDeleted directory in vCenter Server.
- Open vRealize Automation Agent – agent-name service. and restart the
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.