So I'm messing around in my lab and testing all of my plug-ins in advance of my vSphere 5 production upgrade. One of the components I need to test is my XenDesktop environment against vSphere 5. In the past you had three options, disable security by removing the https redirects, enable security by using a corporate CA or a commercial signed certificate. Disabling security has always been a no-no, but was accomplished by modifying the "proxy.xml" file in vCenter. In VMware vSphere 5 the "proxy.xml" is still under the C:ProgramDataVMware folder. No one should break security just to make life easier. According to CTX119849, you must use HTTPS in order for the DDC to communicate with vCenter. The default certificate from vCenter will not work either!