Product Documentation

XenApp 6 Migration Tool

Oct 09, 2015

The XenApp 6 Migration Tool comprises PowerShell cmdlets packaged as a PowerShell 2.0 module. The Migration Tool pulls data from a legacy XenApp farm and imports (adds) it to your new XenApp 6 server farm.

You install the Migration Tool and run the cmdlets on a server in the new XenApp 6 farm. When you start a migration, you point to a remote server in the legacy XenApp 5 farm. The Migration Tool uses MFCOM to communicate with that remote server; the Migration Tool uses XenApp 6 commands to communicate with the new XenApp 6 farm.

Citrix recommends performing the migration entirely from a server in the new XenApp 6 farm; this is called a direct migration. However, if your deployment does not allow this, see Advanced Cmdlets for information about indirect migrations.

Settings are grouped as object types. You can migrate all object types at once, or include and exclude object types and named objects in the migration. You can specify new values for migrated object properties. Servers in the legacy farm are migrated to worker groups in the new farm according to server mappings you specify.

Repeat the migration as additional servers in the legacy farm become ready for reimaging in the new farm. During subsequent migrations, the XenApp 6 Migration Tool compares newly-migrated objects from the legacy farm with previously-migrated object in the new farm. Previously-migrated objects in the new farm are updated if needed.

For example, assume you migrate applications from the legacy farm in June, then change the configuration of Application XYZ in the legacy farm in September. When you migrate applications again in December, the configuration of Application XYZ is updated in the new farm.

However, if you migrate settings, then change them in the new farm, a later migration of the same objects will overwrite the new settings with the legacy farm values.

As the migration of more legacy farm servers continues, use the Web Interface user roaming feature to help ensure that users can access applications and resources.

Objects You Can Migrate

You can migrate the following XenApp object types.
Object Type Description


All applications are enumerated; however, for the corresponding worker group to be associated with the application, the application must be published to one of the servers specified in the server mapping file. Only users that can be resolved on the server in the new farm (account authorities that are trusted in the new farm) are migrated.


Includes application folders and server folders. Server folders are migrated so that server permissions can be copied; however, the server objects are not migrated.

Load evaluator

Load evaluators and their rules are migrated. Migrated load evaluators are attached to applications (where applicable), but they are not attached to servers.


Policies are migrated by creating an IMA (Independent Management Architecture) User GPO (Group Policy Object) with the same name as the policy. Server filters are migrated by using the Server Group (worker group) filter for the servers in the mapping file. For user filters, only the accounts that can be resolved on the target server in the new farm (account authorities that are trusted in the new farm) are migrated.

The Zone Preference and Failover policy is converted to a Worker Group Preference and Failover policy. Servers in the zone that are specified in the server mapping file resolve to a worker group.

Server configuration

Configuration settings for servers specified in the server mapping file are migrated by creating an IMA Machine GPO named "WorkerGroupname" where name is the name of the worker group specified in the server mapping file. This policy is filtered by worker group. Worker groups are created as necessary, but they are not associated with servers or OUs (Organizational Units).

Farm configuration

Farm configuration settings are migrated by creating an IMA Machine GPO named "Farm." This policy is unfiltered.


Only Citrix administrators whose accounts can be resolved on the server in the new farm are migrated (the corresponding account authorities are trusted in the new farm or they represent Citrix built-in accounts).

Farm and server settings from the legacy farm are compared against the default values used when the new XenApp farm was created. The corresponding setting in the policy in the new farm is set to "Not Configured" if it matches the default value for the same setting in the new farm.

Health Monitoring and Recovery (HMR) test executables are not copied; however, HMR test configurations are migrated into policies in the new farm.

You cannot transfer the following settings using the Migration Tool:
  • Zones
  • Printer management
  • Configuration Logging settings

Only settings that reside in the IMA data store are migrated; settings that reside only in the server registry are not migrated.

The migration process ignores the following settings:
  • Deprecated settings, such as AIE (Application Isolation Environment).
  • Permissions that do not exist in the XenApp 6 for Windows Server 2008 R2 release, whether they correspond to a deprecated feature or a configuration setting that is now supported as a policy.