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 25 View pods to provide a single large desktop brokering and management environment for five geographically distant sites and provide desktops and applications for up to 50,000 sessions.
The following diagram is an example of a basic Cloud Pod Architecture topology.
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.
The Cloud Pod Architecture feature is not supported in an IPv6 environment. Kiosk mode clients are not supported in a Cloud Pod Architecture implementation. The restricted entitlements feature, which uses tag matching to determine whether a user can access a particular pool, does not work in a Cloud Pod Architecture implementation.
For more information, see Administering View Cloud Pod Architecture.