Control File Syntax

The default migration .xml files use XML elements to control migration behavior. These files cover the most common applications, documents, and settings. If you want to migrate settings and application data that the default migration .xml files don't cover, you should create a custom .xml file. The full XML reference for USMT is in the USMT.chm help file in the Windows AIK. Additionally, the XML reference in USMT.chm contains good examples that you can use as your starting point for creating custom migration .xml files.

Note The best practice is to create custom migration .xml files instead of adding application data and settings to the default migration .xml files. Doing so makes maintaining those settings easier over time and prevents confusion.

Deploying Migration Files

The following list describes how to deploy custom migration .xml files for stand-alone use, with MDT 2010, and with Configuration Manager:

• Stand-alone use You can store the migration .xml files in the USMT program folder or place them in a central location. You must specify the full path to each migration .xml file (Scanstate \\server\share\computer /I:\\server\share\migration.xml).
• Microsoft Deployment Toolkit MDT 2010 has a specific organization for deployment shares. You must store custom migration .xml files in the USMT\platform folder of the deployment share, where platform is either x86 or x64.
• Configuration Manager Configuration Manager uses USMT to migrate user state data during operating system deployments. You can specify the location of migration .xml files and data stores during the configuration of Configuration Manager. See the System Center Configuration Manager 2007 documentation for more information.