You must upgrade the SQL database and configure all systems that have IaaS components installed. You can use these steps for minimal and distributed installations.

Note: The IaaS installer must be on the machine that contains the IaaS components you want to upgrade. You cannot run the installer from an external location, except for the Microsoft SQL database which also can be upgraded remotely from the Web node.

Verify that snapshots of the IaaS servers in your deployment are available. If the upgrade fails, you can return to the snapshot and attempt another upgrade.

Perform the upgrade so that services are upgraded in the following order:
  1. IaaS Web sites

    If you are using a load balancer, disable traffic to all non-primary nodes.

    Finish the upgrade on one server before upgrading the next server that is running a Website service. Start with the one that has the Model Manager Data component installed.

    If you are performing a manual external Microsoft SQL database upgrade, you must upgrade the external SQL before you upgrade the Web node. You can upgrade the external SQL remotely from the Web node.

  2. Manager Services

    Upgrade the active Manager Service before you upgrade the passive Manager Service.

    If you do not have SSL encryption enabled in your SQL instance, uncheck the SSL encryption checkbox in the Iaas Upgrade configuration dialog box next to the SQL definition.

  3. DEM orchestrator and workers

    Upgrade all DEM orchestrators and workers. Finish the upgrade on one server before you upgrade the next server.

  4. Agents

    Finish the upgrade on one server before you upgrade the next server that is running an agent.

  5. Management Agent

    Is updated automatically as part of the upgrade process.

If you are using different services on one server, the upgrade updates the services in the proper order. For example, if your site has Web site and manager services on the same server, select both for update. The upgrade installer applies the updates in the proper order. You must complete the upgrade on one server before you begin an upgrade on another.

Note: If your deployment uses a load balancer, the first appliance you plan to upgrade must be connected to the load balancer. All other instances of vRealize Automation appliance appliances must be disabled for load balancer traffic before you apply the upgrade to avoid caching errors.


  • Back up your existing vRealize Automation 6.2.4 or 6.2.5 environment.
  • If you reboot an IaaS server after you update all the vRealize Automation appliances but before you upgrade the IaaS components , stop all of the IaaS windows services, except for the Management Agent service, on the server.
  • Download the IaaS Installer to Upgrade IaaS Components After Upgrading vRealize Automation 6.x to 7.2.
  • Verify that your primary IaaS Website, Microsoft SQL database, and Model Manager node has JAVA SE Runtime Environment 8, 64bits, update 91 or later installed. After you install Java, you must set the environment variable, JAVA_HOME , to the new version on each server node.
  • Verify that the creation date is earlier than the modified date in the web.config file. If the creation date for the web.config file is the same as or later than the modified date, perform the procedure in Upgrade Fails for IaaS Website Component.
  • If you are upgrading from vRealize Automation 6.2.x and have an external Microsoft SQL database, ensure that the Management Agent on the external database is version 7.0 or later before you run the IaaS Web site upgrade. You can check the Management Agent version in the Control Panel of your external SQL machine. If the Management Agent is not version 7.0 or later, complete the following steps to perform a manual upgrade of the Management Agent.
    1. Open a browser and navigate to the VMware vRealize Automation IaaS Installation page on the vRealize Automation appliance at https://virtual_appliance_host:5480/installer.
    2. Download and run the Management Agent Installer.
  • If you have a Common Components Catalog component installed, you must uninstall the component before you upgrade. For more information, see the Common Components Catalog Installation Guide or follow the steps provided in Checklist for Upgrading from vRealize Automation 6.2.4 or 6.2.5.


  1. If you are using a load balancer, prepare your environment.
    1. Verify the IaaS Website node that contains the Model Manager data is enabled for load balancer traffic.
      You can identify this node by the presence of the vCAC Folder\Server\ConfigTool folder.
    2. Disable all other IaaS Websites and non-primary Manager Services for load balancer traffic.
  2. Right-click the setup__vrealize-automation-appliance-FQDN@5480.exe setup file and select Run as administrator.
  3. Click Next.
  4. Accept the license agreement and click Next.
  5. Type the administrator credentials for your current deployment on the Log In page.
    The user name is root and the password is the password that you specified when you deployed the appliance.
  6. Select Accept Certificate.
  7. On the Installation Type page, verify that Upgrade is selected.
    If Upgrade is not selected, the components on this system are already upgraded to this version.
  8. Click Next.
  9. Configure the upgrade settings.
    Option Action
    If you are upgrading the Model Manager Data

    Select the Model Manager Data check box in the vCAC Server section.

    The check box is selected by default. Upgrade the Model Manager data only once. If you are running the setup file on multiple machines to upgrade a distributed installation, the Web servers stop functioning while there is a version mismatch between the Web servers and the Model Manager data. When you have upgraded the Model Manager data and all of the Web servers, all of the Web servers should function.

    If you are not upgrading the Model Manager Data Unselect the Model Manager Data check box in the vCAC Server section.
    To preserve customized workflows as the latest version in your Model Manager Data

    If you are upgrading the Model Manager Data, select the Preserve my latest workflow versions check box in the Extensibility Workflows section.

    The check box is selected by default. Customized workflows are always preserved. The checkbox determines version order only. If you used vRealize Automation Designer to customize workflows in the Model Manager, select this option to maintain the most recent version of each customized workflow before upgrade as the most recent version after upgrade.

    If you do not select this option, the version of each workflow provided with vRealize Automation Designer becomes the most recent after upgrade, and the most recent version before upgrade becomes the second most recent.

    For information about vRealize Automation Designer, see Life Cycle Extensibility.

    If you are upgrading a Distributed Execution Manager or a proxy agent

    Enter the credentials for the administrator account in the Service Account section.

    All of the services that you upgrade run under this account.

    To specify your Microsoft SQL Server database If you are upgrading the Model Manager Data, enter the names of the database server and database instance in the Server text box in the Microsoft SQL Server Database Installation Information section. Enter a fully qualified domain name (FQDN) for the database server name in the Database name text box.

    If the database instance is on a non-default SQL port, include the port number in the server instance specification. The Microsoft SQL default port number is 1433.

    When upgrading the manager nodes, the MSSQL SSL option is selected by default. If your database does not use SSL, uncheck Use SSL for database connection.

  10. Click Next.
  11. Confirm that all services to upgrade appear on the Ready to Upgrade page, and click Upgrade.
    The Upgrading page and a progress indicator appear. When the upgrade process finishes, the Next button is enabled.
  12. Click Next.
  13. Click Finish.
  14. Verify that all services restarted.
  15. Repeat these steps for each IaaS server in your deployment in the recommended order.
  16. After all components are upgraded, log in to the management console for the appliance and verify that all services, including IaaS, are now registered.


All of the selected components are upgraded to the new release.

What to do next

If your deployment uses a load balancer, upgrade each load balancer node to use vRealize Automation health checks, and re-enable load balancer traffic for any unconnected nodes. If your previous deployment used a load balanced embedded PostgreSQL database, disable all nodes in the PostgreSQL pool because they are not needed. Delete the pool at a convenient time.