4.5

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 7
or Windows Vista View desktop that is created on an ESX 3.5 host cannot
produce 3-D and Windows Aero effects. This limitation applies even when the
desktop is checked out for local use on a Windows 7 or Windows Vista host.
Windows Aero and 3-D effects are available only if the View desktop is created
using vSphere 4.x.
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.
Check-outs
When the View desktop is checked out, the vCenter Server version of the
desktop is locked so that no other users can access it. When a View desktop is
locked, vCenter Server operations are disabled, including operations such as
powering on the online desktop, taking snapshots, and editing the virtual
machine settings. View administrators can, however, still monitor the local
session and access the vCenter Server version to remove access or roll back the
desktop.
Backups
During backups, the View desktop in vCenter Server is updated with all new
data and configurations, but the local desktop remains checked out on the local
system and the lock remains in place in vCenter Server.
Rollbacks
During rollbacks, the local View desktop is discarded and the lock is released
in vCenter Server. Future client connections are directed to the View desktop
in vCenter Server until the desktop is checked out again.
Check-ins
When a View desktop is checked in, the local desktop is uploaded to vCenter
Server, and the lock is released. Future client connections are directed to the
View desktop in vCenter Server until the desktop is checked out again.
The data on each local system is encrypted with AES. 128-bit encryption is the default, but you can configure
256-bit encryption. The desktop has a lifetime controlled through policy. If the client loses contact with View
Connection Server, the maximum time without server contact is the period in which the user can continue to
use the desktop before the user is refused access. Similarly, if user access is removed, the client system becomes
inaccessible when the cache expires or after the client detects this change through View Connection Server.
View Client with Local Mode has the following limitations and restrictions:
n
You must have a View license that includes the Local Mode component.
n
End users cannot access their local desktop while rollbacks and check-ins are taking place.
n
This feature is available only for virtual machines that are managed by vCenter Server.
n
Assigning application packages created with VMware ThinApp is not supported on local desktops.
VMware View Administrator's Guide
212 VMware, Inc.