In the migration configuration file, you can specify settings that control the profile migration. Some settings correspond to the migprofile.exe command-line options. Additional settings let you configure other aspects of a migration.

For example, you can specify folders to include or exclude and registry keys to include or exclude.

Take Ownership of the User Profile

Set the takeownership setting to "1" to cause the migprofile.exe utility to take ownership of the user profile during the migration. Use the following format:

<migconfig takeownership="1">
   ...
   ...
</migconfig>

If you do not specify this setting, the value defaults to "0", which turns off the takeownership behavior.

Source V1 Profile Path

Use the source_profile_path setting to specify the path name of the source V1 profile path to be migrated:

<source>
  <profilepath>source_profile_path</profilepath>
</source>

If you do not specify the source profile path in a command-line option, you must specify this setting in the migration configuration file. You can specify a single user's profile path or use the * wildcard to migrate all profiles under a folder.

The following example specifies a single remote user profile:

<source>
  <profilepath>\\file01\profiles\ts115</profilepath>
</source>

The following example specifies a single user's local profile on an existing machine:

<source>
  <profilepath>\\devvm-winxp\c$\documents and settings\ts115</profilepath>
</source>

The following example specifies all remote user profiles under a remote shared folder:

<source>
  <profilepath>\\file01\profiles\*</profilepath>
</source>

Target V2 Profile Path

Use the target_profile_path setting to specify the path name of the target V2 profile after the migration:

<target>
  <profilepath>target_profile_path</profilepath>
</target>

The utility appends .V2 to the root folder name of the target V2 profile.

Folders to Include

Use the included_profile_folders setting to list the V1 profile folders to include in the migration.

By default, all top-level shell folders except Cache, History, and Local AppData are migrated. If you use this setting, only the specified folders are migrated.

Format this setting as a comma-separated list. To specify folders, use the folder identifiers shown in 1. Do not use folder names.

The following example specifies the My Documents, Desktop, Start Menu, and Network Neighborhood folders to migrate:

<includefolders>Personal, Desktop, Start Menu, NetHood</includefolders>
Table 1. Folder Identifiers Used in the Migration Configuration File

Folder Identifiers

Windows Folder Names

AppData

\Application Data

Cache

\Local Settings\Temporary Internet Files

Cookies

\Cookies

Desktop

\Desktop

Favorites

\Favorites

History

\Local Settings\History

Local AppData

\Local Settings\Application Data

My Music

\My Documents\My Music

My Pictures

\My Documents\My Pictures

My Video

\My Documents\My Videos

NetHood

\NetHood (Network Neighborhood)

Personal

\My Documents

PrintHood

\PrintHood (Printer Neighborhood)

Programs

\Start Menu\Programs

Recent

\Recent

SendTo

\SendTo

Start Menu

\Start Menu

Startup

\Start Menu\Programs\Startup

Templates

\Templates

Folders to Exclude

Use the excluded_profile_folders setting to list the V1 profile folders to exclude from the migration. This list can exclude folders that are included by default and folders that reside under folders in the included_profile_folders list.

Format this setting as a comma-separated list. To specify folders, use the folder identifiers shown in 1. Do not use folder names.

The following example specifies the My Documents and My Pictures folders to exclude from migration:

<excludefolders>Personal, My Pictures</excludefolders>

Disable Registry Migration

To disable registry migration, set the optional disabled setting to "1". Use the following format:

<registry disabled="1">
</registry>

Registry Keys to Include

Use the included_registry_keys setting to list registry keys to include in the migration.

By default, the all registry keys in the user registry hive are migrated to the V2 profile. If you use this setting, only the specified registry keys are migrated.

Format this setting as a comma-separated list. To specify registry keys, use the following key identifiers:

  • Console

  • Control Panel

  • Identities

  • Keyboard Layout

  • Printers

  • Software

  • System

The following example specifies the Console and System keys:

<includekeys>Console, System</includekeys>

Registry Keys to Exclude

Use the excluded_registry_keys setting to list registry keys to exclude from the migration. You can exclude keys that are included by default, keys that reside within the included_registry_keys list, and subkeys of top-level keys.

Format this setting as a comma-separated list. To specify registry keys, use the key identifiers shown in Registry Keys to Include.