XenDesktop.ppt

Let’s start by looking at the end user view. A typical XD deployment caters very well for users access virtual desktops through the Intranet. In a desktop-replacement scenario, where the user’s desktop is entirely virtualized, Desktop Appliances are the most cost effective way of delivering access. DAs are available from a wide range of Citrix partners, and are access devices that require minimal management overhead and provide an excellent end user experience when accessing and using virtual desktops. Of course our reference architecture works also well for remote and home users, who would typically connect through the Internet. The Citrix Access Gateway functionalityis included in all XenDesktop editions and ensures that the communication with the virtual desktop is safe and secure – it works just like it always has when deployed in conjunction with XenApp. Besides the end user devices and security appliances such as the gateway, all other components reside in the data center. We recommend that XD farms are not deployed across data centers separated by WANs. Instead, in such an environment you should implement separate farms in every site, and aggregate them using Web Interface technology that underpins the end user access mechanism. The Desktop Delivery Controller is responsible for providing access to desktops, managing them and brokering access. It is built on top of XenApp technology, and is thus fully fault tolerant. In our reference architecture, the virtual desktops are running as Virtual Machines – this is the most economic solution and can exploit the advantages of virtualisation, e.g. Allowing unused virtual desktops to be suspended so that they don’t consume valuable resources. However, of course XD also supports virtual desktops running on top of blade PC hardware, if your applications require this (remember traders?). In any case, the virtual desktops should be properly secured and ideally be hosted in a separate security enclave in the data cente