6.1
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
Table 4‑12. Example of a LAN-Based View Pod with One vCenter Server
Item Example
vSphere clusters 6 (5 clusters with one linked-clone pool per cluster, and 1
infrastructure cluster)
vCenter Server 1
View Composer 1 (standalone)
Database server 1 (standalone) MS SQL Server or Oracle database server
Active Directory server 1 or 2
View Connection Server instances 5
Security servers 5
vLANs 8 (5 for the desktop pool clusters, and 1 each for
management, VMotion, and the infrastructure cluster)
Cloud Pod Architecture Overview
To use a group of replicated View Connection Server instances across a WAN, MAN (metropolitan area
network), or other non-LAN, in scenarios where a View deployment needs to span datacenters, you must
use the Cloud Pod Architecture feature.
This feature uses standard View components to provide cross-datacenter administration, global and flexible
user-to-desktop mapping, high-availability desktops, and disaster recovery capabilities. You can link
together four View pods to provide a single large desktop brokering and management environment for two
geographically distant sites and manage up to 20,000 remote desktops.
The following diagram is an example of a basic Cloud Pod Architecture topology.
Security
Server
User
View
Connection
Server
View
Connection
Server
Security
Server
View
Connection
Server
View
Connection
Server
Security
Server
Security
Server
London Pod
London Datacenter
Interpod
communication
Remote
desktop
New York Pod
New York Datacenter
Global Data Layer
In the example topology, two previously standalone View pods in different datacenters are joined together
to form a single pod federation. An end user in this environment can connect to a View Connection Server
instance in the New York datacenter and receive a session on a desktop in the London data center.
This feature has the following limitations:
n
It does not support using the HTML Access feature. With HTML Access, end users can use a Web
browser to connect to remote desktops and are not required to install any client software on their local
systems.
n
It does not support using remote Windows-based applications hosted on a Microsoft RDS host.
n
It is not supported in an IPv6 environment.
For more information, see Administering View Cloud Pod Architecture.
View Architecture Planning
66 VMware, Inc.