When maintaining an environment or network, you might need to assign a different host name to an existing vRealize Automation IaaS Windows server.

Procedure

  1. Take a snapshot of the IaaS server.
  2. On the IaaS server, use IIS Manager to stop the vRealize Automation application pools: Repository, VMware vRealize Automation, and Wapi.
  3. On the IaaS server, use Administrative Tools > Services to stop all vRealize Automation services, agents, and DEMs.
  4. In DNS, create an additional record with the new host name.

    Do not remove the existing DNS record with the old host name yet.

  5. Wait for DNS replication and zone distribution to occur.
  6. On the IaaS server, change the host name, but do not restart when prompted.

    Look for the host name in the Windows system properties, under the computer name, domain, and workgroup settings.

    When prompted to restart, click the option to restart later.

  7. If you used the old host name to generate certificates, update certificates.

    For more information, see Updating vRealize Automation Certificates.

  8. Use a text editor to locate and update the host name inside configuration files.

    Make the updates based on which IaaS server host name you changed. In a distributed HA deployment, you might need to access more than one server. There are no updates if you change the host name of a DEM Orchestrator or DEM Worker.

    Note:

    Only update the old Windows server host name. If you find a load balancer name instead, keep the load balancer name.

    Table 1. Files to Update When Changing a Web Node Host Name

    IaaS Server

    Path

    File

    Web nodes

    install-folder\Server\Website

    Web.config

    install-folder\Server\Website\Cafe

    Vcac-Config.exe.config

    install-folder\Web API

    Web.config

    install-folder\Web API\ConfigTool

    Vcac-Config.exe.config

    Node with the Model Manager component installed

    install-folder\Server\Model Manager Data

    Repoutil.exe.config

    install-folder\Server\Model Manager Data\Cafe

    Vcac-Config.exe.config

    Manager Service nodes

    install-folder\Server

    ManagerService.exe.config

    DEM Orchestrator nodes

    install-folder\Distributed Execution Manager\dem

    DynamicOps.DEM.exe.config

    DEM Worker nodes

    install-folder\Distributed Execution Manager\DEM-name

    DynamicOps.DEM.exe.config

    Agent nodes

    install-folder\Agents\agent-name

    RepoUtil.exe.config

    install-folder\Agents\agent-name

    VRMAgent.exe.config

    Table 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 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. In DNS, remove the existing DNS record with the old host name.
  13. Wait for DNS replication and zone distribution to occur.

What to do next

Validate that vRealize Automation is ready for use. See the vRealize Suite Backup and Restore documentation.