As you might have already read my previous post on Migrating from Embedded SSO to External PSC you probably know how tedious the vCenter Server 5.5 re-pointing process can be.
I’ve taken VMware’s KB2033620 a wrapped it all up in Windows Batch Script to largely automate the process.
DISCLAIMER: The script provided here comes with zero support from VMware or myself. It is my own utility. Use at your own risk. It is your responsibility to take the necessary backups and precautions.
- Inventory Service, vCenter Server, Web Client must all exist on this machine.
- Advise to be running vCenter Server 5.5 U3e first as some bugs with the repointing process have been fixed with that release.
- There is no error handling – if one of the services fail to repoint the script will still continue on.
Download the hytr-repoint_vc55.bat from HERE.
Extract the zip file to the Windows vCenter Server 5.5 machine
Open an Administrator Command Prompt to the location of the script
Run the following to run the script and to prevent the command prompt window from closing on error
cmd /k hytr-repoint_vc55.bat
The initial output should be similar to the below.
- You will be asked for the FQDN of the new SSO Server and the administrator@vsphere.local password.
- The script will auto-detect the installation paths of the services
- It will ensure you have extracted the sso_svccfg.zip
C:\Users\Administrator\Desktop>cmd /k repoint_vc55.bat This utility assumes that the Inventory Service, vCenter Server and vSphere Web Client are all installed on this machine *************************************************** Enter new external SSO details *************************************************** Enter the FQDN of the new SSO Server: external-sso.domain.com Enter the Administrator@vsphere.local Password for external-sso.domain.com: ***** VMware JRE install location: C:\Program Files\Common Files\VMware\VMware vCenter Server - Java Components\ Inventory Service install location: E:\Program Files\VMware\Infrastructure\Inventory Service vCenter Server install location: E:\Program Files\VMware\Infrastructure\VirtualCenter Server\ Web Client install location: E:\Program Files\VMware\Infrastructure\vSphereWebClient\ Local FQDN: VC1.DOMAIN.COM New SSO Server to repoint to: external-sso.domain.com *************************************************** "You have not unzipped sso_svccfg.zip" "Unzip sso_svccfg.zip located at E:\Program Files\VMware\Infrastructure\VirtualCenter Server\ssoregtool\ before proceeding" *************************************************** Press Enter to Continue once sso_svccfg.zip has been unzipped Press any key to continue . . . *************************************************** The vCenter Server services will be repointed to the SSO on external-sso.domain.com Press CTRL+C to cancel and correct any variables and run the batch file again. DISCLAIMER: This script does not perform any error checking outside of checks from the VMware scripts called It is STRONGLY advised that you update your vCenter Server 5.5 to U3e first as some repointing issues have been fixed By proceeding you agree that you have taken the necessary backups/snapshots of your environment *************************************************** Press any key to continue . . .
have you tried reinstalling? 
Féidhlim, OMG this worked great!!! It was so easy I thought it had failed until I checked config.vpxd.sso.admin.uri under advanced settings…golden Thanks
LikeLiked by 1 person
Awesome Ray, glad it was of help!
LikeLike
Have a specific question could you help please? Re-pointing to new 5.5 multisite SSO server I built for customer. During build I was offered a custom port, 8888 for http which I accepted. Repoint to this machine was successful.
Now I’m using 6.0U2m to migrate. The pre-checks in migration assistant for my vCenter are reporting warnings that the port I used for HTTP is unsupported. I know the migration will not proceed. I have migrated the first site vCenter and SSO to to 6.0 appliances. Now I have the partnered SSO and vCenter with the custom port unable to migrate. How to change the ports on these windows machines? When I change the http port to 80 in the registry for vCenter vCenter works but the migration assistant reports. Error:
“Unable to fetch or parse VC URL from vCenter ServiceInstance!
Resolution: VC URL in vCenter is unreadable. The vCenter Service may not be reachable.
Any ideas? do these ports need to be changed in SSO and vC?
LikeLike
Hi Ray, for this I would advise getting a support request open with VMware Support so they can investigate.
LikeLike
Féidhlim, is the bat file for this still available? Getting stuck with the migration and it’s driving me nuts.
Thanks!
LikeLike
Hi – sorry Dropbox messed up all my public links https://www.dropbox.com/s/of36kz9zvu023nc/hytr-repoint_vc55.zip
Updated the post too.
LikeLike
Hi Guys, has anyone else tried the script? I’m getting ready to upgrade our environment and this would come in really handy if it does indeed work. We have 9 5.5 vcenter servers in link-mode, which means i would need to break it up for each vcenter, one at a time, deploy a new SSO and run the script (9 times) to re-point each vcenter to its new SSO server.
LikeLike