You can upgrade your current VMware vRealize ™ Automation environment to the latest version.

Depending on your current vRealize Automation environment, you can upgrade to the latest version by performing an in-place upgrade or a side-by-side upgrade.

An in-place upgrade is a multi-stage process in which you perform procedures in a particular order to update the various components in your current environment. You must upgrade all product components to the same version.

A side-by-side upgrade migrates the data in your current vRealize Automation 6.2.x environment to a target 7.1 environment that mirrors your current environment. Migration does not change your current 6.2.x environment. You cannot use migration to upgrade a vRealize Automation 7.x environment to the latest version. If your current environment is integrated with vCloud Director, vCloud Air or has physical endpoints, you must use migration to upgrade. Migration removes all unsupported endpoints and everything associated with them in the target environment.

New vRealize Automation features introduce several enhancements along with the ability to upgrade or migrate to the new version. For recommendations and guidance before you begin the upgrade process, visit the vRealize Automation Upgrade Assistance Program web page at http://www.vmware.com/products/vrealize-automation/upgrade-center before you begin the upgrade process.

Locate your current vRealize Automation version in the table and use the documents on the right to perform an upgrade of your vRealize Automation environment to the latest version.

Table 1. Supported In-Place Upgrade Paths to 7.2

Your Currently Installed Version

Documentation for Incremental Upgrades

vRealize Automation 7.1

See Upgrading vRealize Automation 7.1 .

vRealize Automation 7.0 or 7.0.1

See Upgrading vRealize Automation 7.0 or 7.0.1.

vRealize Automation 6.2.4 or 6.2.5

See Upgrading vRealize Automation 6.2.4 or 6.2.5 .

vRealize Automation 6.2.0, 6.2.1, 6.2.2, 6.2.3

See Migrating vRealize Automation 6.2.x

This table provides information about upgrading from an earlier vCloud Automation Center 6.x release to vRealize Automation 6.2.5 in preparation for upgrading to the latest version of vRealize Automation. You can find links to the documentation for all versions of vCloud Automation Center and vRealize Automation at https://www.vmware.com/support/pubs/vcac-pubs.html.

Table 2. Supported Upgrade Paths in 6.x

Your Currently Installed Version

Documentation for Incremental Upgrades

vCloud Automation Center 6.0

Perform upgrades in the following order:

  1. Upgrading vCloud Automation Center 6.0 to 6.0.1

  2. Upgrading to vCloud Automation Center 6.1

  3. Upgrading to vRealize Automation 6.2.x

vCloud Automation Center 6.0.1

Perform upgrades in the following order:

  1. Upgrading to vCloud Automation Center 6.1

  2. Upgrading to vRealize Automation 6.2.x

vCloud Automation Center 6.1.x

Upgrading to vRealize Automation 6.2.x

vRealize Automation 6.2.x

Upgrade directly to the latest 6.2.x release as described in Upgrading to vRealize Automation 6.2.x

Note:

Beginning in 6.2.0, vCloud Automation Center is rebranded to vRealize Automation. Only the user interface and service names are changed. Directory names and program names that contain vcac are not affected.

If you are upgrading from a 6.2.x environment, review these items.

  • Upgrading from a 6.2.x environment to 7.x introduces many functional changes. For more information see Considerations About Upgrading to This vRealize Automation Version.

  • If you have customized your 6.2.x deployment, contact your CCE support staff for additional information about upgrade considerations.

  • To avoid a known issue when upgrading from vRealize Automation 6.2.0, perform the following step sequence on every IaaS Web site node before you upgrade. This issue affects 6.2.0 only. Other 6.2.x versions are not affected.

    1. Open Notepad with Administrative rights.

    2. Open the following file:

      C:\Program Files (x86)\VMware\vCAC\Server\Model Manager Web\web.config

    3. Locate the following statement in the file:

      <!-- add key="DisableMessageSignatureCheck" value="false"-->

    4. Uncomment the statement and change the value from false to true.

      <add key="DisableMessageSignatureCheck" value="true" />

    5. Save the file.

      If Notepad prompts you to Save As, you did not open Notepad as Administrator and must go back to step 1.

    6. Open a Command Prompt window with Administrative rights.

    7. Run reset.

    8. Repeat steps 1 - 7 for all Web site nodes.