Product Documentation

Edit the Migration Tool XML file

Sep 23, 2016

Before importing data to a XenDesktop 7.x Site, check and edit the contents of the XML file generated by the export tool (XdExport), particularly if you migrate in multiple stages and import some users, Delivery Groups, and policies before importing others.

Use any text editor to view or change the file contents; you can use a specialized XML editor such as Microsoft XML Notepad.

Some elements within the XML content must be present for the XML file to be accepted by the import tool (XdImport).

The required XML schema is defined in the XdFarm.xsd file that is supplied as part of the Migration Tool download. When working with this file:
  • A minOccurs attribute with a value of 1 or more indicates that particular elements must be present if the parent element is present.
  • If the XML file supplied to the Import tool is not valid, the tool halts and an error message appears that should enable you to locate where the problem lies in the XML file.

Import a subset of desktops or Delivery Groups

To import only a subset of Delivery Groups and desktops, edit the contents of the DesktopGroups element. The DesktopGroups element can hold many DesktopGroup elements, and within each DesktopGroup element there is a Desktops element that can contain many Desktop elements.

Do not delete the DesktopGroups element, although you can delete all the DesktopGroup elements and leave it empty. Similarly, within each DesktopGroup element, the Desktops element must be present but can be empty of Desktop elements.

Delete Desktop or DesktopGroup elements to avoid importing particular single machines or entire Delivery Groups. For example, the XML file contains:
<DesktopGroups> 
 <DesktopGroup name="Group1"> 
… 
  <Desktops> 
   <Desktop sameName="DOMAIN\MACHINE1$"> 
… 
   </Desktop> 
  </Desktops> 
…  
 </DesktopGroup> 
 <DesktopGroup name="Group2"> 
… 
  <Desktops> 
   <Desktop samName="DOMAIN\MACHINE2$"> 
… 
   </Desktop> 
   <Desktop samName="DOMAIN\MACHINE3$"> 
… 
   </Desktop> 
  </Desktops> 
… 
 </DesktopGroup> 
</DesktopGroups>
In this example, the edits prevent Group1 group from being imported. Only Machine3 from the Group2 group will be imported:
<DesktopGroups> 
 <DesktopGroup name="Group2"> 
… 
  <Desktops> 
   <Desktop samName="DOMAIN\MACHINE3$"> 
… 
   </Desktop> 
  </Desktops> 
… 
  </DesktopGroup> 
</DesktopGroups>

Manage Delivery Groups with duplicate names

In XenDesktop 4, Desktop Groups can be organized in folders, Desktop Groups with the same name can appear in different folders, and the internal desktop group name is the name that appears to users. In this release, Delivery Groups cannot be placed in folders, and each Delivery Group must have a unique internal name, and the name that appears to users can be different from the internal name. To accommodate these differences, you might have to rename Desktop Groups.

For example, in your XenDesktop 4 farm, you could have two different Desktop Groups that appear with the name "My Desktop" to two different users, and you could use Desktop Groups folders to achieve this. If these Delivery Groups are to remain separate in the XenDesktop 7.x Site, you must edit the Desktop Group names in the XML file to make them unique.

If a Delivery Group in the XenDesktop 7.x Site has the same name as a Desktop Group to be imported, and the Delivery Groups are to remain separate in the XenDesktop 7.x Site, you must edit the XenDesktop 4 Desktop Group name in the XML file to keep the name unique in the Site. If the Desktop Group to be imported is really the same as the XenDesktop 7.x Delivery Group, and the machines in the XML file are to be merged into the existing Desktop Group, you do not need to rename the Desktop Group; instead, specify the -MergeDesktops parameter to the Import tool. For example, if the XML file contains:
<DesktopGroups> 
 <DesktopGroup name="My Desktop"> 
… 
  <Folder>\Sales</Folder> 
 </DesktopGroup> 
 <DesktopGroup name="My Desktop"> 
… 
  <Folder>\Finance</Folder> 
 </DesktopGroup> 
</DesktopGroups>
Remove the duplicate names as follows:
<DesktopGroups> 
 <DesktopGroup name="Sales Desktops"> 
… 
  <Folder>\Sales</Folder> 
 </DesktopGroup> 
 <DesktopGroup name="Finance Desktops"> 
… 
  <Folder>\Finance</Folder> 
 </DesktopGroup> 
</DesktopGroups>

Manage policy imports

You can delete policies from the XML file, and you can specify unique names to avoid policy name duplication. There is no support for merging policies.
  • When you import policy data, either all polices are imported successfully or, if there is any failure, no policy data is imported.
  • Importing large numbers of policies with many settings can take several hours.
  • If you import policies in batches, their original prioritization may be affected. When you import policies, the relative priorities of the imported polices are maintained, but they are given higher priority than policies already in the Site. For example, if you have four polices to import with priority numbers 1 to 4, and you decide to import them in two batches, you should import policies with priorities 3 and 4 first, because the second batch of policies automatically gets higher priority.
To import only a subset of policies into the XenDesktop 7.x Site, edit the contents of the Policies element. The Policies element can hold many Policy elements. You must not delete the Policies element, although you can delete all the Policy elements and leave it empty. Delete entire Policy elements to avoid importing particular XenDesktop 4 farm policies. For example, if the XML file contains:
<Policies> 
 <Policy name="Sales Policy"> 
… 
 </Policy> 
… 
</Policies>
To avoid importing any XenDesktop 4 policies, and avoid clashes with policies already configured in the XenDesktop 7.x Site, edit the file to remove the individual Policy elements as follows:
<Policies> 
</Policies>
Alternatively, edit the file so that the policy is imported with a different name as follows:
<Policies> 
 <Policy name="XD4 Sales Policy"> 
… 
 </Policy> 
… 
</Policies>