7.3

Table 7‑3. Files to Update When Changing an Agent Node Host Name
IaaS Server Path File
Agent node install-folder\Agents\agent-name VRMAgent.exe.config
9 Restart the IaaS server where you changed the host name.
10 Start the vRealize Automation application pools that you stopped earlier.
11 Start the vRealize Automation services, agents, and DEMs that you stopped earlier.
12 If the old IaaS server host name was used with a load balancer in an HA environment, check and
reconfigure the load balancer with the new name.
13 In DNS, remove the existing DNS record with the old host name.
14 Wait for DNS replication and zone distribution to occur.
15 If you changed the host name of a Manager Service host, take the following additional steps.
a Update software agents on existing virtual machines.
b Recreate any ISOs or templates that contain a guest agent.
What to do next
Validate that vRealize Automation is ready for use. See the vRealize Suite Backup and Restore
documentation.
Set the vRealize Automation Login URL to a Custom Name
If you want vRealize Automation users to log in to a URL name other than the vRealize Automation
appliance or load balancer name, take customization steps before and after installation.
Procedure
1 Before installing, prepare a certificate that includes the CNAME that you want, as well as
vRealize Automation appliance and load balancer names.
2 Install vRealize Automation, entering the appliance or load balancer name as usual. During
installation, import the customized certificate.
3 After installing, in DNS, create a CNAME alias of Common Name, and point it to the appliance or load
balancer VIP address.
4 Log in to the vRealize Automation appliance administrator interface as root.
https://vrealize-automation-appliance-FQDN:5480
5 Under vRA Settings > Host Settings, change the Host Name to the CNAME that you chose.
Installing vRealize Automation
VMware, Inc. 142