6.0

This chapter includes the following topics:
n
“Best Practices for Running a V1 to V2 Profile Migration,” on page 8
n
“Prerequisites for Running the Profile Migration Utility,” on page 8
n
“migprofile.exe Command Usage,” on page 9
n
“Migration Configuration File,” on page 10
Best Practices for Running a V1 to V2 Profile Migration
Following best practices ensures the success of a profile migration.
n
In View, configure Windows 7, Windows 8 or 8.1, or Windows Server 2008 R2 desktop pools for your
users before you begin the profile migration. Configure View Persona Management for the desktop
pools.
In particular, configure a CIFS network share as the View Persona Management remote profile
repository. The CIFS network share will be the destination path in the migration.
n
In general, run the migration utility on a Windows 7 or later 32-bit system, because most V1 profiles 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 files in the base image's default profile are then migrated to the
V2 user profiles.
n
If a user must continue to use the legacy Windows XP system after a migration, configure redirected
folders for both the legacy Windows XP system and the Windows 7, Windows 8 or 8.1, or Windows
Server 2008 R2 View machine. This approach allows the user to access files from both systems.
Prerequisites for Running the Profile Migration Utility
Before you run the migprofile.exe utility, verify that your legacy and destination environments satisfy
specific prerequisites.
n
Run the migration utility on a Windows 7, Windows 8 or 8.1, or Windows Server 2008 R2 physical
computer or virtual machine.
n
Log in to the system as a local administrator.
n
Verify that the system on which you run the utility has network access to the CIFS network shares that
contain the source V1 path and destination V2 path.
n
Verify that the user account that runs the utility is a local administrator on the destination CIFS network
share.
n
If the user account that runs the utility does not have full ownership of the user profiles that are
migrated, specify the /takeownership option with the utility.
This option passes ownership of the user profile folders to the utility during the migration. Ownership
is returned to the users after the migration is completed.
n
Ensure that the users whose profiles are being migrated are not logged in to their Windows XP systems
when you initiate the migration.
If a user is in an active session during the migration, the migration might fail.
n
Ensure that users do not start using their Windows 7, Windows 8 or 8.1, or Windows Server 2008 R2
desktops before the migration is completed.
When users start using their View desktops, View Persona Management creates V2 profiles for the
users. If a V2 profile already exists before the migration runs, the utility leaves the existing V2 profile in
place and does not migrate the legacy V1 profile.
View User Profile Migration
8 VMware, Inc.