www.citrix.com
Technical Guide for Adding
XenDesktop™ 4 to an
Existing XenApp™ 5
Environment
Citrix Systems released XenDesktop 4 on November 16, 2009.
This document provides technical insights related to adding
XenDesktop 4 to an existing XenApp environment. In addition
to easy-to-follow installation steps, this document includes
several sample scenarios. It should serve as a technical guide for
Citrix administrators and partners.
Author: Jo Harder, Citrix Worldwide Technical Readiness Date Created: December 2009
Page 2
Table of Contents
Introduction 3
XenDesktop 4 FlexCast™ Delivery Technology...3
Existing XenApp + New XenDesktop ...4
Existing XenApp Architecture ...4
Upgrade vs. Migration ...5
Licensing ...5
Reusing XenApp Components/Features 6
Additional Technical Considerations ...9Installing XenDesktop Virtual Desktops Where XenApp Infrastructure Exists 11
Sequential Installation Order for XenDesktop Virtual Desktops: Easy as 1-2-3-4! ... 11Adding Provisioning Services to Support XenDesktop ... 12
Adding EdgeSight for Virtual Desktops ... 13
Deployment Scenarios 14
Scenario #1: Adding Virtual Desktops to Address New Call Center Users... 14Scenario #2: Adding VM Hosted Apps on PC Blades to Support a Resource-Intensive App ... 20
Page 3
Introduction
On November 16, 2009, Citrix released XenDesktop 4. Citrix XenDesktop is a desktop virtualization solution that delivers Microsoft© Windows™ desktops as an on-demand service to any user, anywhere. XenDesktop 4 Enterprise and Platinum editions include XenApp functionality, and customers that purchase XenDesktop VDI edition licenses or those that take advantage of the XenDesktop Trade-Up program may wish to retain their existing XenApp infrastructure and add XenDesktop functionality.
To facilitate adding XenDesktop to an existing XenApp infrastructure, this guide contains the following sections:
• Reusing XenApp Components/Features
• Installing XenDesktop Where XenApp Infrastructure Exists
• Deployment Scenarios
XenDesktop 4 FlexCast™ Delivery Technology
XenDesktop 4 introduced FlexCast delivery technology. To the IT professional, this means that there are six options for delivering desktop resources to users:
Type Description Example
Hosted Shared
Desktops Locked down desktops based on
a shared server XenApp published desktop Hosted VM-based
VDI Desktops Personalized Windows desktops
based on a virtualized desktop Virtualized desktops hosted on XenServer
Hosted Blade PC
Desktops Personalized Windows desktops
based on a blade PC Desktops hosted on blade PCs Local Streamed
Desktops Local desktops based on a
streamed image Local desktops streamed by means of Provisioning services Virtual Apps to
Installed Desktops Virtual apps accessed by a client
device VM Hosted Apps
Local VM-based
Desktops Virtualized desktops that can be
accessed offline XenClient
Page 4
Existing XenApp + New XenDesktop
Organizations may require more than one of the FlexCast delivery technologies described above. Because many organizations may have needs for both application virtualization and desktop virtualization based on distinct business and technical requirements, what has traditionally been known as both XenApp and XenDesktop farms may be required to address those requirements. As such, this document focuses on those administrators that have existing XenApp environments and wish to add XenDesktop functionality. From the user perspective, users that have been authorized to use both XenApp and XenDesktop resources can access both from a Web Interface site or the StartÆPrograms menu.
Later in this document, several sample scenarios are presented so that the IT professional has a better understanding of the implementation steps and the reasons why those steps are undertaken. Specifically, the following sample scenarios are explored:
Scenario Example
Adding XenDesktop to a XenApp
environment to address desktop virtualization requirements for a specific group of users
Call center users will access virtualized desktops
Adding XenDesktop to a XenApp environment to address application virtualization requirements for a specific application
A resource-intensive application that is not compatible with any Windows Server platform will be hosted on PC blades and accessed as VM Hosted Apps through XenApp
Existing XenApp Architecture
For the purposes of this document, references to XenApp are based on one of the following:
• Presentation Server 4.5
• XenApp 5 for Windows Server 2003
• XenApp 5 for Windows Server 2008
Citrix strongly recommends upgrading to XenApp 5 Feature Pack 2; however, notations will be provided within this document where the most recent feature or component is recommended or required. For information regarding upgrading or migrating to XenApp 5 Feature Pack 2, please see CTX122303 for more information.
Page 5
Upgrade vs. Migration
Within this document, there is a distinction between the terms upgrade and migration as defined below:
• Upgrade: installing a newer version of a feature or release over an existing version
• Migration: a clean, new installation of that feature or release
Licensing
This document assumes the use of the XenDesktop Platinum edition. This guide discusses the technical aspects of the Citrix License Server but does not incorporate Microsoft licensing requirements. Please consult Microsoft licensing documentation.
Page 6
Reusing XenApp Components/Features
The following components or features can be reused for XenDesktop deployments:
XenApp Component or Feature
Reusability
Active
Directory • Designate a new OU where XenDesktop functionality will be housed. This can either be a child OU of a parent OU that contains other Citrix components or a new OU. The designated OU will be assigned a Service Connection Point for Virtual Desktop Agent registration; it will not contain any Desktop Delivery Controllers.
• Where Citrix Profile management is implemented, a sister OU enables the same profile to apply to both XenApp and XenDesktop where enabled as part of the parent OU.
License
Server • If reusing the existing Citrix License Server, do not install a new Citrix License Server during XenDesktop installation. The Citrix License Server must be based on version 11.6.1; build 9019 will function, although build 9020 is strongly recommended.
Upgrade if necessary.
• Ensure that the startup license (as downloaded from My Citrix) is dated November 16, 2009, or later. Delete any startup licenses prior to that date.
• Add XenDesktop licenses to the existing Citrix License Server.
If appropriate, delete extraneous license files.
• Designate the existing Citrix License Server in the XenDesktop Delivery Services Console (Farm PropertiesÆLicense Server).
Database
server • Add a database instance for the XenDesktop data store to the existing SQL Server or Oracle database server. During the Desktop Delivery Controller installation, designate the existing database server when prompted.
• If a new Provisioning services farm will be implemented,
designate a SQL Server database instance for this purpose as well.
Page 7
XenApp Component or Feature
Reusability
Management
consoles • The Delivery Services Console (formerly known as the Access Management Console) can be consolidated within a custom MMC to administer both XenApp and XenDesktop farms. Any other MMC-based management consoles can also be
consolidated within a custom MMC. If Web Interface is installed on that server, it too can be consolidated into a custom MMC.
Note that the Web Interface MMC is only installed in
conjunction with Web Interface and is thus the Web Interface MMC is not available as a standalone installation.
• The Advanced Configuration Console/Presentation Server Console servicing XenApp and XenDesktop farms cannot be accessed from the same server because both use distinct versions of the same executable (ctxload.exe).
Web Interface • If presenting both XenApp applications and XenDesktop resources through the same Web Interface site is desired, do not install Web Interface during XenDesktop installation (command line setup.exe –nosites). For this purpose, Web Interface must be based on version 5.2; if necessary, upgrade to this version.
• If XenDesktop resources will be located from a distinct Web Interface site, install Web Interface as part of the XenDesktop installation.
• Where Zone Preference and Failover is used for XenApp
application availability, Web Interface User Roaming functionality can be configured within the WebInterface.conf file to address XenDesktop failover requirements.
XenApp published applications (streamed or hosted)
• Hosted or streamed applications can be made available through XenDesktop. Enabling these applications by means of a Web Interface Services site--as presented to the user within the StartÆAll Programs menu--generally provides the most transparent means for user access. Where applications will be streamed to the virtual desktops, pre-caching the applications should be considered for faster startup.
Page 8
XenApp Component or Feature
Reusability
Profile
management • If Citrix Profile management is implemented for the XenApp servers based on v1 (Windows Server 2003) or v2 (Windows Server 2008) platforms, consider the new XenDesktop operating system platform and Active Directory OU structure. For example, users accessing Citrix profiles based on XenApp 5 for Windows Server 2008 (v2) and XenDesktop based on Windows 7 (v2) under the same parent OU can successfully utilize the same user profile, whereas users accessing Citrix profiles based on XenApp 5 for Windows Server 2003 (v1) and XenDesktop based on Windows 7 (v2) under the same parent OU cannot
successfully utilize the same user profile.
WAN Optimization • HDX IntelliCache (ICA Acceleration) benefits achieved with Branch Repeater 5.5 (and higher) and XenApp 5 for Windows Server 2003 (HRP4 and higher) is likewise built into XenDesktop 4. ICA traffic is automatically optimized based on these
prerequisites, and no configuration or changes are necessary.
Service
monitoring • Service Monitoring (Citrix EdgeSight technology) can be used in the same manner as the physical desktop deployment. Each XenDesktop virtual desktop requires the installation of the Service Monitoring for Virtual Desktop Agent. Enabling XenDesktop functionality for an existing XenApp Service Monitoring implementation requires the addition of the EdgeSight Agent database server in order to capture data from pooled virtual desktops prior to being redeployed.
Provisioning
services • Provisioning services should be used to provision virtual desktop images. Where possible, minimize the number of virtual desktop images in order to facilitate easy management.
• Although XenApp avails multiple Zone Data Collectors to support large sites, XenDesktop requires distinct farms because there is only one farm master. In addition, bandwidth constraints and SQL Server replication generally cannot effectively support multiple locations; thus, consideration should be given to creating a XenDesktop farm and corresponding Provisioning Services farm for each site.
Citrix Online
plug-In • Citrix Online plug-in version 11.2 is required where both XenApp and XenDesktop will be accessed from the same physical client device. If necessary, upgrade the client software to this version.
Page 9
XenApp Component or Feature
Reusability
Single
Sign-on • Now that Single Sign-on (Password Manager) is included with XenDesktop Platinum, password management on XenDesktop devices can be used in the same manner as the physical desktop deployment that has been available with XenApp Platinum.
Thus, the Single Sign-on agent must be installed on each virtual desktop.
EasyCall voice services
• EasyCall can be used in the same manner as the physical desktop deployment. The EasyCall plug-in must be installed on the XenDesktop virtual image.
Citrix
Receiver • The Citrix Receiver plug-in should be pre-installed as part of the XenDesktop image.
• Citrix Receiver can be used in the same manner as the physical desktop deployment. No changes to the Merchandising Server are required; however, administrators may wish to assess the agents and/or plug-ins that are required for XenDesktop as the full set would not likely be required.
Additional Technical Considerations
When installing a new XenDesktop farm within an environment where XenApp already exists, consider the following:
Aspect Description
Port 8080 XenDesktop uses TCP port 8080 for communications between virtual desktops and the Desktop Delivery Controller. Where TCP port 80 is not shared with IIS for Web Interface Citrix XML Service
communications, port 8080 is sometimes selected. In addition, the Citrix License Server prior to 11.6.1 build 9020 may have port 8080 conflicts; upgrading to Citrix License Server 11.6.1 build 9020 addresses potential port 8080 conflicts. Thus, XenDesktop Desktop Delivery Controllers, Web Interface, XenApp Data Collectors, and Citrix License Server communications should be validated to ensure that no conflicts exist with TCP port 8080 traffic.
Page 10
Citrix policies Where Citrix policies, such as drive mappings, are configured for a XenApp farm, these policies also need to be configured within the XenDesktop farm. Citrix policies are only applicable to the farm where configured, and XenApp policies do not extend to a XenDesktop farm.
VM Hosted
Apps Although accessed through a XenApp 5 for Windows Server 2003 farm, VM Hosted Apps resources are hosted and delivered using XenDesktop technology. The XenDesktop 4 media should be used for VM Hosted Apps functionality. When creating a Desktop Group, on the Assignment Type screen, select Use Desktop Group for VM Hosted Apps. In addition, modify the application icon and place the application shortcut item in the SeamlessInitialProgram folder. Lastly, keep in mind that only one application can be accessed as a VM Hosted App based on this functionality.
Redundancy
and failover Citrix recommends always incorporating redundancy. For example, multiple Web Interface servers should be deployed, not just a single Web Interface server. In addition, where failover is incorporated into a XenApp environment, such as by means of Zone Preference and Failover, similar functionality should be incorporated into the XenDesktop environment, such as by means of Web Interface User Roaming configuration.
HDX MediaStream for Flash
This technology improves Flash responsiveness within web sites and requires that the physical Windows device have Internet Explorer and Adobe Flash 10 installed locally and LAN-like connectivity (30 ms or less by default). Accessing Internet Explorer-based sites by means of a XenApp hosted application through XenDesktop virtual desktops is a
“double hop”. In such a case HDX MediaStream for Flash will not function properly.
Hypervisor XenDesktop is server agnostic and is supported on Citrix XenServer™, Microsoft© Hyper-V™, or VMWare© vSphere™, platforms.
Operating System platform
Desktop Delivery Controller functionality, whether used to support VM Hosted Apps or XenDesktop 4, can only be installed on Windows Server 2003 SP2 or higher; it cannot be installed on the Windows Server 2008 platform. However, resources from XenApp 5 for Windows Server 2003, XenApp 5 for Windows Server 2008, and XenDesktop 4 farms can be consolidated by means of Web Interface.
Page 11
Installing XenDesktop Virtual Desktops
Where XenApp Infrastructure Exists
Assuming that your XenApp infrastructure is fully functional and that existing components will be reused to the extent possible, this section describes the installation steps. For more details regarding these installation steps, please see the XenDesktop product documentation available from the Citrix eDocs site. The steps below are based on XenApp 5 Feature Pack 2; if your environment is not at this level, please see the Technical Guide to Upgrading/Migrating to XenApp 5 Feature Pack 2.
Sequential Installation Order for XenDesktop Virtual Desktops: Easy as 1-2-3-4!
When adding XenDesktop to an existing XenApp 5 infrastructure, the following sequence should be followed:
1. Before installing XenDesktop:
• Ensure that Citrix Licensing Server is based on version 11.6.1 build 9020 and add XenDesktop licenses
• Ensure that Web Interface is based on version 5.2
• Designate a database instance on the SQL Server or Oracle database server for the XenDesktop data store
• Ensure that client devices are based on the Citrix Online plug-in version 11.2
• Designate an Active Directory OU for the Desktop Delivery Controller(s); optimally, this will be a sister OU of the XenApp servers OU if Citrix Profile management will be used
2. During installation of the XenDesktop Desktop Delivery Controller:
• If the XenDesktop Delivery Services and Presentation Server consoles will be administered on the Desktop Delivery Controller server, ensure that the Management Consoles option remains checked;
otherwise deselect
• To avoid installation of Web Interface, use the command line syntax setup.exe –nosites; do not simply deselect Web Interface within the installation interface
• Deselect Citrix License Server installation
• Designate a unique farm name during the installation; do not provide the same name as an existing XenApp farm
• Designate the XenDesktop edition purchased; do not select the XenApp edition in use
• Designate the SQL Server or Oracle database server that will house the XenDesktop data store
• When the Active Directory Configuration Wizard appears, designate the previously configured Active Directory OU
3. When creating virtual desktops:
Page 12
• Install the operating system and any desired applications, including the Citrix Online plug-in and Adobe Flash 10 if HDX Flash will be enabled
• Install Virtual Desktop Agent and ensure that the TCP port 8080 designation and Windows firewall changes do not conflict with internal security requirements
• Ensure that each virtual desktop is assigned a unique device name and IP address; Citrix Provisioning services automatically addresses this requirement
4. To configure and access XenDesktop:
• Within the XenDesktop Delivery Services Console, create desktop group(s) as appropriate
• Within Web Interface, add the XenDesktop farm as a server farm, and designate a Desktop Delivery Controller as a Citrix XML Service server
Based on the instructions provided above, your new environment will have these characteristics:
Adding Provisioning Services to Support XenDesktop
Assuming that Provisioning services has already been deployed to support XenApp, no additional infrastructure is required to support virtualized or blade PC desktops. However, because there will be an increase in the number of virtual images, additional storage space should be allocated.
Depending on your environment and network configuration, it is typically best to allocate a Provisioning services farm and associated database for each large data center where a XenDesktop farm will be deployed. As an example, Citrix internally has four sites where XenDesktop is deployed, and each site has its own XenDesktop farm, Provisioning services farm, and SQL Server database.
Page 13
Adding EdgeSight for Virtual Desktops
In order for EdgeSight to effectively support virtualized desktops, EdgeSight Agent database server functionality may be considered. The purpose of this additional server is to store data recorded on the virtual desktops during user sessions. By doing so, session data is retained even though the virtual desktop is deleted. Because each virtual desktop contributes to the size of the SQL Server database, additional storage space should be designated.
The EdgeSight agent uses a local data store to record the performance and usage information that it collects. In a XenDesktop deployment where there is a common image for the XenDesktop virtual images, that data store is lost each time image is restarted because the image reverts to its initial state. Accordingly, there needs to be a location for a persistent agent data store, which is facilitated by means of the EdgeSight Agent database server. The EdgeSight database server can be an extra virtual machine on each host that uses few resources such that it does not impact the performance of the real virtual machine images that are also running on the host. EdgeSight manages all of the brokering and communication. The only incremental costs would be the operating system licenses for the EdgeSight Agent database server virtual machine(s), which can be based on client operating systems such as Windows XP or Windows 7.
Based on incorporating EdgeSight for Virtual Desktops, your new environment will have these characteristics:
EdgeSight Server
Citrix License Server 11.6.1 Build 9020
XenServer Hosting Virtual Desktops
XenApp Farm XenDesktop DDC
SQL Server hosting XenApp and XenDesktop
Data Stores and EdgeSight database
Web Interface 5.2
Physical client device with Citrix Online
plug-in 11.2
EdgeSight Agent Database Server
Agent database
upload
EdgeSight For Virtual Desktop Agents
EdgeSight communications
EdgeSight for XenApp EdgeSight
for EndPoints
Page 14
Deployment Scenarios
Two sample scenarios are discussed below in order to provide more specific guidance as to how the implementation of XenDesktop should be undertaken. Of course, every environment is unique, so the generalities discussed within this section may or may not apply to your organization.
Scenario #1: Adding Virtual Desktops to Address New Call Center Users
The Telephone Company is a regional telecommunications provider that uses XenApp 5 for Windows Server 2008 to host several strategic applications. Aside from core XenApp 5, Service Monitoring (EdgeSight) is deployed to monitor the XenApp environment.
The CIO at the Telephone Company has reviewed the benefits of virtualized desktops and has decided to implement Windows 7 virtual desktops for a pilot group of 25 call center users. The call center group will not have access to the XenApp resources, and the XenApp users will not have access to the XenDesktop resources. However, the pilot environment should be configured so that future corporate users will have access to both XenApp and XenDesktop resources. As part of this transition, the necessary core infrastructure components will be upgraded as necessary, Service Monitoring (EdgeSight) functionality will be extended to the virtual desktops, and Provisioning services will be implemented to support both XenDesktop and XenApp.
After gathering business and technical requirements from the stakeholders, the Citrix administrator is now ready to move forward with the XenDesktop implementation. Thus, the status before and after is as follows:
Component
or Feature
Status Before Status After Changes
XenDesktop None One XenDesktop 4
farm hosting virtual desktops based in the main data center
Add XenDesktop farm based on XenServer
Active
Directory Domain.com
Citrix
XenApp
Domain.com
Citrix
XenApp
XenDesktop
Add XenDesktop OU as a sister OU to the XenApp servers because Citrix Profile
management is applied to the Citrix OU
Page 15
Component
or Feature
Status Before Status After Changes
License
Server Version 11.5 Version 11.6.1 build
9020 Upgrade and add
XenDesktop licenses Database
server Clustered SQL Server 2005 with databases instances for:
• XenApp Data Store
• Configuration Logging
• EdgeSight
Clustered SQL Server 2005 with databases instances for:
• XenApp Data Store
• Configuration Logging
• EdgeSight
• XenDesktop Data Store
• Provisioning services
Add XenDesktop and Provisioning services database instances
Page 16
Component
or Feature
Status Before Status After Changes
Management
consoles XenApp Access Management and Advanced Configuration consoles hosted on dedicated XenApp dedicated Zone Data Collector and Backup Zone Data Collector Web Interface console hosted on each Web Interface server License Management console hosted on Citrix License Server
XenApp Access Management and Advanced Configuration consoles hosted on dedicated XenApp dedicated Zone Data Collector and Backup Zone Data Collector Web Interface console hosted on each Web Interface server
License Management console hosted on Citrix License Server XenDesktop Delivery Services and
Presentation Server consoles hosted on Desktop Delivery Controllers
Adding XenDesktop management consoles to the Desktop Delivery Services
Controller, which will be
administered by a different
administrator
Web Interface XenApp Services site presented by Web Interface 5.0.1
XenApp Services site presented by Web Interface 5.2
Upgrade and add XenDesktop farm to server farm tab XenApp
applications Five applications available to most corporate users
Five applications available to most corporate users
None
Page 17
Component
or Feature
Status Before Status After Changes
Profile
management Terminal Services roaming profiles for XenApp users
Terminal Services roaming profiles for XenApp users Citrix Profile management for call center group based on adding ADM template to Citrix OU
Add Citrix Profile
management for call center group Implemented under Citrix OU because future users will have access to both XenApp and XenDesktop farm resources WAN Optimization Not used as all users
are located within one single site
Not used as all users are located within one single site
None
Service Monitoring (EdgeSight)
Version 5.2.1 enabled
for XenApp servers Version 5.2.1 enabled for XenApp servers and XenDesktop virtual desktops
Add Service Monitoring for Virtual Desktop agent to virtual desktop images Implement EdgeSight Agent database server to capture virtual desktop data where the persistence of data is required Provisioning
services Not used Enabled for XenApp servers and
XenDesktop virtual desktops
Install Provisioning services and create images Citrix Online
plug-in Version 11.0 Version 11.2 Upgrade
Single sign-on (Password Manager)
Not used Not used None
Page 18
Component
or Feature
Status Before Status After Changes
EasyCall
voice services Not used Not used None
Citrix
Receiver Not used Not used None
Page 19
Thus, the new environment will be implemented as follows:
Page 20
Scenario #2: Adding VM Hosted Apps on PC Blades to Support a Resource-
Intensive App
The Engineering Firm is a 100-person engineering design enterprise that uses XenApp 5 for Windows Server 2003 Feature Pack 2 to host computer-aided design (CAD) applications. The IT Director has found that a new resource- intensive application named Intensive App has severely impacted the number of users that can effectively use XenApp-based applications. Rather than add more XenApp servers to the farm, she has decided to transition Intensive App to XenApp VM Hosted Apps functionality based on PC blades.
Due to the sensitive nature of the CAD designs, engineers only have basic utilities installed locally on their laptop computers. Engineers currently access Intensive App by means of the StartÆPrograms menu on their laptop
computers, and the IT Director wants to make the transition to VM Hosted Apps transparent to the users. As part of this transition, the necessary core infrastructure components will be upgraded as necessary, Citrix Receiver and Branch Repeater will be implemented, and Provisioning services functionality will be extended to the PC blades.
After gathering business and technical requirements from the stakeholders, the Citrix administrator is now ready to move forward with the XenDesktop implementation. Thus, the status before and after is as follows:
Component
or Feature
Status Before Status After Changes
XenDesktop None One XenDesktop 4
farm based on PC blades
Add XenDesktop farm and configure Desktop Group using the VM Hosted Apps assignment type Active
Directory Domain.com
Citrix
XenApp
Domain.com
Citrix
XenApp
XenDesktop
Add XenDesktop OU as a sister OU to the XenApp servers
License Server Version 11.6.1 build
9020 Version 11.6.1 build
9020 None
Page 21
Component
or Feature
Status Before Status After Changes
Database
server SQL Server 2005 with databases instances for:
• XenApp Data Store
• Configuration Logging
• EdgeSight
• Provisioning services
SQL Server 2005 with databases instances for:
• XenApp Data Store
• Configuration Logging
• EdgeSight
• Provisioning services
• XenDesktop Data Store
Add XenDesktop database instance
Management
consoles XenApp Delivery Services and Advanced Configuration consoles hosted on a dedicated XenApp Zone Data Collector Web Interface console hosted on each Web Interface server
License Management console hosted on Citrix License Server
XenApp Delivery Services and Advanced Configuration consoles hosted on a dedicated XenApp Zone Data Collector
Web Interface console hosted on each Web Interface server License Management console hosted on Citrix License Server Consolidate
XenDesktop administrative consoles onto XenApp Zone Data Collector where feasible
Install XenDesktop Delivery
Services console on dedicated XenApp Zone Data Collector and create new MMC based on Citrix-related snap-ins Install XenDesktop Presentation Server console on XenDesktop Desktop Delivery Controller to administer Citrix policies and other
administration
Page 22
Component
or Feature
Status Before Status After Changes
Web Interface XenApp Services site presented by Web Interface 5.2
XenApp Services site presented by Web Interface 5.2
When
publishing the application, modify the application icon and place the application shortcut item in the SeamlessInitial Program folder XenApp
applications Five applications available to most corporate users
Five applications available to most corporate users
None; Intensive App presented in same manner but accessed as a VM Hosted App
Profile
management Mandatory profiles with folder
redirection
Mandatory profiles
with folder redirection None
WAN Optimization Branch Repeater appliance version 4.5.3 installed in headquarters and Mexico City office Registry modified on XenApp servers to enable acceleration of RC128 ICA
connections
Branch Repeater appliance version 5.5 installed in
headquarters and Mexico City and Buenos Aires offices Registry modified on XenApp servers to enable acceleration of RC128 ICA
connections
Upgrade Branch Repeater to version 5.5 or higher and add one Branch Repeater in Buenos Aires ICA Acceleration automatically enabled with XenDesktop 4
Service monitoring (EdgeSight)
Not used Not used None
Page 23
Component
or Feature
Status Before Status After Changes
Provisioning
services Enabled for XenApp
servers Enable for PC blades Add images and monitor storage requirements
Citrix Online
plug-in Version 11.0 Version 11.2 De-install plug- in and include as part of Citrix Merchandising Server
Single Sign-on (Password Manager)
Not used Not used None
EasyCall voice
services Not used Not used None
Citrix Receiver Not used Enable Citrix
Merchandising Server and deploy designated plug-ins
Install Citrix Receiver on client devices Install Citrix Merchandising Server and enable
deployment of Citrix Online plug-in and Dazzle plug-in
Page 24
Thus, the new environment will be implemented as follows:
hp bc2800 hp bc2800 hp bc2800 hp bc2800 hp bc2800 hp bc2800 hp bc2800 hp bc2800 hp bc2800 hp bc2800 hp bc2800 hp bc2800 hp bc2800 hp bc2800 hp bc2800 hp bc2800 hp bc2800 hp bc2800 hp bc2800 hp bc2800
HP BladeSystem PC Blade Enclosure
Citrix License Server 11.6.1 Build 9020
XenApp 5 for Windows
Server 2003 Farm SQL Server 2005
hosting Citrix databases:
- XenApp Data Store - Configuration Logging - Provisioning Services - XenDesktop Data Store Laptop with
Citrix Receiver
Provisioning Services 5.1 SP1
Dedicated Zone Data Collectors hosting - MMC comprising XenApp/XenDesktop Delivery Service Console
- Advanced Configuration
Console Web Interface
5.2
XenDesktop 4 DDCs hosting - Presentation Server Console Branch Repeater
About Citrix
Citrix Systems, Inc. (Nasdaq:CTXS) is the global leader and the most trusted name in application delivery infrastructure. More than 200,000 organizations worldwide rely on Citrix to deliver any application to users anywhere with the best performance, highest security and lowest cost. Citrix customers include 100% of the Fortune 100 companies and 98% of the Fortune Global 500, as well as hundreds of thousands of small businesses and prosumers. Citrix has approximately 6,200 channel and alliance partners in more than 100 countries. Annual revenue in 2006 was $1.1 billion.
©2009 Citrix Systems, Inc. All rights reserved. Citrix®, Citrix XenApp™, Citrix XenServer™ are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the United States Patent and Trademark Office and in other countries. Microsoft® and Windows® are registered trademarks of Microsoft Corporation in the United States and/or other countries. UNIX® is a registered trademark of The Open Group in the United States and other countries.
All other trademarks and registered trademarks are property of their respective owners.
Citrix Worldwide
Worldwide headquarters
Citrix Systems, Inc.
851 West Cypress Creek Road Fort Lauderdale, FL 33309 USA
T +1 800 393 1888 T +1 954 267 3000 Regional headquarters
Americas Citrix Silicon Valley 4988 Great America Parkway Santa Clara, CA 95054 USA
T +1 408 790 8000
Europe
Citrix Systems International GmbH Rheinweg 9
8200 Schaffhausen Switzerland T +41 52 635 7700
Asia Pacific
Citrix Systems Hong Kong Ltd.
Suite 3201, 32nd Floor One International Finance Centre 1 Harbour View Street
Central Hong Kong T +852 2100 5000
Citrix Online division 5385 Hollister Avenue Santa Barbara, CA 93111 USA
T +1 805 690 6400 www.citrix.com
