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
Required
Value Description Credential Format
web_userna
me
User name for the primary Web node. Required only
once.
Domain\User
web_passw
ord
Password for the primary Web node. Required only
once.
Password
dem_userna
me
User name for the DEM worker or DEM orchestrator.
Required for each node where a DEM component is
installed.
Domain\User
dem_passw
ord
Password for the DEM worker or DEM orchestrator.
Required for each node where a DEM component is
installed.
Password
agent_usern
ame
User name for an agent such as a vSphere agent.
Required for each node where an agent component is
installed.
Domain\User
agent_pass
word
Password for an agent such as a vSphere agent.
Required for each node where an agent component is
installed.
Password
vidm_admi
n_password
The VIDM administrator password. Required only
when you upgrade from vRealize Automation 6.2.4 or
6.2.5.
vIDM_password
For security reasons, the upgrade.properties le is removed when you run the upgrade shell script.
The properties in the le are dened using the information for each IaaS component that comes through
the IaaS Management Agents. It is important that all IaaS Management Agents are upgraded and
healthy prior to running the ./generate_properies or ./upgrade shell scripts. If any IaaS Management
Agent has a problem when you run the upgrade shell script, see “Upgrade Fails to Upgrade the
Management Agent or Certicate Not Installed on a IaaS Node,” on page 64. To recreate the
upgrade.properties le, repeat steps 2 and 3.
5 Run the upgrade script.
a At the command prompt, enter ./upgrade.
b Press Enter.
The script displays each IaaS node and all the components installed on it. The script validates each
component before installing the upgrade. If there are incorrect values in the upgrade.properties le, the
script fails.
If the Upgrade Shell Script is unsuccessful, review the upgrade.log le.
You can run the upgrade script again after you x a problem. Before you run the upgrade script again,
recreate the upgrade.properties le, open it, and enter all the required values.
What to do next
Chapter 6, “Add Users or Groups to an Active Directory Connection,” on page 47
Upgrading IaaS Components Using the IaaS MSI Package After
Upgrading vRealize Automation 6.x to 7.2
You can use this alternative method to upgrade IaaS components.
Chapter 4 Upgrading the IaaS Server Components After Upgrading vRealize Automation 6.x to 7.2
VMware, Inc. 37