5.2

n
Migrate user profiles from physical systems to View desktops.
n
Perform a staged migration from physical systems to View desktops.
n
Support up-to-date profiles when users go offline.
Limitations
View Persona Management has the following limitations and restrictions:
n
You must have a Horizon View license that includes the View Personal Management component.
n
View Persona Management requires a CIFS (Common Internet File System) share.
n
You cannot use View Persona Management with desktops that run in local mode.
n
A user cannot access the same profile if the user switches between desktops that have v1 user profiles and
v2 user profiles. However, redirected folders can be shared between v1 and v2 profiles. Windows XP uses
v1 profiles. Windows Vista, Windows 7, and Windows 8 use v2 profiles.
Benefits of Using View Desktops in Local Mode
With View Client with Local Mode, users can check out and download a View desktop to a local system such
as a laptop. Administrators can manage these local View desktops by setting policies for the frequency of
backups and contact with the server, access to USB devices, and permission to check in desktops.
For employees at remote offices with poor network connections, applications run faster on a local View desktop
than on a remote desktop. Also, users can use the local version of the desktop with or without a network
connection.
If a network connection is present on the client system, the desktop that is checked out continues to
communicate with View Connection Server to provide policy updates, and ensure that locally cached
authentication criteria is current. By default, contact is attempted every 6 minutes.
View desktops in local mode behave in the same way as their remote desktop equivalents, yet can take
advantage of local resources. Latency is eliminated, and performance is enhanced. Users can disconnect from
their local View desktop and log in again without connecting to the View Connection Server. After network
access is restored, or when the user is ready, the checked-out virtual machine can be backed up, rolled back,
or checked in.
Local resource
utilization
After a local desktop is checked out, it can take advantage of the memory and
CPU capabilities of the local system. For example, memory available beyond
what is required for the host and guest operating systems is usually split
between the host and the local View desktop, regardless of the memory settings
that are specified for the virtual machine in vCenter Server. Similarly, the local
View desktop can automatically use up to two CPUs available on the local
system, and you can configure the local desktop to use up to four CPUs.
Although a local desktop can take advantage of local resources, a Windows 8,
Windows 7, or Windows Vista View desktop that is created on an ESX/ESXi
3.5 host cannot produce 3D and Windows Aero effects. This limitation applies
even when the desktop is checked out for local use on a Windows 8, Windows
7, or Windows Vista host. Windows Aero and 3D effects are available only if
the View desktop is created using vSphere 4.x or later.
Conserving datacenter
resources by requiring
local mode
You can reduce datacenter costs associated with bandwidth, memory, and CPU
resources by requiring that View desktops be downloaded and used only in
local mode. This strategy is sometimes called a bring-your-own-PC program
for employees and contractors.
Chapter 2 Planning a Rich User Experience
VMware, Inc. 23