7.0
Table Of Contents
- View Architecture Planning
- Contents
- View Architecture Planning
- Introduction to View
- Planning a Rich User Experience
- Feature Support Matrix for Horizon Agent
- Choosing a Display Protocol
- Using Hosted Applications
- Using View Persona Management to Retain User Data and Settings
- Using USB Devices with Remote Desktops and Applications
- 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
- Monitors and Screen Resolution
- Managing Desktop and Application Pools from a Central Location
- Advantages of Desktop Pools
- Advantages of Application Pools
- Reducing and Managing Storage Requirements
- Application Provisioning
- Deploying Individual Applications Using an RDS Host
- Deploying Applications and System Updates with View Composer
- Deploying Applications and System Updates with Instant Clones
- Managing VMware ThinApp Applications in View Administrator
- Deploying and Managing Applications Using App Volumes
- Using Existing Processes or VMware Mirage for Application Provisioning
- Using Active Directory GPOs to Manage Users and Desktops
- 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
- Using Smart Policies
- 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 or Blast
Extreme
In addition to system memory, a virtual machine also requires a small amount of RAM on the ESXi host for
video overhead. This VRAM size requirement depends in on the display resolution and number of monitors
configured for end users. 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 or Blast Extreme functionality.
Table 4‑1. PCoIP or Blast Extreme Client Display Overhead
Display
Resolution
Standard
Width, in
Pixels
Height, in
Pixels
1-Monitor
Overhead
2-Monitor
Overhead
3-Monitor
Overhead
4-Monitor
Overhead
VGA 640 480 1.20MB 3.20MB 4.80MB 5.60MB
WXGA 1280 800 4.00MB 12.50MB 18.75MB 25.00MB
1080p 1920 1080 8.00MB 25.40MB 38.00MB 50.60MB
WQXGA 2560 1600 16.00MB 60.00MB 84.80MB 109.60MB
UHD (4K) 3840 2160 32.00MB 78.00MB 124.00MB Not supported
For calculating system requirements, the VRAM values are in addition to the base system RAM for the
virtual machine. Overhead memory is automatically calculated and configured when you specify the
maximum number of monitors and select the display resolution in View Administrator.
If you use the 3D rendering feature and select Soft3D or vSGA, you can recalculate using the additional
VRAM values in a View Administrator control for configuring VRAM for 3D guests. Alternatively, and for
other types of graphics acceleration besides Soft3D and vSGA, you can specify the exact amount of VRAM if
you elect to manage VRAM by using vSphere Client.
By default, the multiple-monitor configuration matches the host topology. There is extra overhead
precalcuated for more than 2 monitors to accommodate additional topology schemes. If you encounter a
black screen when starting a remote desktop session, verify that the values for the number of monitors and
the display resolution, which are set in View Administrator, match the host system, or manually adjust the
amount of memory by using selecting Manage using vSphere Client in View Administrator and then set
the total video memory value to maximum of 128MB.
RAM Sizing for Specific Workloads and Operating Systems
Because the amount of RAM required can vary widely, depending on the type of worker, many companies
conduct a pilot phase to determine the correct setting for various pools of workers in their enterprise.
A good starting point is to allocate 1GB for 32-bit Windows 7 or later desktops and 2GB for 64-bit
Windows 7 or later desktops. If you want to use one of the hardware accelerated graphics features for 3D
workloads, VMware recommends 2 virtual CPUs and 4GB of RAM. During a pilot, monitor the performance
and disk space used with various types of workers and make adjustments until you find the optimal setting
for each pool of workers.
View Architecture Planning
52 VMware, Inc.