Upgrading changes deployments to the newest component versions without having to set up new machines or Sites; this is known as an in-place upgrade. You can upgrade to the current version from:
- XenDesktop 5.6 *
- XenDesktop 7.0
- XenDesktop 7.1
- XenApp and XenDesktop 7.5
- XenApp and XenDesktop 7.6
- XenApp and XenDesktop 7.6 LTSR
- XenApp and XenDesktop 7.7
- XenApp and XenDesktop 7.8
- XenApp and XenDesktop 7.9
- XenApp and XenDesktop 7.11
- XenApp and XenDesktop 7.12
- XenApp and XenDesktop 7.13
- XenApp and XenDesktop 7.14
- XenApp and XenDesktop 7.15 LTSR
- XenApp and XenDesktop 7.16
- XenApp and XenDesktop 7.17
* To upgrade from XenDesktop 5.6 to this CR, first upgrade to 7.6 LTSR (with the latest CU), then upgrade to this CR.
- Run the installer on the machines where the core components and VDAs are installed. The software determines if an upgrade is available and installs the newer version.
- Use the newly upgraded Studio to upgrade the database and the Site.
For details, see Upgrade a deployment.
For information about installing Controller hotfixes, see CTX201988.
Migrating moves data from an earlier deployment to the newest version. You can migrate a XenApp 6 deployment. Migrating includes installing current components and creating a new Site, exporting data from the older farm, and then importing the data to the new Site.
For information about architecture, component, and feature changes that were introduced with the 7.x releases, see Changes in 7.x.
To migrate from XenApp 6.5:
- Install core components and create a new XenApp Site.
- From the XenApp 6.5 controller, use PowerShell cmdlets to export policy and/or farm data to XML files. You can edit the XML file content to tailor the information you will import.
- From the new Site, use PowerShell cmdlets and the XML files to import policy and/or application data to the new Site.
- Complete post-migration tasks on the new Site.
For details, see Migrate XenApp 6.x.