7.3

If a certificate prompt does not appear, the certificate might currently be correctly stored in a trusted
root authority of the Windows machine hosting service for the endpoint, for example as a proxy agent
machine or DEM machine.
7 Click OK to apply the certificate acceptance and save the endpoint.
8 Repeat this procedure for each vSphere endpoint.
9 Repeat this procedure for each NSX endpoint.
If the Test Connection action is successful but some data collection or provisioning operations fail, you
can install the same certificate on all the agent machines that serve the endpoint and on all DEM
machines. Alternatively, you can uninstall the certificate from existing machines and repeat the above
procedure for the failing endpoint.
Run NSX Network and Security Inventory Data Collection
in Your Target vRealize Automation 7.3 Environment
After you migrate, you must run NSX Network and Security Inventory data collection in the target
VMware vRealize ™ Automation 7.3 environment.
This data collection is necessary for the Load Balancer Reconfigure action to work in
vRealize Automation 7.3 for 7.1 and 7.2 deployments.
Note You do not need to perform this data collection if you migrated from vRealize Automation 6.2.x to
7.3.
Prerequisites
n
Run NSX Network and Security Inventory Data Collection in the Source vRealize Automation
Environment .
n
Successfully migrate to vRealize Automation 7.3.
Procedure
u
Run NSX Network and Security Inventory data collection in your target vRealize Automation
environment before you migrate to vRealize Automation 7.3. See Start Endpoint Data Collection
Manually in Managing vRealize Automation.
Reconfigure Load Balancers After Migration to a High-
Availability Environment
When you migrate to a high-availability environment, you must reconfigure each load balancer after you
finish migration.
Prerequisites
Migrate vRealize Automation Source Data to a vRealize Automation 7.3 High-Availability Environment.
Migrating vRealize Automation to 7.3 or 7.3.1
VMware, Inc. 35