Technical Guide for

Upgrading/Migrating to
XenApp™ 6
Citrix released XenApp 6 for Windows Server 2008 R2, on
March 24, 2010.

This document provides a brief technical overview of new

XenApp 6 functionality to help you determine which features
are applicable to your environment. It primarily focuses on
easy-to-follow installation steps and will serve as a companion
technical guide for Citrix administrators and partners.

Author: Jo Harder, Citrix Worldwide Technical Readiness

Date Created: May 2010

www.citrix.com
Table of Contents

Introduction 3
Upgrade vs. Migration ................................................................. 3

XenApp Feature Set by Edition ....................................................... 4

Which Features Should Be Implemented? ........................................... 4

What’s Included with XenApp 6? 5

XenApp 6 Platinum Components and Features ..................................... 5

Upgrade/Migration Steps 7
Sequential Installation Order for Core XenApp 6 .................................. 7

Documentation ......................................................................... 7

Citrix License Server 11.6.1 Build 10007............................................ 8

XenApp 6 for Windows Server 2008 R2 .............................................. 9

Citrix Policy Administration .......................................................... 9

XenApp 6 Migration Tool (Beta) ..................................................... 10

Web Interface 5.3 ..................................................................... 13

Secure Gateway 3.2 .................................................................. 13

Citrix Merchandising Server 1.2/Receiver 1.2..................................... 14

VM Hosted Apps ....................................................................... 14

Profile Management 3.0 .............................................................. 15

SmartAuditor 1.3 ...................................................................... 16

Power and Capacity Management................................................... 17

HDX WAN Optimization ............................................................... 17

Application Streaming 6.0 ........................................................... 18

Load Testing Services 3.6.1.......................................................... 18

Provisioning Services 5.1 SP2 ........................................................ 19

Service Monitoring 5.3 (formerly EdgeSight) ...................................... 20

EasyCall Voice Services 3.0 .......................................................... 20

Single Sign-On 4.8 (formerly Password Manager) ................................. 21

Workflow Studio Orchestration 2.0.1 .............................................. 22
Page 2
Introduction
On March 24, 2010, Citrix released XenApp 6, which was purpose built expressly for the Windows Server 2008 R2
x64 platform. In addition to core XenApp, this release includes enhancements to numerous Platinum edition
component features. For the purposes of this document, XenApp Platinum edition is assumed; however, the
XenApp feature set is licensed based on specific editions, as well as the Enterprise and Platinum editions of
XenDesktop.

XenApp 6 includes a streamlined installation process and centralized management. Migration to this new XenApp
version is necessary because mixed farms and in-place upgrades from previous versions are not supported. However,
Citrix is providing the XenApp 6 Migration Tool to facilitate exporting Presentation Server 4.5/XenApp 5 farm
settings and importing these settings into the new XenApp 6 farm. The XenApp 6 Migration Tool is explained later
in this document.

Many of the XenApp Platinum features--including Web Interface, Service monitoring (EdgeSight), and Application
Streaming--can be upgraded, and details are discussed subsequently within this document.

This technical guide addresses the installation steps associated with the XenApp 6 Platinum feature set. Detailed
information regarding planning and installation is available through Citrix eDocs (http://www.citrix.com/edocs).

To facilitate the implementation of XenApp 6, this document contains the following sections:

 What’s Included with XenApp 6?

 Upgrade/Migration Steps

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 item over an existing version
 Migration: a clean, new installation of that feature or release item

Migrations are preferred from a technical standpoint.

This document will discuss each of the new features and the associated installation steps; however, in all cases, active
Subscription Advantage as of March 17, 2010, is required.

Page 3
XenApp Feature Set by Edition

XenApp features can only be implemented based on availability by edition. XenApp is offered based on four
editions, and feature set entitlement is based on the specific edition licensed. This document discusses new and
updated items incorporated into the Platinum feature set. For more information regarding the complete feature set,
please see the XenApp Features by Edition
(http://www.citrix.com/English/ps2/products/subfeature.asp?contentID=1689907) matrix.

In addition, XenApp is included with the Enterprise and Platinum editions of XenDesktop. For example, an
organization licensed for the XenDesktop Enterprise or Platinum edition may choose to present applications hosted
on XenApp through XenDesktop virtual desktops. For more information regarding the XenDesktop feature set,
please see the XenDesktop Features by Edition
(http://www.citrix.com/English/ps2/products/subfeature.asp?contentID=1685000) matrix.

Which Features Should Be Implemented?

Because there are numerous new features and related components that have been released as part of or in conjunction
with XenApp 6, administrators and architects should review the functionality of each one in order to determine those
which to implement.

To assist you with learning about XenApp 6 and the new feature set, Citrix offers evaluation options that can be
accessed at no charge from http://www.citrix.com/tryxenapp:

 A pre-configured virtual machine to evaluate XenApp in your own data center

 Download software and evaluation licenses to create your own XenApp environment

Once the appropriate features have been identified, use the steps or references from this guide to implement them.
It’s that easy!

Page 4
What’s Included with XenApp 6?
XenApp 6 includes not only a purpose-built version based on Windows Server 2008 R2, but also new components
and features. Many of the new components and features also support Windows Server 2008 R2.

Performance improvements for XenApp 6 include 15% or more users per server. Fully streamlined installation and a
unified management console are two new features that administrators will appreciate, as well as:

 HDX RealTime for Microsoft Office Communicator 2007 and softphone support, as well as CD quality audio
 HDX MediaStream for Flash with server-side media content fetching
 Enhanced color and monitor support, including DirectX/Direct3D hardware acceleration/32-bit graphics and
improved multi-monitor functionality
 Windows 7 smart card support

Please note that the Citrix Online plug-in 12.0 is required for the full array of HDX functionality.

XenApp 6 Platinum Components and Features

As part of the XenApp 6 release, the following components and features were also revised:

Feature New Functionality Sample Use Case

License Server Dashboard and administrative An administrator wishes to track the
11.6.1 Build functionality that provides detailed number of user licenses available during a
10007 status information peak period.
License Server License monitoring data available An administrator uses the license
Monitoring for all XenApp editions through monitoring functionality to determine
and Reporting Track Usage reports (EdgeSight) licensing compliance.
Application Supports isolation of Windows An administrator profiles and streams
Streaming 6.0 services into streaming profiles Microsoft Office 2010 to user desktops.
Web Interface Adds support for XenApp 6 and A user accesses hosted applications from a
5.3 Windows Server 2008 R2 XenApp 6 farm via a Web Interface site.
Power and Supports XenApp 6 for Windows An administrator configures Power and
Capacity Server 2008 R2 Capacity Management to shut down
Management XenApp 6 servers after business hours.
SmartAuditor Adds support for XenApp 6 for An administrator configures SmartAuditor
1.3 Windows Server 2008 R2, Windows 1.3 based on SQL Server 2008 to monitor
7, and SQL Server 2008 database sessions running on XenApp 6.
Profile Profiles streamed for faster session To address profile requirements for
Management startup XenApp and XenDesktop, an
3.0 administrator employs Citrix Profile
management.

Page 5
 Service Adds support for XenApp 6 for An administrator enables Service
Monitoring 5.3 Windows Server 2008 R2 monitoring for a new XenApp 6 farm
(formerly
EdgeSight)
Provisioning Adds support for Windows Server An administrator within an environment
Services 5.1 2008 R2 that is transitioning all servers to Windows
SP2 Server 2008 R2 incorporates Provisioning
services 5.1 SP2.
Single Sign-On Adds support for Windows 7, A user accesses XenApp 6 hosted
(formerly Windows Server 2008 R2, and x64- applications without entering additional
Password based computers passwords because Single sign-on has been
Manager) enabled.
Secure Adds support for Windows Server In an environment wherein Windows
Gateway 3.2 2008 R2 Server 2008 R2 is required, an
administrator deploys Secure Gateway 3.2.
Merchandising Supports 32- and 64-bit versions of An administrator enables a self-service
Server/ Windows 7, XP, Vista, Server 2003, enterprise “app store” for employees.
Receiver 1.2 and Server 2008, the 32- and 64-bit
for Mac and Intel versions of Mac OS X 10.5
Windows / (Leopard) and Mac OS X 10.6
Dazzle 1.1.1 (Snow Leopard), and App-V plug-in

Please note that this list focuses only on the major enhancements included with this release.

Page 6
Upgrade/Migration Steps
As with all upgrades or migrations, a thoroughly documented and tested design should be part of the project plan.
The design should incorporate input from all stakeholders, and a segregated lab environment should be used to
systematically test the planned implementation. For example, if the XenApp 6 Migration Tool is used to import
settings from the XenApp 5 farm, the farm settings should be verified within a lab environment before rolling into
Production.

Sequential Installation Order for Core XenApp 6

When migrating a XenApp farm, the following sequence should be followed:

1. Install or upgrade Citrix Licensing Server 11.6.1 Build 10007 (optional but strongly recommended)
a. Add licenses and/or verify that Subscription Advantage date is March 17, 2010, or later
2. If using SQL Server for the Data Store database, install and configure. SQL Server Express 2008 is installed
automatically if selected.
3. Install XenApp 6 on first server
a. If applicable, import settings from XenApp 5 farm using XenApp 6 Migration Tool
4. Install XenApp 6 on member servers
5. Install or upgrade Web Interface server(s)*
6. Install or upgrade other features/components
*Some upgrade situations warrant Web Interface installation earlier.

Documentation

For more detailed explanation regarding any of the installation steps presented, please see
http://support.citrix.com/proddocs/topic/xenapp/xenapp6-w2k8-wrapper.html.

Page 7
Citrix License Server 11.6.1 Build 10007

Citrix License Server 11.6.1 has had three iterations: Build 9019, Build 9020, and Build 10007, all of which can be used
to support XenApp 6. Citrix strongly recommends that the latest release, Build 10007, be used because it
incorporates a new dashboard and administrative functionality.

The latest Citrix License Server is not based on IIS or Java, thus an in-place upgrade of an existing Citrix License
Server has no new prerequisites. Prior to upgrading, ensure upgrade eligibility by confirming the Citrix License Server
version currently in use. To do so, access the following location in the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\LicenseServer\Install.

After installation, ensure that the built-in administrative user account “admin” (all lower case) is used for login. The
admin account, as well as other accounts created, are case sensitive.

Upgrade/Migration Steps for Citrix License Server 11.6.1 Build 10007

Upgrading from Citrix License Server Migrating to Citrix License Server 11.6.1
11.3 or higher to Citrix License Server Build 10007
11.6.1 Build 10007

1. Install CTX_Licensing.msi 1. On a Windows Server 2003, 2008, or 2008

2. Go to StartProgramsCitrix R2 server, ensure that .NET Framework 2.0
Management ConsoleLicense or higher is installed
Administration Console to open the 2. Install CTX_Licensing.msi
Dashboard and verify Subscription 3. Install license file(s)
Advantage date of March 17, 2010, or later

Page 8
XenApp 6 for Windows Server 2008 R2

In addition to a unified management console, XenApp 6 includes several technical changes:

 All XenApp 6 prerequisites are automatically installed during the installation process. As such, only the base Windows
Server 2008 R2 operating system must be installed on the server. Automatic reboots will occur during the XenApp
installation process.
 Data Store database can only be based on SQL Server 2005/2008, SQL Server Express 2008 or Oracle .
 Citrix policies and farm settings are configured and applied universally as Group Policy Objects (GPOs) that have
precedence over other local machine policies.

Please note that the IMA Data Store can house policies; the use of Active Directory GPOs is not mandatory.

XenApp 6 implementations must be based on clean Windows Server 2008 R2 operating system installations as Citrix
does not support operating system upgrades. Thus, there is no path for upgrading existing XenApp 5 servers, even if
based on Windows Server 2008 x64. In addition, a XenApp 6 farm can only encompass XenApp 6 servers; mixed
farms are not supported for XenApp 6.

Upgrade/Migration Steps for XenApp 6

for Windows Server 2008 R2

Upgrading to XenApp 6 from Migrating to XenApp 6

XenApp 5

No direct upgrade path exists; see XenApp 1. Install Windows Server 2008 R2.
6 Migration Tool below 2. Initiate the XenApp 6 installation via
autorun.exe; note that all prerequisites will
be installed automatically

Citrix Policy Administration

When configuring Citrix policies and farm settings, Citrix recommends the following order of preference based on
administrative rights:

Preference Policy Applies to When to Use

Configuration
Location

1 Group Policy All or subset of Admin has rights to modify Citrix resources
Management servers (as within respective Active Directory OUs and
Console configured) other group policy functionality such as
inheritance are required
2 Delivery Services All or subset of Admin has no rights to modify Citrix
Console servers (as resources within respective Active Directory
configured) OUs but has full administrative rights within

Page 9
 Delivery Services Console
3 Local Group Policies Local server Admin has no rights to modify Citrix
only; must resources within respective Active Directory
manually OUs nor full administrative rights within
propagate to Delivery Services Console
other servers

The mechanism used for configuring policies should be used consistently. For example, if a policy is applied through
the Group Policy Management Console while another administrator is configuring another policy through the
Delivery Services Console, unexpected issues may result. As such, care must be taken when using both the Group
Policy Management Console and Delivery Console to configure policies. Citrix also recommends enabling RSoP
(Resultant Set of Policies) logging mode and/or Configuration Logging to track administrative changes.

XenApp 6 Migration Tool

To initiate the transition to XenApp 6, administrators must initiate a new farm and thus have the following options:

 Create a new XenApp 6 farm and designate all settings manually

 Migrate settings from an existing XenApp 5 farm into a new XenApp 6 farm

When using the XenApp 6 Migration Tool, administrators are encouraged to review all settings to ensure that they are
desired in the new farm; automatically applying the same settings may not be optimal based on environmental changes
that have occurred since the XenApp 5 farm was installed. The Migration Tool provides options for excluding or
modifying setting prior to importation into the new farm.

The XenApp 6 Migration Tool can be used to export settings from the XenApp 5 farm and import into the new
XenApp 6 farm. Specifically, the following items are/are not transferred:

Settings Transferred Settings Not Transferred

 Applications  Zones
 Application and server folders  Printer management
 Load evaluators  Configuration Logging settings
 Policies  Health Monitoring and Recovery
 Server configuration  Deprecated settings, such as
 Farm configuration Application Isolation
 Administrator accounts

Note that the Zone Preference and Failover policy within XenApp 5 is converted to a load balancing policy in
XenApp 6. Previously, many customers implemented additional zones in order to configure failover, whereas
XenApp 6 addresses this more efficiently through Worker Groups. As such, zone settings are not transferred.

The originating farm from which settings are pulled can only be based on XenApp 5 for Windows Server 2003 HRP5
or XenApp 5 for Windows Server 2008. Some or all settings can then be transferred via the command line tool. If
Page 10
the existing farm is based on server or application folders, these settings can be exported so that they will be identified
as Worker Groups within the new farm. Additional command line entries are available to include, exclude, or modify
specific settings. The administrator must have full administrative rights within the XenApp 6 farm.

Prior to initiating the migration of settings, Worker Groups should be designated so that server and application silos
can be assigned appropriately. This provides administrators with additional flexibility and enables a significant
number of new servers to be added to the new XenApp 6 farm at once using a tool such as Citrix Provisioning
services.

To transfer all farm settings into a single worker group via the XenApp 6 Migration Tool, the administrator should do
the following:

Steps to Transfer All Farm Settings via the XenApp 6 Migration Tool
1. On a XenApp 6 server, install the XenApp 6 Migration Tool
(Citrix.XenApp.Migration.Install_x64.msi), including the option to set the PowerShell execution
policy to AllSigned
2. On the XenApp 6 server, access the tool via the StartProgramsCitrixXenApp Migration
Tool menu or open PowerShell and execute:
a. To import the Migration Tool (necessary if accessed directly via PowerShell): Import-
Module citrix.xenapp.migration
b. To enable the unsigned scripts to run (necessary if PowerShell execution policy not set to
AllSigned): Set-ExecutionPolicy RemoteSigned
c. To designate the XenApp 5 server name: Set-XAMigrationOption -RemoteServerName
[servername] -Passthru
d. To map a server in the XenApp 5 farm to a worker group in the XenApp 6 farm:
Add-XAServerMapping [servername] [worker group name]
e. To transfer all settings: Start-XAMigration
3. Perform post-migration steps

The above instructions are only applicable where all servers in the legacy farm run all applications and transferring all
settings to the new farm is desired. Please see http://www.citrix.com/tv/#videos/2510 for a demonstration of the
above.

The XenApp 6 Migration Tool allows administrators to import server silo settings directly into pre-designated worker
groups, transfer a subset of settings, modify settings, and much more. Please see the complete documentation for
more details: http://support.citrix.com/proddocs/topic/xenapp6-w2k8/ps-migrate-xa6-wrapper.html

Post-migration steps include:

 Attaching load evaluators to servers

 Associating applications folders with worker groups
 Associating servers or OUs with worker groups
 Assigning zones
 Configuring printer settings
 Initiating Configuration Logging within the new farm
 Configuring Health Monitoring settings

Page 11
With exception of load evaluators and zones, post-migration steps are only required once per farm. Load evaluators
and zone assignments are not based on Worker Groups and are required when new servers are added to a XenApp 6
farm.

Page 12
Web Interface 5.3

Web Interface 5.3 adds support for XenApp 6 farms and Windows Server 2008 R2. As in the past, Web Interface can
be used to consolidate XenApp applications, XenDesktop virtual desktops, and published content from multiple
Citrix farms. In addition, Web Interface can facilitate the transition to XenApp 6 by hiding duplicate applications
with identical names and folder locations; thus, the transition to XenApp 6 can be seamless to users. To do so,
modify the WebInterface.conf file as follows:

 SupressDuplicateResources=On
 Farm<N>Groups=<domain>\<Group1>;<domain>\<Group2>

Please note that within Web Interface 5.1 and earlier, the \Clients folder structure differed. When upgrading from
version 5.1 and earlier, you must adapt to the new \Clients folder structure in order to continue to install client
software by means of Web Interface.

Upgrade/Migration Steps for Web Interface 5.3 on IIS

Upgrading from Web Interface 4.5 or Migrating to Web Interface 5.3

higher to Web Interface 5.3

1. Remove any centrally configured sites 1. Install Windows Server 2003 SP2, Windows
2. Install Web Interface 5.3 Server 2008 SP2, or Windows Server 2008
R2
a. Windows Server 2003 requires IIS6
b. Windows Server 2008 R1 and R2
require Web Server (IIS) role, including
IIS6 Management Compatibility
2. Install the following:
a. .NET Framework 3.5 SP1
b. Visual J#.NET 2.0 Second Edition
c. ASP.NET 2.0
3. Install Web Interface 5.3

Secure Gateway 3.2

Secure Gateway 3.2 adds support for the Windows Server 2008 R2 platform. It includes no new functionality.

Page 13
Citrix Merchandising Server 1.2/Receiver 1.2

Citrix Merchandising Server 1.2 Admin Console enhancements, as well as several new plug-ins, such as App-V.
Receiver for Windows 1.2 is now available in eight languages, and Receiver for Macintosh 1.2 addresses OSX-based
devices. Both Merchandising Server and Citrix Receiver should be based on version 1.2.

Dazzle can optionally be used to present users with access to a resource storefront so that they can pick and choose
applications needed. Dazzle 1.1.1 requires Merchandising Server 1.2.

Upgrade/Migration Steps for Citrix Merchandising Server 1.2

Upgrading from Citrix Merchandising Migrating to Citrix Merchandising

Server 1.0 or higher to Citrix Server 1.2
Merchandising Server 1.2

1. Download and save Merchandising Server 1. Download and import Merchandising Server
1.2 virtual machine RPM file 1.2 virtual machine into your XenServer or
2. Open Merchandising Server console and VMware environment
access ConfigurationsUpgrade Server and 2. Load new plug-ins through Citrix Update
point to the saved location Service
3. Load new plug-ins through Citrix Update 3. Configure Merchandising Server deliveries
Service 4. Deploy Receiver on client devices via your
4. Modify Merchandising Server deliveries as SMS system or download page
appropriate; Receiver and plug-ins upgrade
automatically on client devices

VM Hosted Apps

VM Hosted Apps enables an application to be hosted and delivered from centralized Windows XP, Vista, or
Windows 7 virtual desktops or workstations and is a compliment to traditional XenApp Terminal Server-based
application delivery. It uses XenDesktop 4 technology to host a single application. With the exception of support for
XenApp 6 for Windows Server 2008 R2, the functionality of VM Hosted Apps has not changed in this release.

Page 14
Profile Management 3.0

Profile management 3.0 adds support for Windows Server 2008 R2 and streamed profiles. This means that the user
profile is streamed to the computer, and the computer is able to process the logon with only a minimal portion of the
profile loaded. Hence, user sessions initiate faster. It also synchronizes the profile during the session so the logoff
process is faster.

While it is technically possible to update the existing Profile management ADM template, there is the risk that a minor
change will be overlooked. The new ADM template has several new settings, and thus Citrix recommends installing
the new Profile management ADM template in a new GPO and transitioning the settings within the previously used
Profile management ADM template to the new GPO prior to being deleted.

Upgrade/Migration Steps for Profile Management 3.0

Upgrading from Profile Management Migrating to Profile Management 3.0

2.x to Profile Management 3.0

1. On each managed computer, install the 1. On each managed computer, install the
Profile Management MSI: Profile Management MSI:
a. On x86-based systems, install a. On x86-based systems, install
profilemgt3.0.0_x86.msi profilemgt3.0.0_x86.msi
b. On x64-based systems, install b. On x64-based systems, install
profilemgt3.0.0_x64.msi profilemgt3.0.0_x64.msi
2. Create a new Active Directory GPO and 2. In a new or existing Active Directory GPO,
import the ctxprofile3.0.0 adm template import the ctxprofile3.0.0.adm template
3. Compare settings in the previously used 3. Configure GPO policy rules
GPO and copy and/or modify settings in
the new GPO
4. Replace assignment of the old GPO with the
new GPO and delete the old GPO

Page 15
SmartAuditor 1.3

SmartAuditor 1.3 provides support for XenApp 6 for Windows Server 2008 R2 farms, as well as Windows Server
2008 R2 for server-side components. In addition, SmartAuditor Policy Console and Player are now supported on
Windows 7.

Please note that the instructions below are based on installing all administration components on a single server.
Commonly, the SQL Server database requirement is addressed on a distinct server, which may be based on Windows
Server 2008 R2, Windows Server 2003 SP2, or Windows 2000 Server SP4.

Upgrade/Migration Steps for SmartAuditor 1.3

Upgrading from SmartAuditor 1.x to 1.3 Migrating to SmartAuditor 1.3

1. There is no upgrade path 1. To install all administration components on

a single Windows Server 2008 R2 server,
install the following:
a. SQL Server 2005 SP2 or SQL Server
2008
b. .NET Framework 3.5
c. Microsoft Message Queuing (MSMQ)
with Active Directory integration
disabled and HTTP support enabled
d. IIS6 Metabase Compatibility
e. SmartAuditor from the XenApp 6
media autorun
2. On each XenApp 6 server, install:
a. MSMQ with Active Directory
integration disabled and HTTP support
enabled
b. SmartAuditor Agent from the XenApp
6 media autorun
3. On the device to be used as the
SmartAuditor Player, install:
a. .NET Framework 3.5
b. SmartAuditor Player from the XenApp
6 media autorun

Page 16
Power and Capacity Management

Power and capacity management provides an effective power management solution for XenApp servers by
automatically turning on and off servers based on a pre-defined configuration, thus reducing energy consumption.

When installing Power and capacity management, Citrix recommends that you do not install the database or
concentrator on a XenApp server as the functionality of Power and capacity management may shut down those
servers. Do not create the database manually because it will be automatically created during the Power and capacity
management database installation. In addition, .NET Framework 3.5 is required prior to installing any of the
components.

Upgrade/Migration Steps for Power and Capacity Management

Upgrading to Power and Capacity Migrating to Power and Capacity

Management Management

Not applicable 1. Install or make available a SQL Server or

SQL Server Express database; SQL
Reporting is optional but recommended
a. .NET Framework 3.5 required
2. On the same or two distinct servers, install
Concentrator and the Management Console
a. .NET Framework 3.5 required
b. On the console, MMC 3.0 or higher
required
3. Install the Power and capacity agent on each
XenApp server
4. Configure session capacity and define a
schedule before enabling power control
and/or load consolidation

HDX WAN Optimization

HDX WAN Optimization, previously known as ICA Acceleration, is incorporated within XenApp 6 for Windows
Server 2008 R2. No changes are required from the XenApp server side to enable ICA acceleration with Branch
Repeater. WAN Optimization requires Branch Repeater, whether based on a virtual machine or physical appliance.

Page 17
Application Streaming 6.0

Application Streaming 6.0 adds support for XenApp 6 for Windows Server 2008 R2 and isolation of Windows
services. In particular, isolation of Windows services is an important feature because it allows administrators to stream
applications such as Office 2010. When profiling applications that contain Windows services, it is necessary to
designate trusted servers for streamed services (see http://support.citrix.com/proddocs/index.jsp?topic=/xenapp-
application-streaming-edocs-v6-0/ps-stream-profile-trust-servers.html).

Rather than upgrading the Citrix Streaming Profiler, Citrix recommends migrating to the new version. Because the
Profiler computer should be based on the operating system most commonly used for profiled applications, a clean
installation of Windows Server 2008 R2 is recommended for applications to be streamed to XenApp 6 servers.

The Streaming Profiler 6.0 should be used in conjunction with the Offline plug-in 6.0, and the Citrix Offline plug-in
can be distributed by means of Citrix Receiver.

Upgrade/Migration Steps for Application Streaming 6.0

Upgrading from Application Streaming Migrating to Application Streaming 6.0

5.0 to Application Streaming 6.0

1. Remove any previous version of the Citrix 1. Install Windows operating similar to target
Streaming Profiler. device
2. Install CitrixStreamingProfiler.exe on the 2. Install the Application Streaming Profiler 6.0
Profiler computer
3. To upgrade a profile, open an existing
profile package, make a minor change, and
save

Load Testing Services 3.6.1

Load testing services, formerly known as EdgeSight for Load Testing, now includes support for Japanese, German,
French, Spanish and Simplified Chinese. It is an effective tool for estimating XenApp user loads and resource
requirements based on physical or virtual servers. There is no limit to the XenApp scalability testing that can be done
with the Load testing feature.

Upgrade/Migration Steps for Load Testing Services 3.6.1

Upgrading from Load Testing Services Migrating to Load Testing Services 3.6.1
3.x to Load Testing Services 3.6.1

1. Back up any existing scripts 1. Install EdgeSight for Load Testing.msi on

2. Install EdgeSight for Load Testing.msi on the server to be designated the controller
the server to be designated the controller 2. Install EdgeSight WI Support.msi on each
3. Install EdgeSight WI Support.msi on each Web Interface server (optional)
Web Interface server (optional)
Page 18
Provisioning Services 5.1 SP2

Provisioning Services enables XenApp workloads to be streamed on demand to physical or virtual machines. Service
Pack 2 release adds support for Windows Server 2008 R2, as well as minor updates.

Upgrade/Migration Steps for Provisioning Services 5.1 SP2

Upgrading from Provisioning Services Migrating to Provisioning Services 5.1

5.0 or higher to Provisioning Services SP2
5.1 SP2

1. Backup the existing Provisioning Services 1. On Windows Server 2003 SP2 or higher,
database Windows Server 2008 or Windows Server
2. Uninstall Provisioning Services and reboot 2008 R2, install Provisioning Services 5.1
the server SP2, which includes:
a. Provisioning Services installation wizard
3. Install Provisioning Services 5.1 SP2 to
upgrade the existing installation (select farm b. Provisioning Services console wizard
already configured) 2. Utilize an existing Microsoft SQL Server
4. On the XenApp servers, install the 2005 or 2008 (or Express) instance or create
Provisioning Services target device software: one
3. Configure Provisioning Services
 Automatic upgrade (recommended):
run the Provisioning Services Upgrade 4. On the XenApp server, install the
Wizard, which includes: Provisioning Services target device software,
which includes the target device installation
a. Provisioning Services Upgrade
wizard
Manager
5. Run XenApp Server Configuration tool and
b. UpgradeConfig.exe
rejoin the XenApp farm
 Manual upgrade: uninstall target device 6. Build vDisk using XenConvert tool
Provisioning Services software, reboot
7. Shut down server and move disk back into
the target device, and install
standard image mode
Provisioning Services 5.1 SP2 target
device software
5. Boot into private mode of newly updated
vDisk and run XenApp Server Configuration
tool to rejoin the XenApp farm
6. Shut down server and move disk back into
standard image mode
.

Page 19
Service Monitoring 5.3 (formerly EdgeSight)

In addition to new report functionality, Service monitoring 5.3 incorporates the EdgeSight Agent 5.3 for XenApp 6.

In addition, Citrix License Server monitoring and reporting has been incorporated in this release and is available for all
Citrix products. This feature does not require an agent because the license servers are polled. However, the
instructions below are based on the full Service monitoring capabilities offered with Platinum licensing.

The instructions for upgrading or migrating the server-side components to Service monitoring (EdgeSight 5.3) are the
same whether the installation is based on XenApp Platinum or XenApp Enterprise licensing. As with the previous
versions, when installing the agent on the XenApp servers, designate Advanced functionality (Service monitoring) for
Platinum licensing and Basic functionality (Resource Manager) for Enterprise licensing.

Upgrade/Migration Steps for EdgeSight 5.3

Upgrading from EdgeSight 5.x to Migrating to EdgeSight 5.3

EdgeSight 5.3

1. Backup the existing EdgeSight database 1. Install Windows Server 2003 SP1 or higher
a. If SQL Server 2000, must upgrade or Windows Server 2008 (including IIS 6 or
to SQL Server 2005 or 2008 higher, MSMQ, and .NET Framework 3.5
SP1), SQL Server 2005 or 2008 (must install
2. Install EdgeSight 5.3 on the existing
Database Services, Reporting Services, and
EdgeSight 5.x console server
Workstation components), and EdgeSight
3. Install the EdgeSight 5.3 agent on each 5.3
XenApp 6 server and reboot
2. Install the EdgeSight agent on each XenApp
server and reboot

EasyCall Voice Services 3.0

EasyCall voice services is a virtual server that integrates with your in-house telephony system and Active Directory. It
now incorporates call forwarding, a secondary conference access number, and a Macintosh plug-in.

Upgrade/Migration Steps for EasyCall Voice Services 3.0

Upgrading from EasyCall Voice Migrating to EasyCall Voice Services 3.0

Services 2.2 (virtual appliance) to
EasyCall Voice Services 3.0

1. Download the EasyCall 3.0 virtual appliance 1. Download the EasyCall 3.0 virtual appliance
upgrade image from MyCitrix and install from MyCitrix and install onto a XenServer
onto a XenServer host host
2. Restart the EasyCall appliance 2. Connect to your in house phone systems
3. Install or upgrade client devices to the 3. Configure integration with Active Directory
EasyCall 3.0 plug-in 4. Install or upgrade client devices to the
EasyCall 3.0 plug-in

Page 20
Single Sign-On 4.8 (formerly Password Manager)

Single sign-on 4.8, formerly known as Password Manager, now includes support for Windows 7, Windows Server
2008 R2, and x64-based computers. In addition, improved web page definition criteria and AES encryption are
offered.

Please note that the Application Definition Tool and central store media should be accessed from the XenApp 6
media. From the XenApp autorun, select Manually install componentsServer componentsMiscellaneousSingle
sign-on.

As with previous versions, the Single sign-on service and Single sign-on plug-in should not be installed on the same
computer, and Single sign-on should not be installed on a domain controller.

Upgrade/Migration Steps for Single Sign-On 4.8

Upgrading from Single Sign- Migrating to Single Sign-On 4.8

On/Password Manager 4.6 to Single
Sign-On 4.8

1. Upgrade the Single sign-on Service (Citrix 1. Create the central store in Active Directory
Password Manager Service.msi) or NTFS file share
2. Upgrade the Single sign-on component 2. Install the Single sign-on component within
within the Delivery Services Console the Delivery Services Console
(ASC_PasswordManager.msi) (ASC_PasswordManager.msi)
3. If used, upgrade the Application Definition 3. Install the Single sign-on Service (Citrix
Tool Password Manager Service.msi)
4. Upgrade the central store 4. Install the Application Definition Tool
5. Upgrade the Single sign-on plug-in on user 5. Install the Single sign-on plug-in on user
computers and/or XenApp servers computers and/or XenApp servers

Page 21
Workflow Studio Orchestration 2.0.1

Workflow Studio orchestration provides a rich interface for designing Citrix Delivery Center workflows. Release 2.0.1
includes new activity libraries for XenDesktop and Provisioning Server.

When upgrading Workflow Studio, the workflows stored in the database and workflow job history data in the user
profile are not removed as part of the uninstall process. Thus, no data is lost when following the upgrade steps
defined below.

Upgrade/Migration Steps for Workflow Studio 2.0

Upgrading from Workflow Studio 1.0 to Migrating to Workflow Studio 2.0.1

Workflow Studio 2.0.1

1. Backup the existing Workflow Studio 1. Install or make available SQL Server 2005
database database instance
2. Uninstall Workflow Studio 1.0 2. Install the following on the Workflow Studio
3. Ensure that the following are installed on the designer console and runtime servers (if
Workflow Studio server: segregated):
a. .NET Framework 3.5 SP1 a. .NET Framework 3.5 SP1
b. PowerShell 1.0 b. PowerShell 1.0
c. Microsoft Authorization Manager c. Microsoft Authorization Manager
4. Install the Workflow Studio 2.0.1 designer 3. Install designer console and Workflow
console and runtime; select the option to Studio runtime on same or different server
upgrade when the database is detected 4. Install Workflow Studio remote runtime on
5. Upgrade Workflow Studio 2.0.1 remote at least one XenApp server (usually Zone
runtime on at least one XenApp server Data Collector)
(usually Zone Data Collector)

Page 22
 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

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.