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
Improves the operational efficiency.
Note Consider using the external vRealize Orchestrator in the following cases:
n
Multiple tenants in the vRealize Automation environment
n
Geographically dispersed environment
n
Workload handling
n
Use of specific plug-ins, such as older versions of the Site Recovery Manager plug-in
Control Center Dierences Between External and Embedded
Orchestrator
Some of the menu items that are available in Control Center of an external vRealize Orchestrator are not
included in the default Control Center view of an embedded Orchestrator instance.
In Control Center of the embedded Orchestrator server, a few options are hidden by default.
Menu Item Details
Licensing The embedded Orchestrator is preconfigured to use vRealize Automation as a license provider.
Export/Import Configuration The embedded Orchestrator configuration is included in the exported vRealize Automation
components.
Configure Database The embedded Orchestrator uses the database that is used by vRealize Automation.
Customer Experience
Improvement Program
You can join the Customer Experience Improvement Program (CEIP) from the
vRealize Automation appliance management interface.
See The Customer Experience Improvement Program in Managing vRealize Automation.
Another options that are hidden from the default Control Center view are the Host address text box and
the UNREGISTER button on the Configure Authentication Provider page.
Note To see the full set of Control Center options in vRealize Orchestrator that is built into
vRealize Automation, you must access the advanced Orchestrator Management page at https://vra-va-
hostname.domain.name_or_load_balancer_address:8283/vco-controlcenter/#/?advanced and click the
F5 button on the keyboard to refresh the page.
Migrate an External vRealize Orchestrator on Windows to
vRealize Automation
After you upgrade your vRealize Automation from version 6.x to version 7.4, you can migrate your
existing external Orchestrator 6.x installed on Windows to the Orchestrator server that is built into
vRealize Automation 7.4.
Note If you have a distributed vRealize Automation environment with multiple vRealize Automation
nodes, perform the migration procedure only on the primary vRealize Automation node.
Upgrading from vRealize Automation 6.2.5 to 7.4
VMware, Inc. 57