7.1

c Select Update > .
d Choose your download method and click Save .
e Click Status.
f Click Check Updates.
g Click Install Updates.
h Accept the VMware End User License Agreement.
i When the update nishes, restart the vRealize Orchestrator appliance.
6 If your clustered vRealize Orchestrator was previously congured with vRealize Automation
authentication type, unregister and re-register the node.
a On the primary node, log in as root to the vRealize Orchestrator Control Center at
hps://your_orchestrator_server_IP_or_DNS_name:8283/vco-controlcenter/.
b Click the Congure Authentication Provider icon.
c Click Unregister.
d Click Connect.
e Enter your user name and password credentials.
f Select the  licenses checkbox and select the vco administrators group.
g Click Save Changes.
h Navigate to Orchestrator Cluster Management at hps://vco-controlcenter:
8283/vcocontrolcenter/#/control-app/ha and append ?remove-nodes to the URL, for example,
hps://vco-controlcenter:8283/vcocontrolcenter/#/control-app/ha?remove-nodes.
i For each vRealize Orchestrator node in the old cluster, select the Remove checkbox in the table and
click Remove and Refresh.
j Restart the main vRealize Orchestrator server service and wait for the service to fully initialize.
7 Verify that the vco service appears as registered in the vRealize Orchestrator Appliance management
console.
8 On the vRealize Orchestrator Control Center, click the Validate Conguration icon and verify that the
conguration is valid.
9 On the vRealize Orchestrator Control Center, upgrade the vRealize Automation default plugins, which
include the NSX plugin.
10 Log in as root to the vRealize Orchestrator Control Center on the primary vRealize Orchestrator node
at hps://your_orchestrator_server_IP_or_DNS_name:8283/vcocontrolcenter.
11 Click the Manage Plugins icon.
12 Select Browse > plug-in name > Install.
13 Deploy a new vRealize Orchestrator appliance for a new secondary vRealize Orchestrator node in this
cluster.
14 Set up the network conguration of the new secondary vRealize Orchestrator node to match the
secondary vRealize Orchestrator node in the old cluster.
Upgrading from vRealize Automation 6.2 to 7.1
38 VMware, Inc.