The standalone command-line utility, migprofile.exe, migrates V2 user profiles to V5 user profiles, or V1 user profiles to V2 user profiles. The utility is intended for users who are migrating from legacy machines in a View environment, or from legacy computers in any physical or virtual environment, to machines running later Windows versions in a View environment.
After you migrate the user profiles, the View Persona Management feature integrates the V2 or V5 profiles on the View machines. When users log in to their new desktops, they are presented with the same personal settings and data that they used on their original machines.
Table 1 shows the Windows user profiles, and their associated Windows operating system versions, that you can migrate with the migprofile.exe utility.
|Source User Profile||Source Windows Version||Destination User Profile||Destination Windows Version|
|V2||Windows 7, Windows 8 or 8.1, Windows Server 2008 R2, or Windows Server 2012 R2||V5||Windows 10|
|V1||Windows XP||V2||Windows 7, Windows 8 or 8.1, Windows Server 2008 R2, or Windows Server 2012 R2|
To migrate user profiles from a Windows XP or Windows Vista desktop deployment to a Windows 10 desktop deployment, you can migrate the V1 profiles to V2 and then migrate the V2 profiles to V5.
With the View user profile migration utility, you can perform an important task in a migration from a legacy Windows XP desktop deployment to a desktop deployment that will continue to be supported in future View releases.
You can migrate V1 or V2 profiles from the following source locations:
- Remote profile repository on a CIFS network share.
The utility can migrate multiple remote profiles on the same CIFS network share or a different CIFS share.
- User's local profile on a physical computer or virtual machine.
The utility can migrate a single local profile on a computer. To migrate multiple users' local profiles, 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 configured with a remote profile management solution such as View Persona Management or Windows roaming profiles. If no remote profile management solution is in place, you must specify users' local profiles as the source profile paths.
The profile migration utility has the following features:
- The destination of the migrated V2 or V5 profiles must be a remote profile repository that resides on a CIFS network share. In View, this CIFS path must be configured as the View Persona Management remote profile repository.
- You run the migration tool as a standalone utility. View components do not have to be running during a profile migration.
- The migration utility performs a one-time migration of user profile data and registry settings.
The utility does not merge the source and destination profiles after the destination profiles are created. If users continue to use their legacy computers after the migration, the new profile data that is generated on their legacy computers remains separate from the migrated profiles.
- 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 configuring settings in a migration configuration file.