7.2
Table Of Contents
- Upgrading vRealize Automation 7.0 or 7.0.1 to 7.2
- Contents
- Updated Information
- vRealize Automation 7.0 or 7.0.1 Upgrade Prerequisites and Process
- Preparing to Upgrade vRealize Automation 7.0 or 7.0.1
- Updating the vRealize Automation 7.0 or 7.0.1 Appliance
- Upgrading the IaaS Server Components After Upgrading vRealize Automation 7.0 or 7.0.1 to 7.2
- Updating vRealize Orchestrator After Upgrading from vRealize Automation 7.0 or 7.0.1 to 7.2
- Add Users or Groups to an Active Directory Connection
- Enable Your Load Balancers
- Post-Upgrade Tasks for Upgrading vRealize Automation 7.0 or 7.0.1
- Troubleshooting the vRealize Automation 7.0 or 7.0.1 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 But Are Not Available to Request
- IaaS Windows Services Fail to Stop
- PostgreSQL External Database Merge Is Unsuccessful
- Delete Orphaned Nodes on vRealize Automation
- Join Cluster Command Appears to Fail After Upgrading a High-Availability Environment
- Upgrade Is Unsuccessful if Root Partition Does Not Provide Sufficient Free Space
- Management Agent Upgrade is Unsuccessful
- Upgrade Fails to Upgrade the Management Agent or Certificate Not Installed on a IaaS Node
- Backup Copies of .xml Files Cause the System to Time Out
- Exclude Management Agents from Upgrade
- Unable to Create New Directory in vRealize Automation
- Index
3 Edit the Management Agent conguration le at C:\Program Files (x86)\VMware\vCAC\Management
Agent\VMware.IaaS.Management.Agent.exe.config to replace the existing alternativeEndpointaddress
value with the URL of the primary virtual appliance endpoint.
The location of the installation folder might be dierent from the default location.
Example of alternativeEndpointaddress in VMware.IaaS.Management.Agent.exe.config.
<alternativeEndpoint address="https://FQDN:5480/" thumbprint="thumbprint number" />
4 Restart the Management Agent Windows service and check the All.log le to verify that is working.
5 Run the upgrade procedure on the primary vRealize Automation appliance.
Upgrade Fails to Upgrade the Management Agent or Certificate Not
Installed on a IaaS Node
Management Agent or Certicate is not upgraded on a IaaS node and error message appears in the
management console.
Problem
If the upgrade fails to upgrade on a IaaS node and error messages about the Management Agent or
Certicate appear in the management console, use these suggestions to troubleshoot the problem.
n
Check the Management Agent log on the aected node for errors.
n
Check if the Management Agent was auto-upgraded by examining the version number in Programs
and Features.
n
If the Management Agent is upgraded, ensure that its service is running.
n
If the Management Agent is upgraded and running, restart upgrade on the virtual appliance.
n
If the Management Agent is not upgraded, perform a manual upgrade of the Management Agent. Open
a browser and navigate to the VMware vRealize Automation IaaS Installation page on the vRealize
Automation appliance at hps://virtual_appliance_host:5480/installer. Download and run the
Management Agent Installer. Restart upgrade on the virtual appliance.
n
If you plan to upgrade the IaaS components with the automatic upgrade shell script, make sure to
download the Management Agent installer shipped as a separate package on the vRealize Automation
7.2 download page. For information, see Knowledge Base Article 2147926.
Do not aempt to use Management Agent installer that is included in the vRealize Automation virtual
appliance.
Backup Copies of .xml Files Cause the System to Time Out
vRealize Automation registers any le with an .xml extension in
the \VMware\vCAC\Server\ExternalWorkows\xmldb\ directory. If this directory contains backup les
with an .xml extension, the system runs duplicate workows that cause the system to time out.
Solution
Workaround: When you back up les in this directory, move the backups to another directory, or change the
extension of the backup le name to something other than .xml.
Upgrading vRealize Automation 7.0 or 7.0.1 to 7.2
50 VMware, Inc.