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
Table 4-4. Desktop Virtual Machine Example for Windows 7, on an ESX/ESXi 4.1 or Later Host (Continued)
Item Example
Virtual SCSI adapter type LSI Logic SAS (the default)
Virtual network adapter VMXNET 3
(To use this adapter, you must install Microsoft hotfix patch
http://support.microsoft.com/kb/2550978 for Windows 7 SP1
or http://support.microsoft.com/kb/2344941 for previous
versions.)
vCenter and View Composer Virtual Machine Configuration and
Desktop Pool Maximums
You install both vCenter Server and View Composer on the same virtual machine. Because this virtual machine
is a server, it requires much more memory and processing power than a desktop virtual machine.
View Composer can create and provision up to 1,000 desktops per pool if you are using vSphere 4.1 or later.
View Composer can also perform a recompose operation on up to 1,000 desktops at a time. Desktop pool size
is limited by the following factors:
n
Each desktop pool can contain only one ESX/ESXi cluster.
n
Each ESX/ESXi cluster can contain no more than 8 ESX/ESXi hosts.
n
Each CPU core has compute capacity for 8 to 10 virtual desktops.
n
The number of IP addresses available for the subnet limits the number of desktops in the pool. For example,
if your network is set up so that the subnet for the pool contains only 256 usable IP addresses, the pool
size is limited to 256 desktops.
Although you can install vCenter Server and View Composer on a physical machine, this example uses a virtual
machine with the specifications listed in Table 4-5. The ESX/ESXi host for this virtual machine can be part of
a VMware HA cluster to guard against physical server failures.
This example assumes that you are using VMware View with vSphere 4.1 or later and vCenter Server 4.1 or
later.
Table 4-5. vCenter Server Virtual Machine Example and Pool Size Maximum
Item Example
Operating system 64-bit Windows Server 2008 R2 Enterprise
RAM 4 GB
Virtual CPU 2
System disk capacity 40GB
Virtual SCSI adapter type LSI Logic SAS (the default for Windows Server 2008)
Virtual network adapter E1000 (the default)
Maximum View Composer pool size 1,000 desktops
IMPORTANT VMware recommends that you place the database to which vCenter and View Composer connect
on a separate virtual machine.
VMware View Architecture Planning
42 VMware, Inc.