User Profile Migration

n
User's local prole on a physical computer or virtual machine.
The utility can migrate a single local prole on a computer. To migrate multiple users' local proles, you
can write a script that directs the utility to execute in batch mode.
The source environment can comprise physical computers or virtual machines. The source environment
does not have to be congured with a remote prole management solution such as View Persona
Management or Windows roaming proles. If no remote prole management solution is in place, you must
specify users' local proles as the source prole paths.
The prole migration utility has the following features:
n
The destination of the migrated V2 or V5 proles must be a remote prole repository that resides on a
CIFS network share. In View, this CIFS path must be congured as the View Persona Management
remote prole repository.
n
You run the migration tool as a standalone utility. View components do not have to be running during a
prole migration.
n
The migration utility performs a one-time migration of user prole data and registry seings.
The utility does not merge the source and destination proles after the destination proles are created.
If users continue to use their legacy computers after the migration, the new prole data that is
generated on their legacy computers remains separate from the migrated proles.
n
You can control the source and destination of the migration, and specify which folders and registry keys
to migrate, by using command-line arguments and conguring seings in a migration conguration
le.
This chapter includes the following topics:
n
“Best Practices for Running a User Prole Migration,” on page 8
n
“Prerequisites for Running the Prole Migration Utility,” on page 9
n
“migprole.exe Command Usage,” on page 9
n
“Migration Conguration File,” on page 11
Best Practices for Running a User Profile Migration
Following best practices ensures the success of a prole migration.
n
In View, congure the destination desktop pools for your users before you begin the prole migration.
Congure View Persona Management for the desktop pools.
In particular, congure a CIFS network share as the View Persona Management remote prole
repository. The CIFS network share will be the destination path in the migration.
n
If you are migrating V1 proles on legacy Windows XP machines, run the migration utility on a
Windows 7 or later 32-bit system, because most V1 proles are 32-bit.
n
If you can, run the migration utility on the same template or virtual machine image that the destination
View desktop pool will use. Folders and les in the base image's default prole are then migrated to the
destination user proles.
n
If a user must continue to use the legacy system after a migration, congure redirected folders for both
the legacy system and the destination View machine. This approach allows the user to access les from
both systems.
View User Profile Migration
8 VMware, Inc.