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.
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 datacenter.
This feature has the following limitations:
This release 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.
This release does not support using remote Windows-based applications hosted on a Microsoft RDS host.
For more information, see Administering View Cloud Pod Architecture.