7.4

Table 7‑1. Files to Update When Changing a Web Node Host Name (Continued)
IaaS Server Path File
Agent nodes install-folder\Agents\agent-name RepoUtil.exe.config
install-folder\Agents\agent-name VRMAgent.exe.config
Table 7‑2. Files to Update When Changing a Manager Service Node Host Name
IaaS Server Path File
DEM Orchestrator nodes install-folder\Distributed Execution
Manager\DEM-name
DynamicOps.DEM.exe.config
DEM Worker nodes install-folder\Distributed Execution
Manager\dem
DynamicOps.DEM.exe.config
Agent nodes install-folder\Agents\agent-name VRMAgent.exe.config
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.
Installing vRealize Automation
VMware, Inc. 141