7.1
Table Of Contents
- Upgrading from vRealize Automation 6.2 to 7.1
- Contents
- Upgrading to vRealize Automation 7.1
- Updated Information
- Upgrading vRealize Automation
- Checklist for Upgrading vRealize Automation Components
- Considerations About Upgrading to This vRealize Automation Version
- Upgrade and Identity Appliance Specifications
- Upgrade and Licensing
- Understanding How Roles Are Upgraded
- Understanding How Blueprints Are Upgraded
- Upgrade and vApp Blueprints, vCloud Endpoints, and vCloud Reservations
- Understanding How Multi-Machine Blueprints Are Upgraded
- Upgrade and Physical Endpoints, Reservations, and Blueprints
- Upgrade and Network Profile Settings
- Upgrade and Entitled Actions
- Upgrade and Custom Properties
- Upgrade and Application Services
- Upgrade and Advanced Service Design
- Upgrade and Blueprint Cost Information
- Prerequisites for Upgrading vRealize Automation
- Preparing to Upgrade vRealize Automation
- Updating the vRealize Automation Appliance
- Upgrading the IaaS Server Components
- Upgrade Stand-Alone External vRealize Orchestrator for Use With vRealize Automation
- Upgrade External vRealize Orchestrator Appliance Clusters
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for vRealize Automation
- Troubleshooting the Upgrade
- Migration of Identity Store Fails Because the Active Directory is...
- Migration of Identity Store Fails Because of Incorrect Credentials
- Migration of Identity Store Fails With a Timeout Error Message...
- Installation or Upgrade Fails with a Load Balancer Timeout Error...
- Upgrade Fails for Website Component During IaaS Upgrade
- Incorrect Tab Names Appear Intermittently
- Manager Service Fails to Run Due to SSL Validation Errors...
- Log In Fails After Upgrade
- Catalog Items Appear in the Service Catalog But Are Not...
- User Migration Batch Files Are Ineffective
- PostgreSQL External Database Merge is Unsuccessful
- Join Cluster Command Appears to Fail After Upgrading a High Availability Environment
- Increase Free Space on the Root Partition
- Manual PostgreSQL Database Merge
- Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on a IaaS Node
- Bad PostgreSQL Service State Stops Upgrade and Displays Error Message
- Backup Copies of .xml Files Cause the System to Time Out
- Index
6 Verify that all services are registered except iaas-service.
The artifact-management-service and release-management service do not start without a
vRealize Code Stream license key.
What to do next
“Update the License Key,” on page 24.
Update the License Key
You must upgrade your license key to use the latest version of the vRealize Automation appliance.
Procedure
1 Navigate to the vRealize Automation appliance management console by using its fully qualied
domain name, hps://vra-va-hostname.domain.name:5480/.
2 Select vRA > Licensing.
If the New License Key text box is not available, perform the following steps.
a Log out of the management console.
b Clear your browser cache.
c Log in again to the management console.
d Repeat step 2.
3 Enter your new license key in the New License Key text box.
Endpoints and quotas are agged according to your end-user license agreement (EULA).
What to do next
“Migrate Identity Stores to the VMware Identity Manager,” on page 24
Migrate Identity Stores to the VMware Identity Manager
As part of upgrading to 7.1 from 6.2.x, you migrate identity stores.
Refer to the snapshot of your 6.2.x tenant conguration information as required in the following procedures.
N vRealize Code Stream users must manually reassign vRealize Code Streamroles after identity store
migration.
Procedure
1 Create a Local User Account for Your Tenants on page 25
As part of upgrading identity stores, you must set up a tenant with a local user account and assign
tenant administrator privileges to the local user account.
2 Synchronize Users and Groups for an Active Directory Link on page 25
Connect to your Active Directory link to import your users and groups into vRealize Automation
using the Directories Management functionality.
3 Migrate Multiple Tenant and IaaS Administrators on page 27
If you have multiple vRealize Automation 6.2.x tenants and IaaS administrators, use the Identity
Stores Migration Tool to migrate your tenant administrators to your newly synchronized vsphere.local
tenant. Alternatively, you can add them manually to the vsphere.local tenants.
Upgrading from vRealize Automation 6.2 to 7.1
24 VMware, Inc.