444 Appendix XenApp 6 FOR WINDOWS 2008 R2 The XenApp content in this book is based on the XenApp 5 Feature Pack 2 version of the product. At the time of writing XenApp 6 for Windows 2008 R2 has been released in the Tech Preview form. Broadly speaking, the settings that need to be configured haven't changed significantly, but rather the management consoles have been simplified. VMware SDK INTEGRATION The interaction between the Citrix components (the Desktop Delivery Controller and the XenDesk- top Setup Wizard) and the VMware hypervisor stack is done through the VMware SDK. The VMware SDK is normally only accessible through HTTPS. The SDK security settings can, however, be changed to allow this communication to occur over HTTP. This is the first choice of many IT engineers ­ who hear the word "Certificates" and break out into a cold sweat! Humor aside, security policies don't always allow you to change the settings to HTTP. I would recommend HTTP for a proof of concept environment, but for a production environment, it would be advisable to use secured communications. The XenDesktop Setup Wizard requires the changes be made on the provisioning server. Changing the SDK Requirements to HTTP In order to change the SDK to allow HTTP access, one has to edit the proxy.xml file on the Virtual Center/vCenter Server. The proxy.xml file is in the "All Users" profile, which is C:\Documents and Settings\Application Data\VMware\VMware VirtualCenter\proxy.xml under Windows 2003, and C:\Users\Application Data\VMware\VMware VirtualCenter\proxy.xml on Windows 2008. Open the proxy.xml <e id="5"> <_type>vim.ProxyService.LocalServiceSpec</_type> <accessMode>HTTPSWithRedirect</accessMode> <port>8085</port> <serverNamespace>/sdk</serverNamespace> </e> Change the section "HTTPSWithRedirect" to "HTTPAndHTTPS" <e id="5"> <_type>vim.ProxyService.LocalServiceSpec</_type> <accessMode>HTTPAndHTTPS</accessMode> <port>8085</port> <serverNamespace>/sdk</serverNamespace> </e> Connecting Using HTTPS This was fairly easy to manage in versions 3 and 3.5, unfortunately changes to how the certificates are created for vCenter (version 4) has made this trickier for the latest version of VMware's software.