6.2

Table 6‑1. Post-migration Tasks (Continued)
Task Related Information
Open the migrated entitlements forms and apply any recreated
approval policies.
See information about entitling users to services in Tenant
Administration.
Verify the Clone From field on each clone blueprint. Open each migrated clone blueprint and verify that the Clone
From field is populated. If the Clone From field is not populated,
add the correct clone template name to the blueprint.
Recreate email notification capabilities. See Recreating Email Notifications.
Upgrade endpoints as required. For a list of supported endpoints, see the vRealize Automation
Support Matrix in vRealize Automation documentation.
Note If you upgrade endpoints after migration is finished, you
may need to adjust endpoint settings. For example, if you
upgrade vRealize Orchestrator after migration, you may need to
change the vCloud Automation Center 5.2-based
vRealize Orchestrator endpoint priority, for example to 2, and
configure the new version of vRealize Orchestrator with the new
user names.
Update necessary customized configuration files if you have not
already done so.
See Updating Customized Configuration Files.
Recreate or reapply deployment customizations. If you received customization packages from VMware or from a
third party, and you still want to use the customizations after
migration, check with the contact who authored the
customizations and request updated vRealize Automation
customizations.
Recreate necessary branding graphic files and catalog icons,
such as blueprint icons.
The screen resolution differs between the source and target
versions. The 5.2 images are pixilated in the target system. The
recommended image resolution is 100 x 100. The file type
should be PNG. See information about configuring branding for
the vRealize Automation console in System Administration.
Add a transport zone value to the migrated
vCloud Networking and Security reservations that are
associated to multi-machine blueprints.
See information about specifying network information for a multi-
machine blueprint in IaaS Integration for Multi-Machine Services.
If you used an app_offline.html file before migration, keep
the app_offline.html file and update its display content.
See Disabling Access to the Source System.
Turn on Storage DRS in all datastore clusters that use Storage
DRS.
See information about enabling and disabling Storage DRS in
the vSphere Client in ESXi and vCenter Server 5.5 or later
documentation.
Perform sample tests to confirm business groups memberships.
Perform sample tests to provision blueprints in a sample of
groups and reservations.
Perform sample tests to run endpoint and compute resource
data collection.
Delete snapshots when you no longer need them. See information about deleting snapshots in ESXi and vCenter
Server 5.5 or later documentation.
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 50