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
The number of connections per Access Point appliance is similar to those for security servers. For more
information about Access Point appliances, see Deploying and Configuring Access Point.
NOTE In this example, although 5 View Connection Server instances could handle 10,000 connections, the
number 7 is shown in the table for availability planning purposes, to accommodate connections coming
from both inside and outside of the corporate network.
For example, if you had 10,000 users, with 8,000 of them inside the corporate network, you would need 5
View Connection Server instances inside the corporate network. That way, if one of the instances became
unavailable, the 4 remaining instances could handle the load. Similarly, for the 2,000 connections coming
from outside the corporate network, you would use 2 View Connection Server instances so that if one
became unavailable, you would still have one instance left that could handle the load.
Hardware Requirements for Access Point with Horizon View
VMware recommends to use 4 vCPUs and 10GB RAM for Access Point appliances to support maximum
number of connections when used with Horizon View.
Table 4‑8. Hardware Requirements for Access Point
Item Example
Operating system OVA (SUSE Linux Enterprise 12 (64-bit))
RAM 4GB
Virtual CPU 4
System disk capacity 20GB (changing the default log level requires additional
space)
Virtual SCSI adapter type LSI Logic Parallel (the default for OVA)
Virtual network adapter VMXNET 3
Network adapter 1Gbps NIC
Network Mapping Single NIC option
vSphere Clusters
View deployments can use VMware HA clusters to guard against physical server failures. Depending on
your setup, clusters can contain up to 32 nodes.
vSphere and vCenter Server provide a rich set of features for managing clusters of servers that host virtual
machine desktops. The cluster configuration is also important because each virtual machine desktop pool
must be associated with a vCenter Server 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.
In very large View deployments, vCenter Server performance and responsiveness can be improved by
having only one cluster object per datacenter object, which is not the default behavior. By default,
vCenter Server creates new clusters within the same datacenter object.
Under the following conditions, vSphere clusters can contain up to 32 ESXi hosts, or nodes:
n
vSphere 5.1 and later, with View Composer linked-clone pools, and store replica disks on NFS
datastores or VMFS5 or later datastores
n
vSphere 6.0 and later, and store pools on Virtual Volumes datastores
If you have vSphere 5.5 Update 1 and later, and store pools on Virtual SAN datastores, the vSphere clusters
can contain up to 20 ESXi hosts.
If you store View Composer replicas on a VMFS version earlier than VMFS5, a cluster can have at most eight
hosts. OS disks and persistent disks can be stored on NFS or VMFS datastores.
Chapter 4 Architecture Design Elements and Planning Guidelines for Remote Desktop Deployments
VMware, Inc. 63