Architecture Planning
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 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 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
Virtual VMotion-
dvswitch (1 uplink per
host)
This switch was used by the ESXi hosts of infrastructure, parent, and desktop
virtual machines.
n
Jumbo Frame (9000 MTU)
n
1 Ephemeral Distributed Port Group
n
Private VLAN and 192.168.x.x addressing
Infra-dvswitch (2 uplink
per host)
This switch was used by the ESXi hosts of infrastructure virtual machines.
n
Jumbo frame (9000 MTU)
n
1 Ephemeral distributed port group
n
Infrastructure VLAN /24 (256 addresses)
Desktop-dvswitch (2
uplink per host)
This switch was used by the ESXi hosts of parent, and desktop virtual
machines.
n
Jumbo frame (9000 MTU)
n
6 Ephemeral distributed port groups
n
5 Desktop port groups (1 per pool)
n
Each network was /21, 2048 addresses
View Composer Performance Test Results
These test results describe a View 5.2 setup with 10,000-desktops, in which one vCenter Server 5.1 instance
managed 5 pools of 2,000 virtual machine desktops each. Only one maintenance period was required for
provisioning a new pool or for recomposing, refreshing, or rebalancing an existing pool of 2,000 virtual
machines. A logon storm of 10,000 users was also tested.
The test results provided here were accomplished with the software, hardware, and configuration settings
described in the following topics:
n
Desktop and pool configurations described in “View Connection Server Maximums and Virtual
Machine Configuration,” on page 55
n
Tiered-storage components described in “Shared Storage Example,” on page 59
n
Networking components described in “Network Bandwidth Considerations,” on page 62
Capacity for an Hour-Long Logon Storm of 10,000 Users
NOTE This example was used in a View 5.2 setup, which was carried out prior to the release of VMware
Virtual SAN. For guidance on sizing and designing the key components of View virtual desktop
infrastructures for VMware Virtual SAN, see the white paper at
http://www.vmware.com/files/pdf/products/vsan/VMW-TMD-Virt-SAN-Dsn-Szing-Guid-Horizon-
View.pdf. For test results with various workloads and View operations when using Virtual SAN, see the
reference architecture white paper at
http://www.vmware.com/files/pdf/techpaper/vmware-horizon-view-virtual-san-reference-architecture.pdf.
The Virtual SAN feature available with vSphere 6.0 and later releases contains many performance
improvements over the feature that was available with vSphere 5.5 Update 1. With vSphere 6.0 this feature
also has broader HCL (hardware compatibility) support. For more information about Virtual SAN in
vSphere 6 or later, see the Administering VMware Virtual SAN document.
In a test setup, the following desktop and pool configurations were used for a logon storm scenario for
10,000 desktops. The power policy for desktops was set to Always On.
View Architecture Planning
64 VMware, Inc.