5.2

n
You must create the full profile path under which the user profile folders will be created. If part of the
path
does not exist, Windows creates the missing folders when the first user logs in and assigns the user's
security restrictions to those folders. Windows assigns the same security restrictions to every folder it
creates under that path.
For example, for user1 you might configure the View Persona Management
path \\server\VPRepository\profiles\user1. If you create the network share \\server\VPRepository,
and the profiles folder does not exist, Windows creates the path \profiles\user1 when user1 logs in.
Windows restricts access to the \profiles\user1 folders to the user1 account. If another user logs in with
a profile path in \\server\VPRepository\profiles, the second user cannot access the repository and the
user's profile fails to be replicated.
Install View Agent with the View Persona Management Option
To use View Persona Management with View desktops, you must install View Agent with the View Persona
Management setup option on the virtual machines that you use to create desktop pools.
For an automated pool, you install View Agent with the View Persona Management setup option on the virtual
machine that you use as a parent or template. When you create a desktop pool from the virtual machine, the
View Persona Management software is deployed on your View desktops.
For a manual pool, you must install View Agent with the View Persona Management setup option on each
virtual machine that is used as a desktop source in the pool. Use Active Directory to configure View Persona
Management group policies for a manual pool. The alternative is to add the ADM Template file and configure
group policies on each individual desktop source.
NOTE A user cannot access the same profile if the user switches between desktops that have v1 user profiles
and v2 user profiles. Windows XP uses v1 profiles. Windows 8 and Windows 7 use v2 profiles.
For example, if a user logs in to a Windows XP desktop and later logs in to a Windows 7 desktop, the Windows
7 virtual machine cannot read the v1 profile that was created during the Windows XP desktop session.
You can use the View profile migration command-line utility to migrate Windows XP profiles to Windows 7
or Windows 8 profiles. See the Vmware Horizon View User Profile Migration document.
Prerequisites
n
Verify
that you are performing the installation on a Windows 8, Windows 7, Windows Vista, or Windows
XP virtual machine. View Persona Management does not operate on Microsoft Terminal Servers.
Installing View Agent with the View Persona Management setup option does not work on physical
computers. You can install the standalone View Persona Management software on physical computers.
See “Install Standalone View Persona Management,” on page 235.
n
Verify that you can log in as an administrator on the virtual machine.
n
Verify that a native RTO Virtual Profiles 2.0 is not installed on the virtual machine. If a native RTO Virtual
Profile 2.0 is present, uninstall it before you install View Agent with the View Persona Management setup
option.
n
On Windows XP virtual machines, download and install the Microsoft User Profile Hive Cleanup Service
(UPHClean) in the guest operating system. See “Installing UPHClean on Windows XP Desktops That Use
View Persona Management,” on page 235.
n
Familiarize yourself with installing View Agent. See “Install View Agent on a Virtual Machine,” on
page 64 or “Install View Agent on an Unmanaged Desktop Source,” on page 55.
Procedure
u
When you install View Agent on a virtual machine, select the View Persona Management setup option.
VMware Horizon View Administration
234 VMware, Inc.