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
Upgrading vRealize Automation
6.2.5 to 7.4 1
You can perform an in-place upgrade of your current vRealize Automation 6.2.5 environment to 7.4. You
use upgrade procedures specific to this version to upgrade your environment.
An in-place upgrade is a three-stage process. You update the components in your current environment in
this order.
1 vRealize Automation appliance
2 IaaS web server
3 vRealize Orchestrator
You must upgrade all product components to the same version.
The vRealize Production Test Upgrade Assist Tool analyzes your vRealize Automation 6.2.x environment
for any feature configuration that can cause upgrade issues and checks that your environment is ready
for upgrade. To download this tool and related documentation, go to the VMware vRealize Production
Test Tool download product page.
Property dictionary controls that are not supported after upgrade can be restored using
vRealize Orchestrator and property dictionary relationships.
If you have workflows in your source environment that contain deprecated code, see the
vRealize Automation Extensibility Migration Guide for information about the code changes required for
conversion to event broker subscriptions.
If you have workflows in your source environment that contain deprecated code, see the vRealize
Automation Extensibility Migration Guide for information about the code changes required for conversion
to event broker subscriptions.
Beginning with vRealize Automation 7.2, JFrog Artifactory Pro is no longer bundled with the vRealize
Automation appliance. If you upgrade from an earlier version of vRealize Automation, the upgrade
process removes JFrog Artifactory Pro. For more information, see Knowledge Base 2147237.
Note If you have customized your current vRealize Automation 6.2.5 environment, contact your CCE
support staff for additional upgrade information.
VMware, Inc.
6