As I was playing around with XenDesktop 4, I had some trouble connecting the Citrix Desktop Delivery Controller to the vCenter server. And as 95% of Xendesktop deployments are on VMware VI or vSphere, I thought this tip could be useful for you as wel.

What I was asked to do when creating a desktop group was to enter the vCenter Server address in the following format:

https://<vCenter server name>/sdk

(BTW, this address is case sensitive)

The Desktop Delivery Controller only accepts a trusted certificate and by default, that is not the case with vCenter’s SDK website. So you have 3 options:

• import the certificate that is used with vCenter server on the Desktop Delivery Controller server.
• Use a trusted certificate.
• Enable HTTP on the SDK website. 

For test/demo environments you can use the last option, for production I would recommend the second option. Jarian Gibson wrote an article that describes how to do this.

Related articles

• June 25, 2010 -- VDI comparison chart
• November 2, 2009 -- Bloggers-battle: Citrix Xendesktop vs VMware View
• March 10, 2009 -- SAP adopting Citrix XenServer next to VMware ESX: weird or smart ?
• June 3, 2008 -- VDI comparison
• May 20, 2010 -- 7 “challenges” migrating from XP to Windows 7 using VDI
• November 4, 2009 -- Bloggers-Battle: Desktop Virtualization is THE way to go!
• May 30, 2009 -- Reduce MS licensing costs by 95% !!! in a virtualized environment.
• May 5, 2009 -- Synergy First Day impression
• April 7, 2009 -- Citrix XenApp on VMware ESX: 1 or 2 vCPU part 2
• March 5, 2009 -- Citrix XenApp on VMware ESX: 1 or 2 vCPU?

Tags: Citrix, VMware, Xendesktop

1. Artem A. Razin Says:
   December 20th, 2009 at 2:58 pm

   Hello, Sven!

   interesting article, thank you.

   PS I’ve tried to contact you but without success, could you please drop me a line to my email. I have one small question… thank you in advance!

   Reply