Accessing Usb Devices Connected To A Local Computer - VMware VIEW 4.5 - ARCHITECTURE PLANNING EN-000350-01 Manual

View architecture planning guide
Table of Contents

Advertisement

Conserving datacenter
resources by requiring
local mode
Check-outs
Backups
Rollbacks
Check-ins
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:
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.
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
n
the local system and the View desktop.

Accessing USB Devices Connected to a Local Computer

Administrators can configure the ability to use USB devices, such as thumb flash drives, VoIP (voice-over-IP)
devices, and printers, from a View desktop. This feature is called USB redirection.
When you use this feature, most USB devices that are attached to the local client system become available from
a menu in View Client. You use the menu to connect and disconnect the devices.
VMware, Inc.
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 3D 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 3D effects are available only if the View desktop is created
using vSphere 4.x.
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.
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.
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.
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.
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.
Chapter 2 Planning a Rich User Experience
19

Advertisement

Table of Contents
loading

This manual is also suitable for:

View 4.5 - architectureView composer 2.5View manager 4.5

Table of Contents