7.2

Procedure
1 If you are using a load balancer, prepare your environment.
a Verify the IaaS Website node that contains the Model Manager data is enabled for load balancer
trac.
You can identify this node by the presence of the vCAC Folder\Server\ConfigTool folder.
b Disable all other IaaS Websites and non-primary Manager Services for load balancer trac.
2 Right-click the [e-mail] setup le 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 specied when you deployed the
appliance.
6 Select Accept .
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 Congure the upgrade seings.
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 le 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  versions check box in the Extensibility Workows section.
The check box is selected by default. Customized workows are always
preserved. The checkbox determines version order only. If you used
vRealize Automation Designer to customize workows in the Model
Manager, select this option to maintain the most recent version of each
customized workow before upgrade as the most recent version after
upgrade.
If you do not select this option, the version of each workow 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.
Upgrading from vRealize Automation 7.1 to 7.2
24 VMware, Inc.