Hi

The support comment was in reference to Scott's comment from the VMware engineer re SSO, vCenter and VCHB on the same server. I didn't see anything about this in the VCHB release notes to be honest.

So the issue is really with protecting SSO when multiple vCenters are deployed(linked or not), and how VCHB can be used to protect the SSO service.

If you could find the KB that would be great.

Cheers

David

What do you mean lack of support? It's supported to be on the same server as vCenter and protected by VCHB. But there is a workaround that needs to be applied to get it to work properly (I don't have the KB off hand). It's just that in the scenario where you have multiple vCenters in play it makes sense to have SSO on it's own VM and not tied to any particular vCenter.

Is this lack of support for SSO on the same server as vCenter and protected by VCHB detailed in any VMware KB's anywhere?

Thanks

Hi Scott, while there are problems that have to be worked around when running SSO on the same host as vCenter and protecting it with Heartbeat this doesn't change the fact that is a supported solution and is documented as such in the VMware product documentation. However, this configuration would not be recommended in the current state due to the problems and defects. The recommended configuration would be to have SSO configured on it's own server, separate from vCenter and then protect that server with vCenter Heartbeat. This would use the same vCenter Heartbeat license. The video included in this article is validated and supported by VMware and supported by VMware Global Support Services. There are other methods of protecting SSO that are documented in VMware KB's.