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. To determine the best upgrade method for your environment, use the vRealize Production Test Tool. For more information, see the vRealize Production Test Upgrade Assessment Guide.

An in-place upgrade is a multi-step process. 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. You can only perform an in-place upgrade for these paths.

  • vRealize Automation 6.2.5 to 7.3

  • vRealize Automation 7.1 to 7.3

  • vRealize Automation 7.2 to 7.3

A side-by-side upgrade migrates the data in your current vRealize Automation environment to a target environment deployed with the latest version of vRealize Automation. You can perform a side-by-side upgrade for these paths.

  • vRealize Automation 6.2.0 through 6.2.5 to 7.3

  • vRealize Automation 7.0 and 7.0.1 to 7.3

  • vRealize Automation 7.1 and 7.2 to 7.3

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

Table 1. Supported Upgrade Paths to vRealize Automation 7.3

Your Currently Installed Version

Documentation for Incremental Upgrades

vRealize Automation 7.1 or 7.2

See Upgrading vRealize Automation 7.1 or 7.2 to 7.3 or Migrating vRealize Automation to 7.3.

vRealize Automation 7.0 or 7.0.1

See Migrating vRealize Automation to 7.3 .

vRealize Automation 6.2.5

See Upgrading vRealize Automation 6.2.5 to 7.3 or Migrating vRealize Automation to 7.3.

vRealize Automation 6.2.0, 6.2.1, 6.2.2, 6.2.3, 6.2.4

See Migrating vRealize Automation to 7.3

This table provides information about upgrading from an earlier vCloud Automation Center 6.x release. You must upgrade to vRealize Automation 6.2.5 before you upgrade 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 to vRealize Automation 6.2.5

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 6.2.5 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.5 environment, review these items.

  • Upgrading from a 6.2.5 environment to the latest version of vRealize Automation introduces many functional changes. For more information, see Considerations About Upgrading to This vRealize Automation Version.

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

To avoid a known problem when upgrading from vRealize Automation 6.2.0, perform the following steps on each IaaS Website node before you upgrade. This problem affects 6.2.0 only. Other 6.2.x versions are not affected.

  1. Open Notepad with Administrative rights. In Start, right-click the Notepad icon and select Run as administrator.

  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 with Administrative rights. In Start, right-click the Command Prompt icon and select Run as administrator.

  7. Run reset.

  8. Repeat steps 1–7 for all website nodes.