View User Profile Migration Modified on 4 JAN 2018 VMware Horizon 7 7.
View User Profile Migration You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/ If you have comments about this documentation, submit your feedback to docfeedback@vmware.com VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com Copyright © 2012–2018 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc.
Contents View User Profile Migration 4 1 User Profile Migration Overview 5 Best Practices for Running a User Profile Migration Prerequisites for Running the Profile Migration Utility migprofile.exe Command Usage Migration Configuration File VMware, Inc.
View User Profile Migration View User Profile Migration describes how to use the View profile migration command-line utility to migrate Windows 7, Windows 8 or 8.1, Windows Server 2008 R2, or Windows Server 2012 R2 user profiles, which use the V2 format, to Windows 10 user profiles, which use the V5 format. You can also migrate Windows XP user profiles, which use the V1 format, to the later Windows versions that use the V2 format.
User Profile Migration Overview 1 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.
View User Profile Migration You can migrate V1 or V2 profiles from the following source locations: n 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. n 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.
View User Profile Migration n If you are migrating V1 profiles on legacy Windows XP machines, 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 destination user profiles.
View User Profile Migration migprofile.exe Command Usage The syntax of the migprofile.exe command controls the migration of profiles. When you install View Agent with the View Persona Management setup option on a virtual machine, the migprofile.exe utility is installed in the install_directory\VMware\VMware View\Agent\bin directory. When you install the standalone View Persona Management software on a system, the migprofile.exe utility is installed in the install_directory\VMware\VMware View\Persona Manage
View User Profile Migration migprofile.exe Command-Line Examples The following example migrates all V1 user profiles under the \\file01\profiles folder to the same location. V2 user profiles are created with .V2 appended to each user's root folder name. The utility takes ownership of the user profiles during the migration: migprofile.exe /s:\\file01\profiles\* /takeownership The following example migrates all V2 user profiles under the \\file02\share\profiles folder to the same location.
View 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.
View User Profile Migration Migration Configuration File Settings In the migration configuration file, you can specify settings that control the profile migration. Some settings correspond to the migprofile.exe command-line options. Additional settings let you configure other aspects of a migration. For example, you can specify folders to include or exclude and registry keys to include or exclude. Take Ownership of the User Profile Set the takeownership setting to "1" to cause the migprofile.
View User Profile Migration Source Profile Path Use the source_profile_path setting to specify the path name of the source V1 or V2 profile path to be migrated. source_profile_path or source_profile_path true If you do not specify the source profile path in a command-line option, you must specify this setting in the migration configuration file.
View User Profile Migration \\file02\share\profiles\*.v2 true Target Profile Path Use the target_profile_path setting to specify the path name of the target V2 or V5 profile after the migration: target_profile_path The utility appends .V2 to the root folder name of a target V2 profile or .V5 to the root folder name of a target V5 profile.
View User Profile Migration Table 1‑3. Folder Identifiers Used in the Migration Configuration File (Continued) Folder Identifiers Windows Folder Names Personal \My Documents PrintHood \PrintHood (Printer Neighborhood) Programs \Start Menu\Programs Recent \Recent SendTo \SendTo Start Menu \Start Menu Startup \Start Menu\Programs\Startup Templates \Templates OneDrive \OneDrive (Used in V5 profiles only) Folders to Exclude Use the excluded_profile_folders setting to list the source profile
View User Profile Migration n Printers n Software n System n AppXBackupContentType (used on Windows 10) The following example specifies the Console and System keys: Console, System 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.
View User Profile Migration Example: Migrating V1 Profiles 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. PAGE 17View User Profile Migration
VMware, Inc.
