I have 3 different instances of vCenter, all 3 were installed in basic mode. Eventually, I'd like to upgrade to vSphere 6, and I like the idea of being able to vMotion between sites but since my vCenters were all installed in basic mode, I won't have that option. During an upgrade of vSphere 6, it doesn't seem like you can separate the SSO/PCS.
Is my only option to follow this article? http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=203362...
is this even the correct approach?
I'd also like to throw in SRM later this year, so is that more reason to separate the SSO, or does it not matter?
is this even the correct approach?
If you have vCenters 5.5, then yes.
1. On separate VM install SSO 5.5
2. Use KB to repoint 3 vCenters to new SSO 5.5. You have to run 3 cmds from this KB (one to change SSO, one for Inventory Service and one for Web Client)
3. Uninstall local SSO from vCenters.
4. Check connectivity for vClient and Web Client
5. Upgrade separate SSO server to version 6
6. Upgrade 3 vCenters to version 6
I have tested this few times and it works good. If you have 5.1, that is different story, i'm struggling with it myself.
this is the only way I know to repoint the vCenters to another SSO Instance...
is this even the correct approach?
If you have vCenters 5.5, then yes.
1. On separate VM install SSO 5.5
2. Use KB to repoint 3 vCenters to new SSO 5.5. You have to run 3 cmds from this KB (one to change SSO, one for Inventory Service and one for Web Client)
3. Uninstall local SSO from vCenters.
4. Check connectivity for vClient and Web Client
5. Upgrade separate SSO server to version 6
6. Upgrade 3 vCenters to version 6
I have tested this few times and it works good. If you have 5.1, that is different story, i'm struggling with it myself.
Thanks everyone.
Yes, I'm running vCenter 5.5 thankfully!