7.4
Table Of Contents
- Upgrading from vRealize Automation 6.2.5 to 7.4
- Contents
- Upgrading vRealize Automation 6.2.5 to 7.4
- Prerequisites for Upgrading vRealize Automation
- 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 Price Information
- Upgrade and Catalog Items
- Checklist for Upgrading vRealize Automation
- vRealize Automation Environment User Interfaces
- Upgrading VMware Products Integrated with vRealize Automation
- Preparing to Upgrade vRealize Automation
- Updating the vRealize Automation Appliance
- Upgrading the IaaS Server Components After Upgrading vRealize Automation
- Upgrading vRealize Orchestrator After Upgrading vRealize Automation
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for Upgrading vRealize Automation
- Port Configuration for High-Availability Deployments
- Reconfigure Built-In vRealize Orchestrator for High Availability
- Enabling the Connect to Remote Console Action for Consumers
- Restore External Workflow Timeout Files
- Verify That vRealize Orchestrator Service Is Available
- Reconfigure Embedded vRealize Orchestrator Endpoint
- Restore Changes to Logging in the app.config File
- Enable Automatic Manager Service Failover After Upgrade
- Run Test Connection and Verify Upgraded Endpoints
- Troubleshooting the vRealize Automation Upgrade
- Installation or Upgrade Fails with a Load Balancer Timeout Error
- Upgrade Fails for IaaS Website Component
- Manager Service Fails to Run Due to SSL Validation Errors During Runtime
- Log In Fails After Upgrade
- Catalog Items Appear in the Service Catalog After Upgrade But Are Not Available to Request
- PostgreSQL External Database Merge Is Unsuccessful
- Join Cluster Command Appears to Fail After Upgrading a High-Availability Environment
- Upgrade Is Unsuccessful if Root Partition Does Not Provide Sufficient Free Space
- Backup Copies of .xml Files Cause the System to Time Out
- Delete Orphaned Nodes on vRealize Automation
- Unable to Create New Directory in vRealize Automation
- Some Virtual Machines Do Not Have a Deployment Created During Upgrade
- Certificate Not Trusted Error
- Installing or Upgrading to vRealize Automation Fails
- Update Fails to Upgrade the Management Agent
- Management Agent Upgrade is Unsuccessful
- vRealize Automation Update Fails Because of Default Timeout Settings
- Upgrading IaaS in a High Availability Environment Fails
- Work Around Upgrade Problems
Procedure
1 Go to the management console for your virtual appliance by using its fully qualified domain name,
https://va-hostname.domain.name:5480.
2 Log in with the user name root and the password you entered when the appliance was deployed.
3 Select vRA Settings > Licensing.
If the Licensing tab is not available, perform the following steps and repeat the procedure.
a Log out of the management console.
b Clear your browser cache.
4 Enter your new license key in the New License Key text box.
Endpoints and quotas are flagged according to your end-user license agreement (EULA).
5 Click Submit Key.
What to do next
Migrate Identity Stores to VMware Identity Manager.
Migrate Identity Stores to VMware Identity Manager
When you upgrade from vRealize Automation 6.2.5 to the current version, you must migrate the identity
stores.
As required in the following procedures, refer to the snapshot of your 6.2.5 tenant configuration
information.
Note After you migrate the identity stores, users of vRealize Code Stream must manually reassign
vRealize Code Stream roles.
Procedure
1 Create a Local User Account for Your Tenants
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
To import your users and groups into vRealize Automation using the Directories Management
capability, you must connect to your Active Directory link.
3 Migrate Custom Groups to the Target VMware Identity Manager
You must migrate all custom groups from the source environment to the VMware Identity Manager
(vIDM) in the target deployment.
4 Migrate Multiple Tenant and IaaS Administrators
For each vRealize Automation tenant with Tenant or IaaS administrators, you must delete and
restore each administrator manually.
Upgrading from vRealize Automation 6.2.5 to 7.4
VMware, Inc. 37