This release unifies hosted applications and desktops (XenApp) with personalized desktops (XenDesktop) within a single architecture and management experience. The capabilities previously available within XenApp are now delivered within the XenDesktop infrastructure and components. If you have prior experience managing XenApp farms, this document helps you understand the following:
To review some of the past XenApp features that are deprecated in this release, see Features not in this release.
The following terms and concepts are important for you to understand so that you can effectively publish applications and desktops from the unified infrastructure. When you publish applications, you are creating or adding applications. These components are:
In moving from a traditional XenApp environment to the unified environment, you will find the following key differences:
For example, instead of using folders and Worker Groups to organize applications, servers, and other resources, in Studio you organize those resources using a combination of machine catalogs, tags, Delivery Groups, and Delegated Administrators.
If you already have experience with a XenDesktop or XenApp environment, it will be helpful to you to identify the components introduced in this release and learn how they work and communicate with each other. Under the new architecture, XenDesktop and XenApp are unified, including management and delivery components, to give administrators a unified management experience.
This figure shows the key components in a typical deployment.
The core components of this release are:
Director — Director is a web-based tool that enables IT support and help desk teams to monitor an environment, troubleshoot issues before they become system-critical, and perform support tasks for end users. You can also view and interact with a user's sessions using Microsoft Remote Assistance.
Receiver — Installed on user devices, Citrix Receiver provides users with quick, secure, self-service access to documents, applications, and desktops from any of the user's devices including smartphones, tablets, and PCs. Receiver provides on-demand access to Windows, Web, and Software as a Service (SaaS) applications.
StoreFront — StoreFront authenticates users to sites hosting resources and manages stores of desktops and applications that users access.
Studio — Studio is the management console that enables you to configure and manage your deployment, eliminating the need for separate management consoles for managing delivery of applications and desktops. Studio provides various wizards to guide you through the process of setting up your environment, creating your workloads to host applications and desktops, and assigning applications and desktops to users.
License server — License server manages your product licenses. You must create at least one license server to store and manage your license files.
Delivery Controller — Installed on servers in the data center, the Delivery Controller consists of services that communicate with the hypervisor to distribute applications and desktops, authenticate and manage user access, and broker connections between users and their virtual desktops and applications. The Controller manages the state of the desktops, starting and stopping them based on demand and administrative configuration. In some editions, the Controller allows you to install Profile management to manage user personalization settings in virtualized or physical Windows environments. Each site has one or more Delivery Controllers.
XenServer — XenServer is an enterprise-class virtual machine infrastructure solution that creates the foundation for delivering virtual desktops and offers advanced management features. Multiple VMs can run on XenServer, which takes advantage of the advanced virtualization features of the latest virtualization-enabled processors from Intel and AMD. For more information about XenServer, see the XenServer documentation in eDocs.
Virtual Delivery Agent (VDA) — Installed on server or workstation operating systems, the VDA enables connections for desktops and apps. For Remote PC Access, install the VDA on the office PC.
Machine Creation Services (MCS) — A collection of services that work together to create virtual servers and desktops from a master image on demand, optimizing storage utilization and providing a pristine virtual machine to users every time they log on. Machine Creation Services is fully integrated and administrated in Citrix Studio.
Windows Server OS machines — VMs or physical machines based on Windows Server operating system used for delivering applications or hosted shared desktops to users.
Desktop OS machines — VMs or physical machines based on Windows Desktop operating system used for delivering personalized desktops to users, or applications from desktop operating systems.
Remote PC Access — User devices that are included on a whitelist, enabling users to access resources on their office PCs remotely, from any device running Citrix Receiver.
Additional components provide the following features:
Secure delivery — When users connect from outside the corporate firewall, this release can use Citrix NetScaler Gateway (formerly Access Gateway) technology to secure these connections with SSL. NetScaler Gateway or NetScaler VPX virtual appliance is an SSL VPN appliance that is deployed in the demilitarized zone (DMZ) to provide a single secure point of access through the corporate firewall.
WAN optimization — In deployments where virtual desktops are delivered to users at remote locations such as branch offices, Citrix CloudBridge (formerly Citrix Branch Repeater or WANScaler) technology can be employed to optimize performance. Repeaters accelerate performance across wide-area networks, so with Repeaters in the network, users in the branch office experience LAN-like performance over the WAN. CloudBridge can prioritize different parts of the user experience so that, for example, the user experience does not degrade in the branch location when a large file or print job is sent over the network. HDX WAN Optimization with CloudBridge provides tokenized compression and data deduplication, dramatically reducing bandwidth requirements and improving performance. For more information, see the Citrix CloudBridge documentation.
In XenApp, you use the Publish Application wizard to prepare applications and deliver them to individuals or groups of users. In XenDesktop, you use the Studio component to create and add applications to make them available to users who are included in a Delivery Group. Using Studio, you first configure a site, create and specify machine catalogs, and then create Delivery Groups within those machine catalogs. Delivery Groups are then used to determine which users have access to the applications you deliver. Refer to the Deliver section for this release.
Once you have created Delivery Groups, you can then create an application to specify which Delivery Groups will provide access to that specific application. In Studio, you can view which applications are added to a selected Delivery Group, as well as enable, disable, or modify the applications. For a detailed explanation of how you configure Delivery Groups to make applications available to users, see Delivery Groups.
These methods are available for delivering applications, and you can choose the method that is most appropriate for your specific environment:
There is no XenApp to XenDesktop 7 upgrade. Citrix will support customers in their migration from XenApp 6.5 to XenDesktop in a future release and plans to release tools and/or scripts to assist in this transition.
The Studio management and Director can monitor and manage only XenDesktop 7 sites. The monitoring and management tools do not support past versions of XenDesktop or XenApp. For example, XenDesktop 7 Director requires a XenDesktop 7 Delivery Controller. Director 7 can monitor XenDesktop 5. x VDAs; however, some data, including logon duration, will not be available with the XenDesktop 5. x VDAs.
Citrix recommends that if you continue running deployments of past versions of XenApp or XenDesktop, you run them in parallel wiht the XenDesktop 7 site and continue running the management consoles with each release for that site. For example, in a mixed environment, to continue using Desktop Director 2.1 to monitor XenApp 6.5, make sure that Desktop Director 2.1 is installed on a separate server from Director 7.
Use StoreFront to aggregate applications and desktops from the different versions of XenApp and XenDesktop.