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
Estimating Memory Requirements for Virtual Machine Desktops
RAM costs more for servers than it does for PCs. Because the cost of RAM is a high percentage of overall
server hardware costs and total storage capacity needed, determining the correct memory allocation is
crucial to planning your desktop deployment.
If the RAM allocation is too low, storage I/O can be negatively affected because too much Windows paging
occurs. If the RAM allocation is too high, storage capacity can be negatively affected because the paging file
in the guest operating system and the swap and suspend files for each virtual machine grow too large.
RAM Sizing Impact on Performance
When allocating RAM, avoid choosing an overly conservative setting. Take the following considerations
into account:
n
Insufficient RAM allocations can cause excessive Windows paging, which can generate I/O that causes
significant performance degradations and increases storage I/O load.
n
VMware ESXi supports sophisticated memory resource management algorithms such as transparent
page sharing and memory ballooning, which can significantly reduce the physical RAM needed to
support a given guest RAM allocation. For example, even though 2GB might be allocated to a virtual
desktop, only a fraction of that number is consumed in physical RAM.
n
Because virtual desktop performance is sensitive to response times, on the ESXi host, set nonzero values
for RAM reservation settings. Reserving some RAM guarantees that idle but in-use desktops are never
completely swapped out to disk. It can also reduce storage space consumed by ESXi swap files.
However, higher reservation settings affect your ability to overcommit memory on an ESXi host and
might affect VMotion maintenance operations.
RAM Sizing Impact on Storage
The amount of RAM that you allocate to a virtual machine is directly related to the size of the certain files
that the virtual machine uses. To access the files in the following list, use the Windows guest operating
system to locate the Windows page and hibernate files, and use the ESXi host's file system to locate the ESXi
swap and suspend files.
Windows page file
By default, this file is sized at 150 percent of guest RAM. This file, which is
by default located at C:\pagefile.sys, causes thin-provisioned storage to
grow because it is accessed frequently. On View Composer linked-clone
virtual machines, the page file and temporary files can be redirected to a
separate virtual disk that is deleted when the virtual machines are powered
off. Disposable page-file redirection saves storage, slowing the growth of
linked clones and also can improve performance. Although you can adjust
the size from within Windows, doing so might have a negative effect on
application performance.
For instant clones, any guest operating systems paging and temp files are
automatically deleted during the logoff operation and so do not have time to
grow very large. Each time a user logs out of an instant clone desktop, View
deletes the clone, and provisions and powers on another instant clone based
on the latest OS image available for the pool.
Windows hibernate file
for laptops
This file can equal 100 percent of guest RAM. You can safely delete this file
because it is not needed in View deployments.
Chapter 4 Architecture Design Elements and Planning Guidelines for Remote Desktop Deployments
VMware, Inc. 51