Horizon 7 User Profile Migration Vmware Horizon 7 7

Summary

Horizon 7 User Profile
Migration
OCT 2020
VMware Horizon 7 7.13
Horizon 7 User Profile Migration
You can find the most up-to-date technical documentation on the VMware website at:
https://docs.vmware.com/
VMware, Inc

3401 Hillview Ave

Palo Alto, CA 94304
www.vmware.com
©
Copyright 2012-2020 VMware, Inc. All rights reserved. Copyright and trademark information

VMware, Inc. 2
Contents
Horizon 7 User Profile Migration 4
1 User Profile Migration Overview 5
Best Practices for Running a User Profile Migration 7
Prerequisites for Running the Profile Migration Utility 7
migprofile.exe Command Usage 8
Migration Configuration File 10
Migration Configuration File Settings 11
Example Migration Configuration Files 15
VMware, Inc. 3
Horizon 7 User Profile Migration
Horizon 7 User Profile Migration describes how to use the 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

Intended Audience
This information is intended for Horizon 7 administrators who want to migrate V1 or V2 profiles
on physical computers or virtual machines to V2 or V5 profiles in a Horizon 7 environment. The
information is written for Windows system administrators who are familiar with XML and the
Horizon Persona Management feature

VMware, Inc. 4
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 Horizon 7 environment, or from legacy computers in any physical or
virtual environment, to machines running later Windows versions in a Horizon 7 environment

After you migrate the user profiles, the Horizon Persona Management feature integrates the V2
or V5 profiles on the Horizon 7 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-1. Source and Destination User Profiles and Windows Operating System Versions shows
the Windows user profiles, and their associated Windows operating system versions, that you
can migrate with the migprofile.exe utility

Table 1-1. Source and Destination User Profiles and Windows Operating System Versions
Source User Destination
Profile Source Windows Version User Profile Destination Windows Version
V2 Windows 7, Windows 8 or 8.1, Windows V5 Windows 10
Server 2008 R2, or Windows Server 2012
R2
V1 Windows XP V2 Windows 7, Windows 8 or 8.1, Windows
Server 2008 R2, or Windows Server 2012
R2
VMware, Inc. 5
Horizon 7 User Profile Migration
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

Important View Agent 6.1 and later releases do not support Windows XP and Windows Vista
desktops. View Agent 6.0.2 is the last release that supports these guest operating systems

Customers who have an extended support agreement with Microsoft for Windows XP and Vista,
and an extended support agreement with VMware for these guest operating systems, can
deploy the View Agent 6.0.2 version of their Windows XP and Vista desktops with Connection
Server 6.1

With the 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 releases

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

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
Horizon 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:
n The destination of the migrated V2 or V5 profiles must be a remote profile repository that
resides on a CIFS network share. In Horizon 7, this CIFS path must be configured as the
Horizon Persona Management remote profile repository

n You run the migration tool as a standalone utility. Horizon 7 components do not have to be
running during a profile migration

n 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

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 configuring settings in a
migration configuration file

VMware, Inc. 6
Horizon 7 User Profile Migration
This chapter includes the following topics:
n Best Practices for Running a User Profile Migration
n Prerequisites for Running the Profile Migration Utility
n migprofile.exe Command Usage
n Migration Configuration File
Best Practices for Running a User Profile Migration
Following best practices ensures the success of a profile migration

n In Horizon 7, configure the destination desktop pools for your users before you begin the
profile migration. Configure Horizon Persona Management for the desktop pools

In particular, configure a CIFS network share as the Horizon Persona Management remote
profile repository. The CIFS network share will be the destination path in the 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 Horizon 7 desktop pool will use. Folders and files in the base image's default
profile are then migrated to the destination user profiles

n If a user must continue to use the legacy system after a migration, configure redirected
folders for both the legacy system and the destination Horizon 7 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 physical computer or virtual machine that runs the destination
Windows operating system version

If you are migrating to a V5 user profile, run the utility on a Windows 10 machine

If you are migrating to a V2 user profile, run the utility on a Windows 7, Windows 8 or 8.1,
Windows Server 2008 R2, or Windows Server 2012 R2 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 path and destination path

n Verify that the user account that runs the utility is a local administrator on the destination
CIFS network share

VMware, Inc. 7
Horizon 7 User Profile Migration
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 legacy
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 destination desktops before the migration is
completed

When users start using their Horizon 7 desktops, Horizon Persona Management creates
destination V2 or V5 profiles for the users. If a destination profile already exists before the
migration runs, the utility leaves the existing destination profile in place and does not migrate
the legacy profile

migprofile.exe Command Usage
The syntax of the migprofile.exe command controls the migration of profiles

When you install Horizon Agent with the Horizon 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 Horizon Persona Management software on a system, the
migprofile.exe utility is installed in the install_directory\VMware\VMware View\Persona
Management directory

From a Windows command prompt, use the following syntax for the migprofile.exe command:
migprofile.exe [/s:source_path] [/t:target_path] [/v2] [/r-:] [/takeownership] [config_file]
Table 1-2. migprofile.exe Command-Line Options
Option Description
/s:source_path The path name of the source V2 or V1 profile path to be migrated

Use the wildcard '*.v2' to indicate that all V2 child folders should be migrated to V5

Use the wildcard '*' to indicate that all V1 child folders should be migrated to V2

This option is mandatory. You must specify the source path either on the command
line or in the migration configuration file. If you specify the source path in both places,
the command-line value is used

/t:target_path Path name of the target V5 or V2 profile path

The migration utility creates a folder under this path with the same name as the source
profile folder, appended by .V5 or .V2

This option is mandatory if the source path is a local profile on a computer

This option is optional if the source path is located on a CIFS network share. In this
case, if you do not specify a target path, the destination profile folder is created as a
sibling of the source profile folder on the same CIFS network share

VMware, Inc. 8
Horizon 7 User Profile Migration
Table 1-2. migprofile.exe Command-Line Options (continued)
Option Description
/v2 Migrates a V2 profile to a V5 profile

This option is required to perform a V2-to-V5 migration. When the /v2 option is not
used, the utility performs a V1-to-V2 profile migration

/r-: Disables registry migration

This option is optional

/takeownership Causes the migprofile.exe utility to take ownership of the user profile during the
migration

Use this option if the administrator account that runs the migration utility does not
have ownership of the user profile to be migrated. Typically, only the user and SYSTEM
accounts have ownership of a user profile

This option is optional. When you use this option, the original ownership of the user
profile is restored after the migration is completed

config_file Name of the migration configuration file

This option is optional. Command-line options take precedence over the corresponding
settings in the configuration file if you specify values in both places

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. V5 user profiles are created with .V5 appended to each user's root folder
name. The utility takes ownership of the user profiles during the migration:
migprofile.exe /s:\\file02\share\profiles\*.v2 /v2 /takeownership
The following example uses the migration settings that are specified in the migconfig.xml file:
migprofile.exe migconfig.xml
The following example migrates the V1 profile for the user ts115 on the computer devvm-winxp to
the remote path \\file01\profiles. The utility takes ownership of the user profiles during the
migration:
migprofile.exe /s:\\devvm-winxp\c$\documents and settings\ts115
/t:\\file01\profiles\ /takeownership
VMware, Inc. 9
Horizon 7 User Profile Migration
The following example migrates the V2 profile for the user ts115 on the computer devvm-win7 to
the remote path \\file02\share\profiles. The utility takes ownership of the user profiles
during the migration:
migprofile.exe /s:\\devvm-win7\c$\Users\ts115.v2
/t:\\file02\share\profiles\ /v2 /takeownership
Migration Configuration File
You can specify a migration configuration file as a command-line option with the profile migration
command. In the configuration file, you can specify settings such as the source and target profile
locations, which are passed to the profile migration utility at runtime

The migration configuration file is optional. You can override settings that you specify in the
configuration file by typing the corresponding command-line options

Migration Configuration File Format
The migration configuration file is in XML format, which makes the file easy to read, edit, and
extend. For definitions of the settings, see Migration Configuration File Settings

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

source_profile_path





source_profile_path

true



target_profile_path



VMware, Inc. 10
Horizon 7 User Profile Migration




included_profile_folders
excluded_profile_folders




included_registry_keys
excluded_registry_keys



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.exe utility to take ownership of
the user profile during the migration. Use the following format:

..

If you do not specify this setting, the value defaults to "0", which turns off the takeownership
behavior

V1-to-V2 or V2-to-V5 Migration
Set the migv2tov5 setting to true to perform a V2-to-V5 profile migration. When you do not use
this setting, the utility performs a V1-to-V2 profile migration

Specify the migv2tov5 setting in the source tag. Use only one source tag in the configuration file

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

VMware, Inc. 11
Horizon 7 User Profile Migration
The following example specifies a V2-to-V5 profile migration:

source_profile_path
true

The following example specifies a V1-to-V2 profile migration:

source_profile_path

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. You can specify a single user's profile path or use the *
wildcard to migrate all profiles under a folder

The following examples specify individual remote user profiles:

\\file01\profiles\ts115


\\file02\share\profiles\ts115.v2
true

The following examples specify individual users' local profiles on existing machines:

\\devvm-winxp\c$\documents and settings\ts115


\\devvm-win7\c$\Users\ts115.v2
VMware, Inc. 12

If you are migrating to a V5 user profile, run the utility on a Windows 10 machine. If you are migrating to a V2 user profile, run the utility on a Windows 7, Windows 8 or 8.1, Windows …

Download Now

Documemt Updated

Popular Download

• › Homeownership Program Customer Intake Form Date
• › How To Submit A Service Desk Ticket Savannah State
• › How To Fill Out The I 9 Page 2 Authorized
• › Home Health Aide Duty Sheet Bluelinehccom
• › How To Organise Plan And Control Projects Govuk
• › High School Graphic Design Textbook Davis Art
• › How To Use Google Docs Resume Templates Putnam
• › How To Write A Research Briefing University Of
• › High Density Polyethylene Jm Eagle
• › Hsbcs Red Mastercard Rewards Catalogue
• › Helping Shape The Future Of Worklife Staples Inc
• › Hate Crime Brochure Template Attorney General Of
• › Healthy Children Children See Adults As Role Models Even At
• › How To Create A Legacy Society Brochure
• › Healthy Start City Of Philadelphia
• › Ho W T O Ma K E A Pu Rc H A S E O Rde R U S I N G Te M
• › How To Create Business Cards Manually In Wordperfect
• › Highly Effective School Library Program Action Plan
• › Home School Brochure Wilmington Christian
• › Hipaa Employee Confidentiality Agreement Eforms

Frequently Asked Questions

What do users want from horizon 7?

They might also occasionally work remotely. These users want a persistent user experience, and Horizon 7 can provide this experience using a combination of Horizon instant clones, App Volumes AppStacks and writable volumes, and Dynamic Environment Manager features such as personalization, folder redirection, and privilege elevation.

What is vmware horizon personalization?

In terms of VMware Horizon features, this capability is called personalization. Personalization of application settings is applicable regardless of whether your user segment calls for Horizon published applications or desktops. (For a discussion of this choice, see Applications or Desktops for a Particular Segment?)

Can i use horizon 7 enterprise edition to implement virtual desktop?

Much of the efficiency and automation potential of Horizon 7 is not possible using this approach. Horizon 7 Enterprise Edition includes several technologies for implementing modern virtual desktop and published-application solutions for a variety of user segments.

What is the horizon 7 published application service used for?

The Horizon 7 Published Application service is defined for the Static Task Worker use case in Horizon Use Case Services. This is a good example of a use case where a published application meets the needs of the end user. Horizon makes it easy to provision and manage RDSH servers and publish Windows applications.