HELP - Understanding converting from vCenter Embedded to Platform Services Controller

[netwatcher_s1]

I'm trying to convert my current embedded vCenter Server to point to an external PSC.  I think I have done that, but my problem is when I login via another vCenter Server, which is pointed to the new external PSC, I do not see my Datacenter, datastores, virtual machines, etc. that I had on my embedded server.  The new vCenter Server is basically thinking I'm starting over.  I'm confused by this, because when I pointed my original embedded vCenter Server to the new PSC shouldn't it of copied my database info to the new PSC?  That way when other vCenter Servers connect to the new PSC it will show vm's and datastores etc. in the vSphere web client?

I'm confused by the conversion from using an embedded vCenter Server and going to PSC servers.  And I do not know why my data is still only showing on my original embedded vCenter Server and no where else.  I've connected a second new installation of vCenter Server to the new PSC and I do not see my original data from the original vCenter embedded server.  I am using version 6 update 1 for ESXi and version 6 for vCenter Server.

So how do I get my original vCenter Servers' Datacenter data to show up on my new PSC server whilst accessing it from a new vCenter server that is pointed to the PSC?

Thanks!

Jay

[JamieGator32]

It sounds like you may have installed a new SSO domain on another Windows server successfully. Did you go through the repointing process to register your inventory, vCenter, and web client with the new SSO domain that is external to your vCenter server?

Here is a kb on the repointing procedure: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2033620

It is not for the faint of heart. My only advice would be to uninstall your services from vCenter and then reinstall the once more to point to the external SSO domain for each registered service.

[vmEck]

JamieGator32 That KB is only applicable to vCenter Server 5.1/5.5.

netwatcher_s1 Here is a great blog that illustrates what you need to do: http://blogs.vmware.com/vsphere/2015/10/reconfiguring-and-repointing-deployment-models-in-vcenter-server-6-0-update-1.html

It sounds like you didn't quite get the entire process completed. Also note, you need to be running at least vCenter 6.0 Update 1 in order to perform this repoint operation.

And to clarify your vCenter Database does not live on the PSC. It still lives on the vCenter Server. To learn more about the PSC you should take a look at this article: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2113115

If you have other questions that aren't answered by the 2 articles just let me know.

[JamieGator32]

That's correct Adam. I was in the admittedly bad habit of calling an external SSO on 5.5 a PSC since I am in the process of upgrading 2 vCenters with one SSO environment. After discussions with my TAM we were referred to Ryan Johnson's blog post

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2033620

He has some great slides as well at http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2033620

After discussing my environment with Ryan he suggested making our SSO domains for both vCenters external in preparation of upgrading to 6.1. So in my mind I had already made the jump to calling the external SSO servers PSCs.

Thanks for the clarification.