User Profile Migration

</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 conguration le, you can specify seings that control the prole migration. Some seings
correspond to the migprofile.exe command-line options. Additional seings let you congure 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 seing to "1" to cause the migprofile.exe utility to take ownership of the user prole
during the migration. Use the following format:
<migconfig takeownership="1">
...
...
</migconfig>
If you do not specify this seing, the value defaults to "0", which turns o the takeownership behavior.
V1-to-V2 or V2-to-V5 Migration
Set the migv2tov5 seing to true to perform a V2-to-V5 prole migration. When you do not use this seing,
the utility performs a V1-to-V2 prole migration.
Specify the migv2tov5 seing in the source tag. Use only one source tag in the conguration le.
You can perform either a V1-to-V2 migration or a V2-to-V5 migration. You cannot perform both migration
paths in the same conguration le.
The following example species a V2-to-V5 prole migration:
<source>
<profilepath>source_profile_path</profilepath>
<migv2tov5>true</migv2tov5>
</source>
The following example species a V1-to-V2 prole migration:
<source>
<profilepath>source_profile_path</profilepath>
</source>
View User Profile Migration
12 VMware, Inc.