6.2

This chapter includes the following topics:
n
Restart vRealize Automation IaaS Services
n
Recreating Approval Policies
n
Recreating ISOs and Templates That Contain a Guest Agent
n
Recreating Email Notifications
Restart vRealize Automation IaaS Services
After migration is finished, restart the target vRealize Automation system, including the IaaS services, on
your IaaS Windows Server to prepare for post-migration tasks.
Procedure
1 Power on the Identity Appliance and wait until it is running and its services start.
You can monitor the status of the Identity Appliance services by checking
the /storage/log/vmware/sso/catalina.out file.
2 Power on the vRealize Appliance and wait until all the services except the IaaS service are started
and registered.
3 Log in to the host IaaS Windows machine for the vRealize Automation server as a user with full
administrative access.
4 Select Start > Administrative Tools > Services.
5 Start the services in the recommended order.
In a distributed environment, start manager services, DEMs, and agents on all of the running
vRealize Automation servers.
a VMware vCloud Automation Center Service (manager service)
b VMware DEM-Orchestrator
c VMware DEM-Worker
d VMware vRealize Automation Agents
Recreating Approval Policies
Approval policies are not migrated. You can recreate approval policies in vRealize Automation after you
finish the pre-migration task or the migration task. Recreating approval policies in the target system
before you start the migration task saves time that you would otherwise spend in recreating the approval
policies during post-migration.
Migration creates a single, default policy that is configured to require only the approval of the business
group manager. The migration process adds the approval policy to each catalog item entitlement for each
blueprint that had an approval configured in the source system.
For related information, see Migrating Approval Policies.
Migrating vCloud Automation Center 5.2.3 to vRealize Automation 6.2
VMware, Inc. 51