6.0

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:
n
Console
n
Control Panel
n
Identities
n
Keyboard Layout
n
Printers
n
Software
n
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,” on page 12.
Example Migration Configuration Files
You can control a migration by editing settings in a migration configuration file.
Example: Migrating from a Remote Profile Path
The following example file converts all remote V1 profiles that reside under the \\file01\profiles folder to
V2 profiles in the same location.
The migrated V2 profiles use the same user names as the V1 profiles. A .V2 extension is appended to the
users' root folders. All folders except Local Settings are migrated. User registry keys are migrated.
<migconfig version = "0.1">
<!-- specify the source V1 profiles to be migrated -->
<source>
<!-- specify the location of user profiles to be migrated -->
<profilepath>\\file01\profiles\*</profilepath>
</source>
<!-- specify the target destination of converted V2 profiles -->
<target>
<profilepath>\\file01\profiles</profilepath>
</target>
</migconfig>
Example: Migrating from a User's Local Profile
The following example file converts a local V1 profile for the user ts115. The utility migrates the local profile
on the machine devvm-winxp to a remote V2 profile under the \\file01\profiles folder.
Chapter 1 User Profile Migration Overview
VMware, Inc. 13