7.3

Table Of Contents
After upgrade or migration, the new Proxy endpoint name is Proxy_YYYYY where YYYYY is a hash
of the proxy's URL, port, and credentials. If you used the same proxy settings (for example the same
URL, port, and credentials) for a different endpoint (for example, a vCloud Air or Amazon endpoint),
after upgrade or migration there is only one Proxy endpoint and an association between the
vCloud Air and Amazon endpoint and the new Proxy endpoint. A proxy endpoint can be associated to
more than one Amazon, vCloud Air or vCloud Director endpoint.
n
When you upgrade or migrate vSphere endpoints that contain NSX manager settings, each vSphere
endpoint is associated to a new NSX endpoint that contains its NSX manager settings.
After upgrade or migration, the NSX endpoint name is NSX_XXXXX where XXXXX is the name of the
parent vSphere endpoint in the pre-vRealize Automation 7.3 release.
n
When vRealize Automation upgrade or migration is finished, an infrastructure administrator can
change the new NSX and Proxy endpoint names.
n
The default security setting for upgraded or migrated endpoints is not to accept untrusted certificates.
n
After upgrading or migrating from an earlier vRealize Automation installation, if you were using
untrusted certificates you must perform the following steps for all vSphere and NSX endpoints to
enable certificate validation. Otherwise, the endpoint operations fail with certificate errors. For more
information, see VMware Knowledge Base articles Endpoint communication is broken after upgrade
to vRA 7.3 (2150230) at http://kb.vmware.com/kb/2150230 and How to download and install vCenter
Server root certificates to avoid Web Browser certificate warnings (2108294) at
http://kb.vmware.com/kb/2108294.
a After upgrade or migration, log in to the vRealize Automation vSphere agent machine and restart
your vSphere agents by using the Services tab.
Migration might not restart all agents, so manually restart them if needed.
b Wait for at least one ping report to finish. It takes a minute or two for a ping report to finish.
c When the vSphere agents have started data collection, log in to vRealize Automation as an IaaS
administrator.
d Click Infrastructure > Endpoints > Endpoints.
e Edit a vSphere endpoint and click Test Connection.
f If a certificate prompt appears, click OK to accept the certificate.
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.
g Click OK to apply the certificate acceptance and save the endpoint.
h Repeat this procedure for each vSphere endpoint.
i Repeat this procedure for each NSX endpoint.
Configuring vRealize Automation
VMware, Inc. 218