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
9 Select the groups and users to synchronize.
a Click the New icon.
b Enter the user domain and click Find Groups.
For example, enter dc=vcac,dc=local.
c To select the groups to synchronize, click Select and click Next.
d On the Select Users page, select the users to synchronize and click Next.
10 Review the users and groups are syncing to the directory, and click Sync Directory.
The directory synchronization takes some time and runs in the background.
11 Select Administration > Directories Management > Identity Providers, and click your new identity
provider.
For example, WorkspaceIDP__1.
12 Scroll to the bottom of the page, and update the value for the IdP Hostname property to point to the
FQDN for the vRealize Automation load balancer.
13 Click Save.
14 Repeat steps 11–13 for each tenant and identity provider.
15 After you upgrade all vRealize Automation nodes, log in to each tenant and select Administration >
Directories Management > Identity Providers.
Each identity provider has all vRealize Automation connectors added to it.
For example, if your deployment has two vRealize Automation appliances, the identity provider has
two associated connectors.
Migrate Custom Groups to the Target VMware Identity Manager
You must migrate all custom groups from the source environment to the VMware Identity Manager (vIDM)
in the target deployment.
Complete this procedure to migrate custom groups.
Prerequisites
n
Create a Local User Account for Your Tenants.
n
Ensure that the horizon-workspace service is running on the vRealize Automation virtual appliance.
Procedure
1 Start an SSH session on the vRealize Automation virtual appliance.
2 At the command prompt, log in as root with the password you created when you installed the
vRealize Automation virtual appliance.
Upgrading from vRealize Automation 6.2.5 to 7.4
VMware, Inc. 40