Product Documentation

Requirements and Installation

Jul 06, 2010

You can migrate a single XenApp 5 farm (multiple farm consolidation to a single farm is not supported).

You should be familiar with MFCOM and PowerShell.

Requirements for the Legacy Farm

  • The servers in the legacy farm must be running XenApp 5 for Windows Server 2003 with Hotfix Rollup Pack 5 (HRP5) or XenApp 5 for Windows Server 2008.
  • The legacy farm server from which you are exporting must have network COM+ access enabled.
  • To access the XenApp 5 server in the legacy farm using a remote connection, you must be a member of the DCOM users group, and you must be a Citrix administrator with at least view-only privileges in the legacy farm.
  • When migrating from a 32-bit XenApp farm to a XenApp 6 farm, network printers used by policies (session printers) must have a 64-bit driver installed in the print server; otherwise, those printers will not be migrated.

Requirements for the New Farm

  • The servers in the new farm must be running XenApp 6 for Windows Server 2008 R2.
  • To install the Citrix XenApp Migration Module, you must have permission to install components. To run the XenApp 6 Migration Tool cmdlets, you must be a Citrix administrator with full privileges.
  • You must have write access to the folder where the migrationoptions.xml file (containing server mappings, migration options, and object property overrides) and the exported data from the legacy farm is placed. By default, this is a folder named Data, located under the XenApp 6 Migration Tool installation files in C:\Users\user\appdata\local\citrix\citrix.xenapp.migration). You can specify a different folder with the -DataFolderPath option in the Set-XAMigrationOption cmdlet.
  • By default, execution of PowerShell scripts is disabled. To run the XenApp 6 Migration Tool cmdlets, sign the scripts or enable the scripts to run (Set-ExecutionPolicy RemoteSigned). You are prompted during installation if this has not been done.
  • If your legacy farm uses file type association for published applications, update the new farm with file type associations (using the Update file types from registry task in the Delivery Services Console) before you migrate applications. This allows the migration process to create the associations in the new farm.
  • Create worker groups in the new farm for server and application silos. (However, if a worker group specified in a server mapping does not exist, the XenApp 6 Migration Tool creates it.)
  • The following software is required to install the Citrix XenApp Migration Module and run the cmdlets. This software is required for XenApp server installation and configuration, so it is likely to already be installed.
    • .NET Framework 3.5 SP1
    • MSI 3.0
    • PowerShell 2.0
  • If you installed the beta version of the XenApp 6 Migration Tool, manually uninstall it and then delete the folder \users\user\AppData\Local\Citrix\Citrix.XenApp.Migration before installing the newer version of the tool.

Installing the XenApp 6 Migration Tool

Install the XenApp 6 Migration Tool on one server in the new farm. In most cases, this is the server where you installed and configured XenApp 6 to create the farm.
  1. Download the XenApp 6 Migration Tool from My Citrix.
  2. Double-click Citrix.XenApp.Migration.exe; the self-extracting executable launches an MSI that installs the module. During installation, you are prompted to set the PowerShell execution policy to unrestricted, if the current policy setting differs.
  3. The installer creates shortcuts in the Start menu. Clicking (launching) the shortcut opens PowerShell and loads the module. (If you do not use the shortcut, open a PowerShell console and type Import-Module Citrix.XenApp.Commands.)

When launching the XenApp 6 Migration Tool, restart the server if you receive the following error message: Import-Module: The specified module 'Citrix.XenApp.Migration' was not loaded because no valid module file was found in any module directory.

Note: Citrix recommends performing the migration entirely from a server in the new farm. If your deployment does not allow this, see Advanced Cmdlets.