After you perform software maintenance, verify that status the Distributed Execution Manager (DEM) and IaaS vSphere Proxy Agents components

After you patch, update, restore, failover, or failback vRealize Automation, verify that the Distributed Execution Manager (DEM) Orchestrators and Workers are online, and that the IaaS vSphere Proxy Agents that connect vRealize Automation to the compute pods are online.


  1. Log in to the vRealize Automation Rainpole portal.
    1. Open a Web browser and go to https://vra01svr01.rainpole.local/vcac/org/rainpole.
    2. Log in using the following credentials.
      Setting Value
      User name itac-tenantadmin
      Password itac-tenantadmin_password
      Domain Rainpole.local
  2. Verify the status of the DEM nodes.
    1. On the Infrastructure tab, click Monitoring > DEM >  Status.
    2. Verify that the status of the DEM-Orchestrator and DEM-Worker virtual machines is Online.
      vRealize Automation Node Virtual Machine
      IaaS Manager Service and DEM Orchestrator vra01ims01a.rainpole.local
      IaaS Manager Service and DEM Orchestrator vra01ims01b.rainpole.local
      vRealize Automation DEM Worker vra01dem01.rainpole.local
      vRealize Automation DEM Worker vra01dem02.rainpole.local

  3. Verify that the vSphere Proxy Agents are working properly.
    1. On the Infrastructure tab, click Compute Resources > Compute Resources.
    2. Verify that the Agent Status for the compute instance is OK.

  4. If the Agent Status for the compute instance is Down, restart the vRealize Automation services on the vSphere Proxy Agent VMs.
    1. Open a Remote Desktop Protocol (RDP) connection to the virtual machine.
      Region Host Name
      Region A



      Region B



    2. Log in using the following credentials.
      Setting Value
      User name Administrator
      Password local_administrator_pwd
    3. From the Windows Start menu, click Administrative Tools, and click Services.
    4. In the Services dialog box, restart the following vRealize Automation services. 
      • VMware vCloud Automation Center Management Agent
      • VMware vCloud Automation Center Agent
    5. If an agent is down after you restart the services, restart the agent VM. 
    6. If the other vSphere Proxy Agent VM is down, repeat the step for it.