Architecture Planning

Although using one vCenter Server and one View Composer for 10,000 desktops is possible, doing so
creates a situation where there is a single point of failure. The loss of that single vCenter Server renders the
entire desktop deployment unavailable for power, provisioning, and refit operations. For this reason, choose
a deployment architecture that meets your requirements for overall component resiliency.
For this example, a 10,000-user pod consists of physical servers, a vSphere infrastructure, View servers,
shared storage, and 5 clusters of 2,000 virtual desktops per cluster.
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 or
application
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 desktop or application in the London data center.
Chapter 4 Architecture Design Elements and Planning Guidelines for Remote Desktop Deployments
VMware, Inc. 69