7.3

5 On the master node, open an SSH session, log in as administrator, and run this command:
rm /etc/vco/app-server/vco-registration-id
6 On the master node, change directories to /etc/vco/app-server/.
7 Open the sso.properties file.
8 If the property name com.vmware.o11n.sso.admin.group.name contains spaces or any other
Bash-related characters that can be accepted as a special character in a Bash command such as a
hyphen (') or a dollar sign ($), complete these steps.
a Copy the line with the com.vmware.o11n.sso.admin.group.name property and enter
AdminGroup for the value.
b Add # to the beginning of the original line with the com.vmware.o11n.sso.admin.group.name
property to comment the line.
c Save and close the sso.properties file.
9 Run this command:
vcac-vami vco-service-reconfigure
10 Open the sso.properties file. If the file has changed, complete these steps.
a Remove the # from the beginning of the original line with the
com.vmware.o11n.sso.admin.group.name property to uncomment the line.
b Remove the copy of the line with the com.vmware.o11n.sso.admin.group.name property.
c Save and close the sso.properties file.
11 Run this command to restart the vco-server service:
service vco-server restart
12 Run this command to restart the vco-configurator service:
service vco-configurator restart
13 In the vRealize Automation appliance management console, click Services and wait until all the
services in the master node are REGISTERED.
14 When all the services are registered, join the vRealize Automation replica nodes to the
vRealize Automation cluster to synchronize the vRealize Orchestrator configuration. For information,
see Reconfigure the Built-In vRealize Orchestrator to Support High Availability.
What to do next
Chapter 6 Upgrading vRealize Orchestrator After Upgrading vRealize Automation.
Upgrading from vRealize Automation 7.1, 7.2 to 7.3 or 7.1, 7.2, 7.3 to 7.3.1
VMware, Inc. 31