Upgrade

2013-06-28 20:44:52 UTC 2013 Citrix Systems, Inc. All rights reserved. Terms of Use | Trademarks | Privacy Statement

Contents

Upgrade ......................................................................................................... XenDesktop 5 to XenDesktop 7 upgrade ...................................................... Upgrade components ............................................................................

3 8 12

Upgrade XenDesktop 5 to XenDesktop 7

Before you upgrade

Before you upgrade a XenDesktop 5 Site, familiarize yourself with the new concepts and components that require upgrading and their versions, and the sequence for a successful upgrade. New concepts and features Compared to previous XenDesktop and XenApp versions, XenDesktop 7 has many new features and introduces new concepts.

For new XenDesktop 7 concepts, terminology, and system requirements, see What's new in XenDesktop 7 and Information for administrators of previous versions of XenDesktop. For XenApp administrator information, see Important information for XenApp administrators.

Manage multiple versions of XenApp and XenDesktop

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 with 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.

Upgrade Use StoreFront to aggregate applications and desktops from the different versions of XenApp and XenDesktop. For details, see the Storefront documentation. XenDesktop Express Edition You cannot upgrade from the XenDesktop Express Edition. You must obtain and install a license for VDI, Enterprise, or Platinum edition before upgrading.

Upgrade components
These components require upgrade:

License server and licenses Virtual Desktop Agents (VDAs) for Desktop OS Machines (Windows desktop) that upgrade to XenDesktop 7 Virtual Delivery Agents Delivery Controllers and other infrastructure components, such as Director Existing database

Important: Make sure you back up your database before performing any upgrade procedures.

VDAs
You can upgrade these VDA versions to XenDesktop 7 Virtual Delivery Agents:

5.0 Service Pack 1 5.5 5.6 5.6 Feature Pack 1 (including Remote PC Access VDAs)

The installer upgrades all agents and existing MSIs (Windows installer packages) on the existing VDA. Unlike previous VDA releases, you can only upgrade VDAs through the installer. You cannot upgrade to XenDesktop 7 using MSIs. Note: Microsoft Windows Vista is not supported by Director or by Remote PC Access. Note: Unsupported features for VDAs running Windows 7 with 5.6 Feature Pack 1 VDAs running Windows 7 with 5.6 Feature Pack 1 do not support the following features:

Configuration of App-V applications from Studio. Configuration of Receiver Storefront addresses from Studio.

Upgrade

Automatic support for Microsoft Windows KMS licensing when using Machine Creation Services (MCS). KMS licensing is supported using the procedure documented in http://support.citrix.com/article/CTX128580. Full information in Director:

Logon times and logon end events impacting the logon duration times in Dashboard, Trends, and User Detail views. Logon duration breakdown details for HDX connection time, authentication time, profile load duration, GPO load duration, logon script duration, and interactive session establishment duration. Some categories of Machine and Connection failures states.

Activity Manager in Help Desk and User Details views. VDAs installed on Windows XP or Windows Vista

Some XenDesktop 7 features are not supported on Windows XP or Windows Vista. If the installer detects a VDA running on a Windows XP or Windows Vista machine, it launches a different installer that updates to the latest VDA version that is supported on Windows XP or Windows Vista. Although these machines and their Machine Catalogs and Delivery Groups cannot use all XenDesktop 7 features, they can run in the XenDesktop 7 Site. Unsupported features for VDAs installed on Windows XP or Windows Vista VDAs running Windows XP or Windows Vista do not support the following features:

Configuration of App-V applications from Studio. Configuration of Receiver Storefront addresses from Studio. Automatic support for Microsoft Windows KMS licensing when using Machine Creation Services (MCS). KMS licensing is supported using the procedure documented in http://support.citrix.com/article/CTX128580. Full information in Director:

Logon times and logon end events impacting the logon duration times in Dashboard, Trends, and User Detail views. Logon duration breakdown details for HDX connection time, authentication time, profile load duration, GPO load duration, logon script duration, and interactive session establishment duration. Some categories of Machine and Connection failures states. Activity Manager in Help Desk and User Details views.

Controllers
You can upgrade the following Controller versions:

5.0

Upgrade

5.0 Service Pack 1 5.5 5.6 5.6 Feature Pack 1

Director
You can upgrade the following Director versions:

1.0 1.1 2.0 2.1

Database
After manually backing up your Site database, you upgrade the Database from an upgraded Delivery Controller. This process updates the schema and migrates data. Studio also performs additional data migration steps for the services.

Other components
The installer also upgrades the following components:

Personal vDisk (PVD) Receiver Note the following about Receiver upgrades:

If Receiver for Windows (Receiver.exe) resides on a machine, it is upgraded to Receiver for Windows 4.0

If Receiver for Windows Enterprise (CitrixReceiverEnterprise.exe) resides on a machine, it is upgraded to Receiver for Windows Enterprise 3.4 Components that require separate upgrade

You need to upgrade the following components outside of the in-place upgrade process:

Provisioning Services (PVS)

Upgrade the PVS server using the PVS server rolling upgrade Upgrade the PVS client using PVS vDisk versioning

Important: If you intend to run XenDesktop 7 and XenDesktop 5.6 sites simultaneously, do not upgrade to Provisioning Services 7. 6

Upgrade

System Center Virtual Machine Manager (SCVMM) XenDesktop 7 supports SCVMM 2012 and SCVMM 2012 SP1, while XenDesktop 5.x supports SCVMM 2008 R2 SP1. Upgrade in the following sequence so that XenDesktop can continue to operate without any downtime.

All XenDesktop Controllers to XenDesktop 5.6 FP1 SCVMM server to SCVMM 2012 XenDesktop to 7

Upgrade SCVMM server from 2012 to 2012 SP1 (optional) For external Web Interface servers, configure StoreFront to provide the desktops formerly provided through Web Interface. For information about installing and configuring StoreFront, seeInstall and set up Storefront.

After upgrading all components, you can optionally use Studio to upgrade Machine Catalogs and Delivery Groups that included machines running earlier VDA versions or Windows XP and Windows Vista operating systems. For detailed information, see Upgrade a machine catalog and Upgrade a Delivery Group.

Upgrade sequence
Citrix recommends that you upgrade components in the following sequence: 1. License server and license files. 2. Provisioning services (PVS) servers and PVS clients. 3. VDA software in your desktops and images. 4. One half of the existing Controllers. Note: By leaving half the Controllers active, users can still access the site. The upgrade servers cannot process requests until the entire site has been upgraded, however. 5. Studio if installed separately from the Controller. 6. Database. 7. Remaining Controllers. See Upgrade components for specific upgrade instructions.

XenDesktop 5 to XenDesktop 7 upgrade

Upgrade considerations

Existing Sites

You must use the XenDesktop 7 upgrade procedure (known as an in-place upgrade). You cannot import or migrate data from a XenDesktop 5 or later Site to a XenDesktop 7 Site. Although parallel sites (XenDesktop 5 and XenDesktop 7) are allowed, you cannot manage a XenDesktop 5.x Site with XenDesktop 7 Studio. Also, you cannot install XenDesktop 7 Studio on the same machine as a 5.x Desktop Studio, unless you intend to upgrade the 5.x site to XenDesktop 7. That is, you cannot run side-by-side Studio installations. Do not upgrade a stand-alone Desktop Studio to XenDesktop 7 Studio if you are not ready to use XenDesktop 7.

You cannot upgrade Desktop Studio Express Edition. You must obtain and install a license for VDI, Enterprise, or Platinum edition before upgrading. Delivery Controllers For Sites with one Controller, the Site is inoperable during the upgrade. For Sites with more than one Controller, the Site can continue to operate during the upgrade. The upgrade only causes a brief interruption in establishing new client connections during the final database upgrade steps. There may also be times when the Site has reduced capacity because fewer Controllers are available.

VDAs You cannot upgrade Virtual Desktop Agents running on Windows XP or Windows Vista to version 7 Virtual Delivery Agents. You must upgrade these VDAs to the Windows XP or Windows Vista version provided by the installer, or upgrade them to Version 5.6 Feature Pack 1. Provisioning Services (PVS) Before upgrading a Site, upgrade any PVS servers that are installed on management machines in the environment. See Upgrading Provisioning Servers.

The following figure shows the high-level processes involved in the upgrade.

XenDesktop 5 to XenDesktop 7 upgrade

High level upgrade steps The high level steps displayed in the previous figure are performed as follows. 1. Upgrade the License Server and associated license files to XenDesktop 7 level.

If there is a separate License Server, upgrade that server first.

If the License Server resides on a Controller, it is upgraded along with the other services. 2. Back up the Controller database.

3. Optionally back up templates and upgrade Hypervisor. 4. Upgrade PvS servers and agents. 5. Upgrade Virtual Desktop Agents (XenDesktop 5.x VDAs). You can upgrade VDAs before or after the Delivery Controllers, but Citrix recommends that you upgrade them before upgrading the Delivery Controllers if possible. This lets you quickly enable new XenDesktop 7 features when the upgrade is complete.

XenDesktop 5 to XenDesktop 7 upgrade 6. Upgrade half (or some) Controllers. Selecting this option also upgrades other core components.

These Controllers are unusable for the existing XenDesktop 5.x Site, and can no longer register machines. Machines that were registered with these Delivery Controllers register with the available Delivery Controllers.

Installer validates that the License Server is upgraded, and issues a warning if the License Server is not upgraded. 7. Upgrade a management machine with Studio, or use Studio on one of the upgraded Controllers.

8. Upgrade the Database using Studio. Important: Citrix strongly recommends that you manually back up the Site, so that you can restore it if any issues are discovered. Use the XenDesktop 7 Studio to upgrade the old database (You must use Studio from one of the upgraded Controllers, not from a XenDesktop 5.x Controller). Studio prompts you to perform a backup and make sure that the License Server is upgraded. If you do not have database administrator rights, select Manual Upgrade to use the separate manual database scripts provided for privileged database operations. See Upgrade components for detailed instructions. While services are disabled, Controllers cannot broker any new connections for your Site, so ideally you should minimize this down time window. The Delivery Controllers are re-enabled after this step completes. The services need to be registered with the Delivery Controller. After updating the database schema, Studio performs final data migration steps for Delivery Controller Services. When the process completes:

Studio runs environment and configuration tests and generates an HTML report for the upgrade procedure. If these tests fail, you can restore the Database backup and then use the original database. After resolving the root cause of those issues, run the upgrade process again.

Upgraded Delivery Controllers now handle machine registration. 9. Upgrade the remaining Delivery Controllers (and Director) and management machines to complete the upgrade.

10. Register the remaining Controllers as described in Upgrade the remaining Delivery Controllers. After completing the XenDesktop upgrade, upgrade machine catalogs as described in Upgrade a machine catalog and Delivery Groups as described in Upgrade a Delivery Group.

10

XenDesktop 5 to XenDesktop 7 upgrade

Post upgrade processes

After the upgrade and data migration is complete, Studio runs environment and configuration tests to ensure that the Site is in functional order.

11

Upgrade components
When you run the installer (AutoSelect), the wizard checks whether certain Site components (such as Delivery Controllers and VDAs), need to be upgraded. If you opt not to upgrade some components during this process, when you run Studio, it performs a component check and notifies you when components need to be upgraded. You cannot proceed to manage your Site until you upgrade for these components. Depending on your Site, the procedures that you perform and the order in which you perform these procedures may vary. Important: Back up your Database before performing any upgrade procedures.

Upgrade the License Server

Before upgrading the License Server, make sure the Subscription Advantage date for license files that is compatible with a supported edition of XenDesktop. 1. Log on to the server using a local administrator account and run the installer by inserting the media or mounting the ISO drive for this release, and double-clicking AutoSelect. 2. On the Welcome page, click Start. The wizard detects what components need to be upgraded and displays the Upgrade options page, activating the components you can upgrade. 3. Accept the license agreement. 4. If the wizard detects an incompatible license server or license files, you are prompted to upgrade that license component. Upgrade the component and then run the installer again, as described in Upgrade core components.

Upgrade core components

The installer automatically upgrades core components such as Delivery Controllers , Studio, and Director if they were previously installed. 1. Log on to the server using a local administrator account and run the installer by inserting the media or mounting the ISO drive for this release, and double-clicking AutoSelect. 2. On the Welcome page, click Start. The wizard detects what components need to be upgraded and displays the Upgrade options page, activating the components you can upgrade. 3. Click Delivery Controller.

12

Upgrade components Note: If the program detects the XenDesktop Express edition, you are prompted to obtain and install a license for a supported edition. You cannot continue the upgrade until you obtain and install a license for VDI, Enterprise, or Platinum edition before upgrading. 4. Accept the license agreement. 5. Review the upgrade steps, click I'm ready to continue and click Next. 6. On the Core Components page review the components available for upgrade. 7. On the Firewall page review the default ports and configure firewall rules. 8. On the Upgrade page review the prerequisites to be installed and the components to be upgraded and then click Upgrade. 9. On the Finish Upgrade page one of the following messages appears upon completion:

Success Upgrade successful appears when the upgrade completes without errors.

Failed The Upgrade failed appears with a list of failed components. Click Why did this fail to review what you must do to fix the problem. Other components that installed successfully are retained; you do not need to reinstall them. Select Launch Studio to start Studio when the upgrade completes and click Finish.

Upgrade the Virtual Delivery Agent

You can only upgrade Desktop OS (Windows Desktop) Virtual Delivery Agents (VDAs). For Remote PC Access deployments, Citrix recommends that you upgrade a VDA in a remote PC using a command-line method. For detailed information, see Install using the command line. 1. Log on to the server using a local administrator account and run the installer by inserting the media or mounting the ISO drive for this release, and double-clicking AutoSelect. 2. On the Welcome page, click Start. The wizard detects what components need to be upgraded and displays the Upgrade options page, activating the components you can upgrade. 3. On the Upgrade options page, select:

Virtual Delivery Agent for Windows Desktop OS for Desktop OS, and earlier XenDesktop versions

Virtual Delivery Agent for Windows Server OS for Server OS 4. On the Installation Environment page, select one of the following:

Build a master image that creates other machines (default)

Install the Virtual Delivery Agent directly on a user's machine 5. On the Core Components page, you can optionally select Citrix Receiver.

13

Upgrade components 6. On the Delivery Controller page, select an option from the drop-down list:

Manually (default) Enter a Controller address as shown in the example. You can optionally add additional Controllers or test the connections. I will do this later or Machine Creation Services configure automatically

Choose locations from Active Directory 7. On the Features page, you can optionally select and clear other features, such as Use Remote Assistance.

8. On the Firewall page review the default ports and configure firewall rules. 9. On the Summary review the prerequisites to be installed and the components to be upgraded then click Upgrade. 10. On the Finish Upgrade page one of the following messages appears upon completion:

Success Upgrade successful appears when the upgrade completes without errors.

Failed The Upgrade failed appears with a list of failed components. Click Why did this fail to review what you must do to fix the problem. Other components that installed successfully are retained; you do not need to reinstall them. Optionally select Launch Studio to start Studio when the upgrade completes and click Finish.

Upgrade the Database using Studio

After upgrading the core components, use Studio to upgrade the Database.

Automatically upgrade the Database

1. Start Studio. The wizard detects what components need to be upgraded and displays the Mandatory upgrade page. 2. Select Start the Site upgrade automatically. 3. At the prompt, select I am ready to upgrade. The wizard displays the upgrade progress. After the upgrade completes, the wizard performs tests. This takes several minutes. 4. At the Site Upgrade Complete window, you can optionally view a data migration report and then click Finish. 5. At the Upgrade successful page, click Finish upgrade and return to the Site overview.

14

Upgrade components

Manually upgrade the Database

To minimize Site down time when performing a manual upgrade, it is important that the XenDesktop Administrator closely coordinates with the Database Administrator. This process requires that you run a script that temporarily disables Xendesktop Services while the manual upgrade scripts run. Ideally, immediately after these scripts complete, the XenDesktop Administrator should enable XenDesktop Services and complete the upgrade using Studio. Manual upgrade requires:

Compatible License Server and license files Database backup Running the generated scripts in the following order:

1. DisableServices.ps1 PowerShell script to be run by the XenDesktop administrator on an XenDesktop Controller 2. UpgradeDatabase.sql SQL script run by the database administrator using a preferred tool (for example, SQL Server Management Studio) 3. EnableServices.ps1 PowerShell script to be run by the XenDesktop administrator on an XenDesktop Controller To upgrade manually 1. Start Studio. The wizard detects what components need to be upgraded and displays the Mandatory upgrade page. 2. Select Manually upgrade this site. 3. The wizard checks for License Server compatibility. Make sure your License Server and license files are compatible with XenDesktop 7. Select the confirmation check box and click Continue. 4. The wizard prompts you to backup the Database. When you have done so, select the confirmation check box and click Continue.

The wizard generates the manual upgrade scripts that you must run and displays them in a window

The Mandatory Upgrade page changes to display a checklist of the manual upgrade steps 5. Make sure you have completed the checklist tasks and click Finish upgrade and return to Common Tasks.

Upgrade the remaining Delivery Controllers

Upgrade any additional Delivery Controllers in your Site. 1. On the Common Tasks page click Upgrade remaining Delivery Controllers. A list of Deliver Controllers appears.

15

Upgrade components 2. Perform all the previously described tasks, starting with To upgrade core components on each Delivery Controller. 3. When you have completed all Delivery Controller upgrades, click I have upgraded remaining Delivery Controllers and click Finish. 4. Close Studio and then reopen Studio to implement the changes. 5. In the SITE CONFIGURATION section of the Common Tasks page, select Perform registration. Registering the remaining Delivery Controllers makes the Delivery Controllers and their services available to the Site.

16