6.0

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
Table 1-2. Do not use folder names.
Chapter 1 User Profile Migration Overview
VMware, Inc. 11