Product Documentation

Using the XenApp 6 Migration Tool Cmdlets

Oct 09, 2015

Run the XenApp 6 Migration Tool cmdlets from the PowerShell console.

  1. Before starting a migration, use the following cmdlets to build a file containing server mappings and optionally, migration options and property value overrides.
    • Use the Add-XAServerMapping cmdlet to map servers in the legacy farm to worker groups in the new farm. The servers in the mapping are representative servers chosen from each server silo in the legacy farm. Server mappings are not required, but a XenApp farm cannot be completely migrated without them (without server mappings, no data about the servers will be migrated; for example, server settings, application servers, or Zone Preference and Failover policy).
      • To display the server mappings you specified, use the Get-XAServerMapping cmdlet.
      • To remove a server mapping, use the Remove-XAServerMapping cmdlet.
    • Use the Set-XAMigrationOption cmdlet to tailor the migration. Setting migration options is optional; it offers flexibility in tailoring your migration.

      You can specify a remote server name; this is the name of the server in the legacy farm from which objects will be migrated. Specifying the remote server name as a migration option eliminates having to specify it each time you start a migration.

      You can also optionally specify a nondefault folder location where the exported data from the legacy farm is stored, and object types or named objects to include or exclude from the migration.

      • To display the migration options you specified, use the Get-XAMigrationOption cmdlet.
    • Use the Add-XASettingOverride cmdlet to specify values for individual object properties, if you do not want to use the migrated values in the new farm. Specifying setting overrides is optional.
      • To display the names of object properties you can specify with the Add-XASettingOverride cmdlet, use the Get-XALegacySettingName cmdlet.
      • To display the property override values you specified, use the Get-XASettingOverride cmdlet.
      • To remove a property override value you specified, use the Remove-XASettingOverride cmdlet.
  2. Launch the migration with the Start-XAMigration cmdlet.
    • To see what would happen during the migration (for example, which objects are migrated and updated, and changes to property values) without actually performing the action, use the -PendingReportOnly option. This option provides more detailed output than the -WhatIf PowerShell common parameter.
  3. After running a migration, use the Get-XAMigrationObjectCount cmdlet to display a count of the objects in the legacy and new farms. This helps monitor equivalency between the new farm and the legacy farm. You can tailor the display to report differences from an existing snapshot.

Subsequent migrations (using the Start-XAMigration cmdlet) will use the current specifications in the server mappings, migration options, and property value overrides file.

Post-migration Tasks

  • Associate servers or OUs with worker groups.
  • Associate application folders with worker groups.
  • Attach load evaluators to servers.
  • Assign zones.
  • Configure printer settings.
  • Initiate Configuration Logging in the new farm.
  • Configure Health Monitoring settings.
  • Optionally, add new servers in the old server folder hierarchy to preserve delegated permissions.
  • To enable streamed-to-server applications to launch after migrating from a 32-bit XenApp farm to a XenApp 6 farm, rebuild profiled applications.