7.4
Table Of Contents
- Migrating vRealize Automation to 7.4
- Contents
- Migrating vRealize Automation
- vRealize Automation Environment User Interfaces
- Migration Prerequisites
- Pre-Migration Tasks
- Review Changes Introduced by Migration from vRealize Automation 6.2.x to 7.x
- Apply Software Agent Patch
- Change DoDeletes Setting on the vSphere Agent to False
- Check Templates in Your vRealize Automation 6.x Source Environment
- Prepare vRealize Automation Virtual Machines for Migration
- Gather Information Required for Migration
- Obtain the Encryption Key
- List Tenant and IaaS Administrators
- Add Each Tenant from the Source Environment
- Create an Administrator for Each Added Tenant
- Synchronize Users and Groups Before Migration to a Minimal Environment
- Synchronize Users and Groups Before Migration to a High-Availability Environment
- Run Data Collection in Source
- Manually Clone the Source Microsoft SQL Database
- Snapshot the Target Environment
- Migration Procedures
- Post-Migration Tasks
- Add Tenant and IaaS Administrators
- Run Test Connection and Verify Migrated Endpoints
- Run Data Collection on Target
- Reconfigure Load Balancers After Migration
- Migrate an External Orchestrator Server
- Reconfigure the vRealize Automation Endpoint
- Reconfigure the vRealize Automation Infrastructure Endpoint
- Install vRealize Orchestrator Customization
- Reconfigure Embedded vRealize Orchestrator Endpoint
- Reconfigure the Azure Endpoint
- Migrate Automation Application Services
- Delete Original Target vRealize Automation IaaS Microsoft SQL Database
- Update Data Center Location Menu Contents After Migration
- Upgrading Software Agents to TLS 1.2
- Validate the Target vRealize Automation 7.4 Environment
- Troubleshooting Migration
- PostgreSQL Version Causes Error
- Some Virtual Machines Do Not Have a Deployment Created during Migration
- Migration Log Locations
- Catalog Items Appear in the Service Catalog After Migration But Are Not Available to Request
- Data Collection Radio buttons Disabled in vRealize Automation
- Troubleshooting the Software Agent Upgrade
Perform the following procedure for each tenant in the target vRealize Automation console.
Note If you migrate from a vRealize Automation 7.x environment, you do not need to perform this
procedure.
Prerequisites
n
Successful migration to the latest version of vRealize Automation.
n
Log in to the target vRealize Automation console as Administrator with the password you entered
when you deployed the target vRealize Automation appliance.
Procedure
1 Select Administration > Tenants.
2 Click a tenant name.
3 Click Administrators.
4 Make a list of each tenant administrator name and user name.
5 Point to each administrator and click the delete icon (Delete) until you delete all administrators.
6 Click Finish.
7 On the Tenants page, click the tenant name again.
8 Click Administrators.
9 Enter the name of each user that you deleted in the appropriate search box and press Enter.
10 Click the name of the appropriate user from the search returns to add the user back as an
administrator.
When you finish, the list of tenant administrators looks the same as the list of administrators you
deleted.
11 Click Finish.
Run Test Connection and Verify Migrated Endpoints
Migrating to vRealize Automation 7.4 makes changes to endpoints in the target environment.
After you migrate to vRealize Automation 7.4, you must use the Test Connection action for all applicable
endpoints. You might also need to make adjustments to some migrated endpoints. For more information,
see Considerations When Working With Upgraded or Migrated Endpoints in Configuring vRealize
Automation.
The default security setting for upgraded or migrated endpoints is not to accept untrusted certificates.
Migrating vRealize Automation to 7.4
VMware, Inc. 37