This is a followup to https://vmscribble.com/vcenter/vcenter-6-upgrade-options-to-enable-cross-vcenter-vmotion-in-the-same-sso-domain/ Where you already have a brand new 6.0 VCSA (external PSC) and want the 5.5 windows VC upgrade to be on the same SSO domain. Option A
Install a new 6.0 VC (new SSO domain). Upgrade the current windows 5.5 VC to 6.0. Un-install the window 6.0 VC. Re-install 6.0 choosing the 6.0 VCSA SSO domain (external PSC). This will allow you to drain the upgraded 5.5 VC so it can be decommissioned (using esxi 6.0 and cross vcenter vmotion)
Note – Even though the new 6.0 and existing/upgraded 5.5 VC’s have vpshere.local as the SSO domain name, they are NOT on the same SSO domain. It is tricky.
You will lose tags, custom VC roles and user permissions for all objects (even at the root VC level.. You will have to re-join to AD.
For grins, I will follow these steps in the manual to prove I can not point the windows VC to the external PSC (eventhough the sso domain listed is the same vsphere.local)
“Reconfigure a Standalone vCenter Server with an Embedded Platform Services Controller to a vCenter Server with an External Platform Services Controller”
On the external PSC.
psc1:~ # /usr/lib/vmware-vmafd/bin/vmafd-cli get-domain-name –server-name localhost
vsphere.local
psc1:~ # /usr/lib/vmware-vmafd/bin/vmafd-cli get-site-name –server-name localhost
psc1-site
psc1:~ # /usr/lib/vmware-vmafd/bin/vmafd-cli get-ls-location –server-name localhost
https://psc1.lab.com/lookupservice/sdk
On the windows VC and am ready to break apart the embedded PSC and point to the exteral PSC.
cd C:Program FilesVMwarevCenter Servervmafdd
vmafd-cli get-domain-name –server-name localhost
vmafd-cli get-site-name –server-name localhost
vmafd-cli get-ls-location –server-name localhost
In my case the site name is 5-5-site and the domain is vsphere.local
cd C:Program FilesVMwarevCenter Serverbin
cmsso-util reconfigure –repoint-psc psc1.lab.com –username administrator –domain-name vsphere.local –passwd VMware1!
C:Program FilesVMwarevCenter Serverpython-modulesidentityvmkeystore.py:4:
RuntimeWarning: to-Python converter for struct client already registered; second
conversion method ignored.
import identity.vmafd as vmafd
C:Program FilesVMwarevCenter Serverpython-modulesidentityvmkeystore.py:4:
RuntimeWarning: to-Python converter for class vmafd_exception already registered
; second conversion method ignored.
import identity.vmafd as vmafd
Validating Provided Configuration …
Error: The provided Platform Services Controller(PSC) psc1.lab.com is not a replication partner of the localhost. Please make sure to provide the Primary Network Identifier (PNID) of the PSC.
Shut down and take a snapshot while powered off of the windows VC VM.
Power on and backup the embedded database using KB Uninstalling vCenter Server 6.0.x resets the embedded VMware Postgres database (2108547)
Open C:ProgramDataVMwarevCenterServercfgvmware-vpx vcdb.properties and copy the password to a new text file.
Stop the VMware VirtualCenter service (which will stop all of the dependent services)
Open a command prompt as admin and type in
cd %VMWARE_CIS_HOME%Python
I extraced the zip file in the KBA to c:windows_backup_restore r0{bX(gnh7vNA39c is the password in vcdb.properties
python c:windows_backup_restorebackup_win.py -p “r0{bX(gnh7vNA39c” -f c:windows_backup_restorebackup_VCDB.bak
Open C:ProgramDataVMwarevCenterServercfgvmware-vpx vcdb.properties and copy the password to a new text file.
Stop the VMware VirtualCenter service (which will stop all of the dependent services) net stop “VMware VirtualCenter Server”
Open a command prompt as admin and type in
cd %VMWARE_CIS_HOME%Python
I extracted the zip file in the KBA to c:windows_backup_restore Yhn{V<*JeZiN$4uH is the password in vcdb.properties
python c:windows_backup_restorerestore_win.py -p “Yhn{V<*JeZiN$4uH” -f c:windows_backup_restorebackup_VCDB.bak
Start the VMware VirtualCenter service net start “VMware VirtualCenter Server”
I had to start the VMware vSphere Web Client service
In the web client, click Home, System Configuration. You will see the external PSC.
You can also validate the ext psc by going to the root VC object / Manage / Settings / Advanced and search for sso The following 3 keys will noted the ext psc.
config.vpxd.sso.admin.uri
config.vpxd.sso.groupcheck.uri
config.vpxd.sso.sts.uri
Reboot the windows VC VM, validate and remove the snapshot.