Product Documentation

Advanced Cmdlets

Jul 06, 2010

Using the Migration Tool on Separate Servers (Indirect Migration)

Citrix recommends performing the migration entirely from a server in the new farm (a direct migration). However, if you cannot use MFCOM to communicate between the legacy farm and the new farm, perhaps because the two farms are in different domains that do not have a trust relationship, you can perform an indirect migration. In this case, you must also install the XenApp 6 Migration Tool on a server in the legacy farm, in addition to installing it on a server in the new farm. For an indirect migration, after you install the XenApp 6 Migration Tool on a server in the new farm:
  1. On a server in the legacy farm:
    1. Install the required software (.NET Framework 3.5 SP1, MSI 3.0, and PowerShell 2.0).
    2. Download the XenApp 6 Migration Tool from My Citrix.
    3. Install the XenApp 6 Migration Tool (32-bit or 64-bit version, depending on the legacy server operating system).
    4. Build a file containing server mappings, migration options, and property value overrides, as described in Using the XenApp 6 Migration Tool Cmdlets.
    5. Export settings using the Start-XAMigration cmdlet with the -ExportOnly option. The output is a series of XML files.
  2. Copy the XML files to the server in the new farm, replacing the files on that server. This includes the file containing server mappings, migration options, and property value overrides.
  3. From the new farm, issue a cmdlet to import the settings (using the Start-XAMigration cmdlet with the -ImportOnly option or using one of the advanced import cmdlets .

Advanced Import Cmdlets

The Start-XAMigration cmdlet is intended for scripted, unattended migrations. For interactive testing, the XenApp 6 Migration Tool includes additional object-specific import cmdlets. These cmdlets offer alternatives to using the –ImportOnly option with the Start-XAMigration cmdlet and the -ObjectType and -Include options with the Set-XAMigrationOption cmdlet.

You can also use these cmdlets during indirect migrations.

These cmdlets use the configured server mappings, migration options, and object property value overrides.

For complete PowerShell syntax, type Get-Help cmdlet.
  • Import-XAApplication
  • Import-XAFolder
  • Import-XALoadEvaluator
  • Import-XAPolicy
  • Import-XAServerConfiguration
  • Import-XAFarmConfiguration
  • Import-XAAdministrator

Advanced XALegacy Cmdlets

Using the advanced XALegacy cmdlets can be helpful if an object did not migrate as expected. The Get-XALegacy* cmdlets connect to the legacy farm and read the settings for an object in the legacy farm. You can use the Convert-XALegacyObject, New-XALegacyConnection, and Remove-XALegacyConnection cmdlets when creating a custom migration script that does not use the Import-XA* or Start-XAMigration cmdlets.

For complete PowerShell syntax, type Get-Help cmdlet.
  • Get-XALegacyAdministrator
  • Get-XALegacyApplication
  • Get-XALegacyFarmConfiguration
  • Get-XALegacyFolder
  • Get-XALegacyHmrTest
  • Get-XALegacyLoadEvaluator
  • Get-XALegacyPolicy
  • Get-XALegacyPolicyConfiguration
  • Get-XALegacyPolicyFilter
  • Get-XALegacyServer
  • Get-XALegacyServerConfiguration
  • Get-XALegacySessionPrinter
  • Convert-XALegacyObject
  • New-XALegacyConnection
  • Remove-XALegacyConnection

These advanced cmdlets include objects that cannot be migrated alone (for example, session printers that are inside a user policy, and HMR tests that are inside farm or server settings). This greater granularity may be helpful when troubleshooting migration, because these objects are more complex, with multiple sets of properties.