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
3 Save your settings.
Verify That vRealize Orchestrator Service Is Available
After you upgrade to the latest version of vRealize Automation, you must verify the connection between
vRealize Automation and vRealize Orchestrator. Sometimes after upgrade you must restore the
connection.
Prerequisites
Log in to the vRealize Orchestrator configuration interface.
Procedure
1 Click Validate Configuration.
2 If the Authentication section has a green check, go to step 5.
3 If the Authentication section does not have a green check, perform the following steps to restore the
connection to vRealize Orchestrator .
a Click Home.
b Click Configure Authentication Provider.
c In the Admin group text box, select Change, and choose a new Admin group that can be
properly resolved.
The vcoadmins group is available only at the default vsphere.local tenant. If you are using
another tenant for the vRealize Orchestrator, then you must select another group.
d Click Save Changes, and if prompted, restart the vRealize Orchestrator server.
e Click Home.
4 Repeat step 1 to confirm that the Authentication section still has a green check.
5 Click Home, and close the vRealize Orchestrator Control Center.
Reconfigure Embedded vRealize Orchestrator
Infrastructure Endpoint in the Target vRealize Automation
When you migrate from a vRealize Automation 6.2.x environment, you must update the URL of the
infrastructure endpoint that points to the target embedded vRealize Orchestrator server.
Prerequisites
n
Successfully migrate to vRealize Automation 7.4.
n
Log in to the target vRealize Automation console.
a Open the vRealize Automation console using the fully qualified domain name of the target virtual
appliance: https://vra-va-hostname.domain.name/vcac.
Upgrading from vRealize Automation 6.2.5 to 7.4
VMware, Inc. 77