I’ve been mentioning for a while now the importance of considering how you want your PSC design to look in vSphere 6 to my customers. I’ve also made sure to point out that the path from an internal SSO (common in vsphere 5.x) to an external PSC (what I recommend to almost everyone in vSphere 6) is neither straightforward, nor automated.
Next generation hybrid cloud architecture for EUC: http://vmw.re/1KX78mW
It’s kind of a big deal.
I want to bring your attention to this KB article, regarding the Web Client and its inability to load after May 5th.
The upshot is this:
- Problem: the web client fails to load with vSphere Web Client 5.0 after May 5th.
- Solution: In progress. VMware engineering is aware of the issue and this is a high priority item to fix.
- Work-around: It’s a bit involved (but certainly not impossible), so you are best to see the KB article for details.
It is not the end of the world, as the C# client will still function, but it is of course highly inconvenient. If more significant news regarding this is made available I will be sure to share it. The KB article will be updated once a fix is available as well.
See this VMware KB article: List of recommended topologies for VMware vSphere 6.0.x (2108548). Pay particular attention to the deprecated topologies:
It further reinforces my recommendation that unless you have a very, very tiny corner case, your Platform Services Controller (PSC) should be external.