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
n
Any operational price, one time price, and price on custom properties of provisioned virtual
machines
n
Deployments, which include the price of virtual machines within the deployments
n
Role-based showback reports in vRealize Business for Cloud
n
Fully leverage new features in vRealize Business for Cloud
Before you upgrade, you can export your existing expense reports from your source vRealize Automation
instance for reference. After you finish your upgrade, you can install and configure
vRealize Business for Cloud to handle pricing.
Note vRealize Automation 7.4 is compatible only with vRealize Business for Cloud 7.4 and later.
Upgrade and Catalog Items
After you upgrade from vRealize Automation 6.2.x to the latest version, some catalog items appear in the
service catalog but are not available to request.
After you migrate to the latest version of vRealize Automation, catalog items that use these property
definitions appear in the service catalog but are not available to request.
n
Control types: Check box or link.
n
Attributes: Relationship, regular expressions, or property layouts.
In vRealize Automation 7.x, the property definitions no longer use these elements. You must recreate the
property definition or configure the property definition to use a vRealize Orchestrator script action rather
than the embedded control types or attributes. For more information, see Catalog Items Appear in the
Service Catalog After Upgrade But Are Not Available to Request.
Checklist for Upgrading vRealize Automation
When you upgrade vRealize Automation from 6.2.5 to 7.4, you update all vRealize Automation
components in a specific order.
Use the checklists to track your work as you complete the upgrade. Finish the tasks in the order they are
given.
Note You must upgrade components in the prescribed order and upgrade all components. Using a
different order can result in an unexpected behavior after the upgrade or failure of the upgrade to
complete.
The order of upgrade varies depending on whether you are upgrading a minimal environment or a
distributed environment with multiple vRealize Automation appliances.
Upgrading from vRealize Automation 6.2.5 to 7.4
VMware, Inc. 15