In some cases, a vRealize Automation appliance FQDN might change when you do not want it to. For example, the FQDN changes if you create an Integrated Windows Authentication (IWA) directory for a domain other than the domain that the appliance is on.

If you create an IWA directory for another domain, take the following steps to change the appliance FQDN back to the original FQDN.


  1. Log in to vRealize Automation and create the IWA directory as you normally would.
  2. If this is an HA environment, also follow the steps in Configure Directories Management for High Availability.
  3. Creating an IWA directory for a domain other than the one that an appliance is on silently changes the appliance FQDN.

    For example, va1.domain1.local changes to va1.domain2.local when you create an IWA directory for domain2.local.

    Undo the change by renaming each appliance back to its original FQDN. See the associated procedure under Changing Host Names and IP Addresses.

  4. After the appliances are completely back online with their original FQDN, log in to each IaaS node, and take the following steps.
    1. Open the following file in a text editor.

      C:\Program Files (x86)\VMware\vCAC\Management Agent\VMware.IaaS.Management.Agent.exe.Config

    2. Change each appliance endpoint address= FQDN back to the original FQDN.

      For example, from:

      <endpoint address="https://va1.domain2.local:5480/" thumbprint="90C55BAEC53E31609EE1614CE4A8336848A8D4CF" />
      <endpoint address="https://va2.domain2.local:5480/" thumbprint="0468BF6EDBC6F2209BE01D0D7FD1094197E324ED" />


      <endpoint address="https://va1.domain1.local:5480/" thumbprint="90C55BAEC53E31609EE1614CE4A8336848A8D4CF" />
      <endpoint address="https://va2.domain1.local:5480/" thumbprint="0468BF6EDBC6F2209BE01D0D7FD1094197E324ED" />

    3. Save and close VMware.IaaS.Management.Agent.exe.Config.

  5. Log in as root to the vRealize Automation appliance management interface.


  6. Go to vRA settings > Messaging and click Reset RabbitMQ Cluster.
  7. After the reset finishes, log in to each appliance management interface.
  8. Go to vRA Settings > Cluster, and verify that all nodes are connected to the cluster.