Update Manager is quite simple to install and to upgrade. And with 6.0u2 it is accessible within the vSphere web interface. The only requirement is that you have a Windows server to install it on.
Enable shell.
Command> shell.set --enabled True Command> shell
Find SSO domain site name of vCSA.
vcenter:~ # /usr/lib/vmware-vmafd/bin/vmafd-cli get-site-name --server-name localhost Default-First-Site
Verify services are running. You can verify a single service, multiple services, or all services.
vcenter:~ # service-control --status vmware-cis-license vmware-sts-idmd vcenter:~ # service-control --status --all
Connect vCSA to external PSC
Command> cmsso-util reconfigure --repoint-psc psc.company.com --username administrator --domain-name vsphere.local --passwd Password1!
Re-point vCSA to different PSC:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2113917
If you are linking multiple vCSAs and didn't configure one of them, or the first one, with FQDN; you may need to SSH into the vCSAs and manually edit the hosts file. You could also attempt to add the lookup domain for the network config, but hosts file is fairly quick.
10.1.0.11 vcsa1.company.com vcsa1 10.2.0.11 vcsa2.company.com vcsa2
Use AD authentication for vCSA shell access.
http://www.virtuallyghetto.com/2017/10/enabling-shell-access-for-active-directory-users-via-ssh-to-vcenter-server-appliance-vcsa.html