5.2

Managing Local Desktops 14
To manage desktops that are used in local mode, you must set up the environment so that data is transferred
when users check View desktops out to their local systems. You must also manage other tasks where data
transfer
occurs, such as desktop check-in, rollback, and backup, and set policies for which of these actions users
can initiate.
This chapter includes the following topics:
n
“Benefits of Using View Desktops in Local Mode,” on page 303
n
“Managing View Transfer Server,” on page 309
n
“Managing the Transfer Server Repository,” on page 313
n
“Managing Data Transfers,” on page 319
n
“Configure Security and Optimization for Local Desktop Operations,” on page 323
n
“Configuring Endpoint Resource Usage,” on page 328
n
“Configuring an HTTP Cache to Provision Local Desktops Over a WAN,” on page 332
n
“Configuring the Heartbeat Interval for Local Desktop Client Computers,” on page 336
n
“Manually Downloading a Local Desktop to a Location with Poor Network Connections,” on
page 337
n
“Troubleshooting View Transfer Server and Local Desktop Operations,” on page 340
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.
VMware, Inc. 303