5.1
Table Of Contents
- VMware View Architecture Planning
- Contents
- VMware View Architecture Planning
- Introduction to VMware View
- Planning a Rich User Experience
- Feature Support Matrix
- Choosing a Display Protocol
- Using View Persona Management to Retain User Data and Settings
- Benefits of Using View Desktops in Local Mode
- Accessing USB Devices Connected to a Local Computer
- Printing from a View Desktop
- Streaming Multimedia to a View Desktop
- Using Single Sign-On for Logging In to a View Desktop
- Using Multiple Monitors with a View Desktop
- Managing Desktop Pools from a Central Location
- Architecture Design Elements and Planning Guidelines
- Virtual Machine Requirements
- VMware View ESX/ESXi Node
- Desktop Pools for Specific Types of Workers
- Desktop Virtual Machine Configuration
- vCenter and View Composer Virtual Machine Configuration and Desktop Pool Maximums
- View Connection Server Maximums and Virtual Machine Configuration
- View Transfer Server Virtual Machine Configuration and Storage
- vSphere Clusters
- VMware View Building Blocks
- VMware View Pod
- Planning for Security Features
- Understanding Client Connections
- Choosing a User Authentication Method
- Restricting View Desktop Access
- Using Group Policy Settings to Secure View Desktops
- Implementing Best Practices to Secure Client Systems
- Assigning Administrator Roles
- Preparing to Use a Security Server
- Understanding VMware View Communications Protocols
- Overview of Steps to Setting Up a VMware View Environment
- Index
Hardware Independence
Virtual machines are hardware-independent. Because a View desktop runs on a server in the datacenter and
is only accessed from a client device, a View desktop can use operating systems that might not be compatible
with the hardware of the client device.
For example, although Windows 7 can run only on Windows 7-enabled PCs, you can install Windows 7 in a
virtual machine and use that virtual machine on a PC that is not Windows 7-enabled.
Virtual desktops run on PCs, Macs, thin clients, PCs that have been repurposed as thin clients, iPads, and
Android devices such as tablets and Kindle Fire.
VMware View Features
Features included in VMware View support usability, security, centralized control, and scalability.
The following features provide a familiar experience for the end user:
n
On Microsoft Windows client devices, print from a virtual desktop to any local or networked printer that
is defined on the Windows client device. This virtual printer feature solves compatibility issues and does
not require you to install additional print drivers in a virtual machine.
n
On any client device, use the location-based printing feature to map to printers that are physically near
the client system. Location-based printing does require that you install print drivers in the virtual machine.
n
Use multiple monitors. With PCoIP multiple-monitor support, you can adjust the display resolution and
rotation separately for each monitor.
n
Access USB devices and other peripherals that are connected to the local device that displays your virtual
desktop.
You can specify which types of USB devices end users are allowed to connect to. For composite devices
that contain multiple types of devices, such as a video input device and a storage device, you can split the
device so that one device (for example, the video input device) is allowed but the other device (for example,
the storage device) is not.
n
Use View Persona Management to retain user settings and data between sessions even after the desktop
has been refreshed or recomposed. View Persona Management has the ability to replicate user profiles to
a remote profile store (CIFS share) at configurable intervals.
You can also use a standalone version of View Persona Management on physical computers and virtual
machines that are not managed by View.
VMware View offers the following security features, among others:
n
Use two-factor authentication, such as RSA SecurID or RADIUS (Remote Authentication Dial-In User
Service), or smart cards to log in.
n
Use pre-created Active Directory accounts when provisioning View desktops in environments that have
read-only access policies for Active Directory.
n
Use SSL tunneling to ensure that all connections are completely encrypted.
n
Use VMware High Availability to host desktops and to ensure automatic failover.
Scalability features depend on the VMware virtualization platform to manage both desktops and servers:
n
Integrate with VMware vSphere to achieve cost-effective densities, high levels of availability, and
advanced resource allocation control for your virtual desktops.
n
Use the View storage accelerator feature to support end-user logins at larger scales with the same storage
resources. This storage accelerator uses features in the vSphere 5 platform to create a host memory cache
of common block reads.
Chapter 1 Introduction to VMware View
VMware, Inc. 9