User Profile Migration

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.
You specify whether to migrate V1 profiles to V2 or V2 profiles to V5 in the source tag. Use only one
source tag in the configuration file.
<migconfig takeownership="takeownership_value">
<!-- specify the source V1 profiles to be migrated -->
<source>
<!-- specify the location of user profiles to be migrated -->
<profilepath>source_profile_path</profilepath>
</source>
<!-- OR -->
<!-- specify the source V2 profiles to be migrated -->
<source>
<!-- specify the location of user profiles to be migrated -->
<profilepath>source_profile_path</profilepath>
<!-- specify a V2-to-V5 profile migration -->
<migv2tov5>true</migv2tov5>
</source>
<!-- specify the target destination of converted V2 or V5 profiles -->
<target>
<profilepath>target_profile_path</profilepath>
</target>
<!-- specify other profile migration settings -->
<migration>
<!-- migration settings for profile folders and files -->
<profile>
<!-- by default, all top-level profile folders are included -->
<!-- except 'Cache', 'History', & 'Local AppData' -->
<includeolders>included_profile_folders</includefolders>
<excludefolders>excluded_profile_folders</excludefolders>
</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>
View User Profile Migration
VMware, Inc. 10