7.0

</profile>
<!-- migration settings for profile registry hive -->
<registry [disabled="1"]>
<!-- by default, no registry keys are converted -->
<includekeys>included_registry_keys</includekeys>
<excludekeys>excluded_registry_keys</excludekeys>
</registry>
</migration>
</migconfig>
Migration Configuration File Settings
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.
V1-to-V2 or V2-to-V5 Migration
Set the migv2tov5 setting to true to perform a V2-to-V5 profile migration. When you do not use this setting,
the utility performs a V1-to-V2 profile migration.
Specify the migv2tov5 setting in the source tag. Use only one source tag in the configuration file.
You can perform either a V1-to-V2 migration or a V2-to-V5 migration. You cannot perform both migration
paths in the same configuration file.
The following example specifies a V2-to-V5 profile migration:
<source>
<profilepath>source_profile_path</profilepath>
<migv2tov5>true</migv2tov5>
</source>
The following example specifies a V1-to-V2 profile migration:
<source>
<profilepath>source_profile_path</profilepath>
</source>
View User Profile Migration
12 VMware, Inc.