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
Procedure
1 Create a Local User Account for Your Tenants on page 29
As part of upgrading identity stores, you must set up a tenant with a local user account and assign
tenant administrator privileges to the local user account.
2 Synchronize Users and Groups for an Active Directory Link on page 30
To import your users and groups into vRealize Automation using the Directories Management
capability, you must connect to your Active Directory link.
3 Migrate Multiple Tenant and IaaS Administrators on page 31
If you have multiple vRealize Automation 6.2.x tenants and IaaS administrators, use the Identity
Stores Migration Tool to migrate your tenant administrators to your newly synchronized vsphere.local
tenant. Alternatively, you can add them manually to the respective tenants.
Create a Local User Account for Your Tenants
As part of upgrading identity stores, you must set up a tenant with a local user account and assign tenant
administrator privileges to the local user account.
Prerequisites
Verify that you have set a new VMware Identity Manager password. See “Update Your Single Sign-On
Password for VMware Identity Manager,” on page 27.
Procedure
1 Log in to the vRealize Automation console with the default system administrator username
administrator and password.
The console location is https://vra-appliance/vcac/.
2 Click your tenant.
For example, for the default tenant, click vsphere.local
3 Select the Local Users tab.
4 Click New.
5 Create a local user account to assign to the tenant administrator role.
The local user name should be unique to the vsphere.local active directory.
6 Click OK.
7 Click the Administrators tab.
8 Enter the local user name in the Tenant administrators search box and press Enter.
9 Click Finish.
10 Repeat these steps for each of your tenants.
11 Log out of the console.
What to do next
“Synchronize Users and Groups for an Active Directory Link,” on page 30
Chapter 3 Updating the vRealize Automation 6.2.4 or 6.2.5 Appliance
VMware, Inc. 29