5.0
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
PCoIP Secure Gateway connections are required if you use security servers for PCoIP connections from outside
the corporate network. Tunneled connections are required if you use security servers for RDP connections
from outside the corporate network and for USB and multimedia redirection (MMR) acceleration with a PCoIP
Secure Gateway connection. You can pair multiple security servers to a single connection server.
View Transfer Server Virtual Machine Configuration and Storage
View Transfer Server is required to support desktops that run View Client with Local Mode (formerly called
Offline Desktop). This server requires less memory than View Connection Server.
View Transfer Server Configuration
You must install View Transfer Server on a virtual rather than a physical machine and the virtual machine
must be managed by the same vCenter Server instance as the local desktops that it will manage. Table 4-8 lists
the virtual machine specifications for a View Transfer Server instance.
Table 4-8. View Transfer Server Virtual Machine Example
Item Example
Operating system 64-bit Windows Server 2008 R2
RAM 4GB
Virtual CPU 2
System disk capacity 20GB
Virtual SCSI adapter type LSI Logic Parallel (not the default, which is SAS)
Virtual network adapter E1000 (the default)
1 NIC 1 Gigabit
Storage and Bandwidth Requirements for View Transfer Server
Several operations use View Transfer Server to send data between the View desktop in vCenter Server and the
corresponding local desktop on the client system. When a user checks in or checks out a desktop, View Transfer
Server transfers the files between the datacenter and the local desktop. View Transfer Server also synchronizes
local desktops with the corresponding desktops in the datacenter by replicating user-generated changes to the
datacenter.
If you use View Composer linked-clones for local desktops, the disk drive on which you configure the Transfer
Server repository must have enough space to store your static image files. Image files are View Composer base
images. The faster your network storage disks are, the better performance will be. For information about
determining the size of base image files, see the VMware View Administration document.
Each Transfer Server instance can theoretically accommodate 60 concurrent disk operations, although network
bandwidth will likely be saturated at a lower number. VMware tested 20 concurrent disk operations, such as
20 clients downloading a local desktop at the same time, over a 1GB per second network connection.
vSphere Clusters
VMware View deployments can use VMware HA clusters to guard against physical server failures. Because
of View Composer limitations, the cluster must contain no more than 8 servers, or nodes.
VMware vSphere and vCenter provide a rich set of features for managing clusters of servers that host View
desktops. The cluster configuration is also important because each View desktop pool must be associated with
a vCenter resource pool. Therefore, the maximum number of desktops per pool is related to the number of
servers and virtual machines that you plan to run per cluster.
VMware View Architecture Planning
44 VMware, Inc.