6.0
Table Of Contents
- View Architecture Planning
- Contents
- View Architecture Planning
- Introduction to View
- Planning a Rich User Experience
- Feature Support Matrix for View Agent
- Choosing a Display Protocol
- Using Hosted Applications
- Using View Persona Management to Retain User Data and Settings
- Using USB Devices with Remote Desktops
- Using the Real-Time Audio-Video Feature for Webcams and Microphones
- Using 3D Graphics Applications
- Streaming Multimedia to a Remote Desktop
- Printing from a Remote Desktop
- Using Single Sign-On for Logging In to a Remote Desktop
- Using Multiple Monitors
- Managing Desktop and Application Pools from a Central Location
- Architecture Design Elements and Planning Guidelines for Remote Desktop Deployments
- Virtual Machine Requirements for Remote Desktops
- View ESXi Node
- Desktop Pools for Specific Types of Workers
- Desktop Virtual Machine Configuration
- RDS Host Virtual Machine Configuration
- vCenter Server and View Composer Virtual Machine Configuration
- View Connection Server Maximums and Virtual Machine Configuration
- vSphere Clusters
- Storage and Bandwidth Requirements
- View Building Blocks
- View Pods
- Advantages of Using Multiple vCenter Servers in a Pod
- Planning for Security Features
- Understanding Client Connections
- Choosing a User Authentication Method
- Restricting Remote Desktop Access
- Using Group Policy Settings to Secure Remote Desktops and Applications
- Implementing Best Practices to Secure Client Systems
- Assigning Administrator Roles
- Preparing to Use a Security Server
- Understanding View Communications Protocols
- Overview of Steps to Setting Up a View Environment
- Index
ESXi swap file
This file, which has a .vswp extension, is created if you reserve less than 100
percent of a virtual machine's RAM. The size of the swap file is equal to the
unreserved portion of guest RAM. For example, if 50 percent of guest RAM
is reserved and guest RAM is 2GB, the ESXi swap file is 1GB. This file can be
stored on the local data store on the ESXi host or cluster.
ESXi suspend file
This file, which has a .vmss extension, is created if you set the desktop pool
logoff policy so that the virtual desktop is suspended when the end user logs
off. The size of this file is equal to the size of guest RAM.
RAM Sizing for Specific Monitor Configurations When Using PCoIP
If you use PCoIP, the display protocol from VMware, the amount of extra RAM that the ESXi host requires
depends in part on the number of monitors configured for end users and on the display resolution. Table 4-1
lists the amount of overhead RAM required for various configurations. The amounts of memory listed in the
columns are in addition to the amount of memory required for other PCoIP functionality.
Table 4‑1. PCoIP Client Display Overhead
Display
Resolution
Standard Width, in Pixels Height, in Pixels
1-Monitor
Overhead
2-Monitor
Overhead
4-Monitor
Overhead
VGA 640 480 2.34MB 4.69MB 9.38MB
SVGA 800 600 3.66MB 7.32MB 14.65MB
720p 1280 720 7.03MB 14.65MB 28.13MB
UXGA 1600 1200 14.65MB 29.30MB 58.59MB
1080p 1920 1080 15.82MB 31.64MB 63.28MB
WUXGA 1920 1200 17.58MB 35.16MB 70.31MB
QXGA 2048 1536 24.00MB 48.00MB 96.00MB
WQXGA 2560 1600 31.25MB 62.50MB 125.00MB
When you consider these requirements, note that virtual machine configuration of allocated RAM does not
change. That is, you do not need to allocate 1GB of RAM for applications and another 31MB for dual 1080p
monitors. Instead, consider the overhead RAM when calculating the total physical RAM required for each
ESXi host. Add the guest operating system RAM to the overhead RAM and multiply by the number of
virtual machines.
IMPORTANT To use the 3D rendering feature, you must allocate sufficient VRAM for each Windows 7 or
later remote desktop.
n
The software-accelerated graphics feature, available with vSphere 5.0 and later, allows you to use 3D
applications such as Windows Aero themes or Google Earth. This features requires 11.8MB to 512MB
(for vSphere 5.1 U1 and later virtual machines) or 64MB (for vSphere 5.0 virtual machines). The default
is 64MB.
n
The Virtual Shared Graphics Acceleration (vSGA) feature, available with vSphere 5.1 and later, allows
multiple virtual machines to share the physical GPUs on the ESXi hosts. You can use 3D applications
for design, modeling, and multimedia. This feature requires 64MB to 512MB of VRAM. The default is
96MB.
n
The Virtual Dedicated Graphics Acceleration (vDGA) feature, available with vSphere 5.5 and later,
dedicates a single physical GPU (graphical processing unit) on an ESXi host to a single virtual machine.
This feature provides high-end, hardware accelerated workstation graphics.
When 3D rendering is enabled, the maximum number of monitors is 2 and the maximum resolution is 1920
x 1200.
View Architecture Planning
44 VMware, Inc.