5.2

The data on each local system is encrypted with AES. 128-bit encryption is the default, but you can configure
192-bit or 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 Horizon 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
You cannot use View Persona Management with desktops that run in local mode.
n
Assigning application packages created with
VMware ThinApp is not supported for View desktops that
are downloaded and used in local mode. Rolling back a desktop might cause View Connection Server to
have incorrect information about the ThinApps on the rolled-back desktop.
n
For security reasons, you cannot access the host CD-ROM from within the View desktop.
n
Also for security reasons, you cannot copy and paste text or system objects such as files and folders between
the local system and the View desktop.
Overview of Setting Up a Local Desktop Deployment
To create and deploy View desktops in local mode, you must have the required license, set up a View Transfer
Server, use a desktop source managed by vCenter Server, and apply settings and policies specific to local mode.
When you create desktops that can be checked out for use on end users' local systems, in addition to the usual
setup tasks, you must complete several tasks for local mode.
1 Verify that you have a license for the VMware View with Local Mode component.
In View Administrator, go to View Configuration > Product licensing and usage.
2 Verify that the user account used to access vCenter Server from View Connection Server has the required
administrator privileges.
To see which user account is being used, in View Administrator, go to View Configuration > Servers,
select the vCenter Server, and click Edit.
The list of privileges required for vCenter Server operations is provided in the VMware Horizon View
Installation document, in the section about configuring user accounts for vCenter Server.
3 Install View Transfer Server in a virtual machine and add this server to a View Connection Server
configuration.
In View Administrator, go to View Configuration > Servers.
4 If you plan to use View Composer linked-clone desktops, configure a Transfer Server repository.
In View Administrator, go to View Configuration > Servers > Transfer Servers > Transfer Server
Repository.
5 If you plan to create a manual pool, verify that the desktop source is a virtual machine managed by vCenter
Server.
6 Create a virtual machine in vCenter Server to use as the desktop source.
If you create a virtual machine that has more virtual memory and processors than are available on a local
client system, the desktop can not be checked out, and an error message will appear.
Chapter 14 Managing Local Desktops
VMware, Inc. 305