7.2
Table Of Contents
- Upgrading from vRealize Automation 6.2.4 or 6.2.5 to 7.2
- Contents
- Updated Information
- vRealize Automation 6.2.4 or 6.2.5 Prerequisites, Considerations, and Process
- Prerequisites for Upgrading from vRealize Automation 6.2.4 or 6.2.5
- 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
- Checklist for Upgrading vRealize Automation 6.2.4 or 6.2.5
- Preparing to Upgrade vRealize Automation 6.2.4 or 6.2.5
- Updating the vRealize Automation 6.2.4 or 6.2.5 Appliance
- Upgrading the IaaS Server Components After Upgrading vRealize Automation 6.x to 7.2
- Updating vRealize Orchestrator After Upgrading from vRealize Automation 6.x to 7.2
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for Upgrading vRealize Automation 6.2.4 or 6.2.5
- Port Configuration for High-Availability Deployments
- Enabling the Connect to Remote Console Action for Consumers
- Restore External Workflow Timeout Files
- Verify That vRealize Orchestrator Service Is Available
- Restore Embedded vRealize Orchestrator Endpoint
- Restore Changes to Logging in the app.config File
- Troubleshooting the vRealize Automation 6.2.4 or 6.2.5 Upgrade
- Migration of Identity Store Fails Because the Active Directory is not Synchronized
- 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 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 But Are Not Available to Request
- User Migration Batch Files Are Ineffective
- 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
- Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on a IaaS Node
- Unable to Create New Directory in vRealize Automation
- Index
Updating vRealize Orchestrator After
Upgrading from vRealize Automation
6.x to 7.2 5
You must update your VMware vRealize ™ Orchestrator ™ instance when you upgrade from
VMware vRealize ™ Automation 6.x to vRealize Automation 7.2.
With the release of vRealize Orchestrator 7.2, you have two options for updating vRealize Orchestrator
when you upgrade to vRealize Automation 7.2.
n
You can migrate your existing external vRealize Orchestrator server to the embedded
vRealize Orchestrator included in vRealize Automation 7.2.
n
You can upgrade your existing standalone or clustered vRealize Orchestrator server to work with
vRealize Automation 7.2.
This chapter includes the following topics:
n
“Migrating an External vRealize Orchestrator Server to vRealize Automation 7.2,” on page 43
n
“Upgrade Stand-Alone vRealize Orchestrator After Upgrading vRealize Automation 6.x to 7.2,” on
page 43
n
“Upgrade External vRealize Orchestrator Appliance Cluster After Upgrading vRealize Automation 6.x
to 7.2,” on page 44
Migrating an External vRealize Orchestrator Server to vRealize
Automation 7.2
You can migrate your existing external VMware vRealize ™ Orchestrator ™ server to a instance embedded
in VMware vRealize ™ Automation 7.2.
For information about migrating your existing external vRealize Orchestrator server, see the
vRealize Orchestrator documentation topic Migrating an External Orchestrator Server to vRealize
Automation 7.2.
Upgrade Stand-Alone vRealize Orchestrator After Upgrading
vRealize Automation 6.x to 7.2
If you maintain a stand-alone, external instance of vRealize Orchestrator for use with vRealize Automation,
you must upgrade vRealize Orchestrator when you upgrade vRealize Automation.
Embedded instances of vRealize Orchestrator are upgraded as part of the vRealize Automation appliance
upgrade. No additional action is required.
Prerequisites
n
Install the update on the primary vRealize Automation appliance.
VMware, Inc.
43