When you install View Connection Server, the View Administrator user interface is also installed.

View Connection Server Configuration

Although you can install View Connection Server on a physical machine, this example uses a virtual machine with the specifications listed in 1. The ESXi host for this virtual machine can be part of a VMware HA cluster to guard against physical server failures.

Table 1. Connection Server Virtual Machine Example

Item

Example

Operating system

64-bit Windows Server 2008 R2 or Windows Server 2012 R2

RAM

10GB

Virtual CPU

4

System disk capacity

70GB

Virtual SCSI adapter type

LSI Logic SAS (the default for Windows Server 2008)

Virtual network adapter

VMXNET 3

Network adapter

1Gbps NIC

View Connection Server Cluster Design Considerations

You can deploy multiple replicated View Connection Server instances in a group to support load balancing and high availability. Groups of replicated instances are designed to support clustering within a LAN-connected single-datacenter environment.

Important:

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. 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. For more information, see Administering View Cloud Pod Architecture.

Maximum Connections for View Connection Server

2 provides information about the tested limits regarding the number of simultaneous connections that a View deployment can accommodate.

This example assumes that View Connection Server is running on a 64-bit Windows Server 2008 R2 Enterprise operating system.

Table 2. Remote Desktop Connections

Connection Servers per Deployment

Connection Type

Maximum Simultaneous Connections

1 Connection Server

Direct connection, RDP or PCoIP:

Tunneled connection, RDP:

PCoIP Secure Gateway connection:

2,000 (tested limit)

2,000 (hard limit)

2,000 (hard limit)

7 Connection Servers

Direct connection, RDP or PCoIP

10,000 (tested, and therefore supported, limit)

1 Connection Server

Unified Access to physical PCs

2,000

1 Connection Server

Unified Access to RDS hosts

2,000

1 Connection Server

Blast Secure Gateway connections to remote desktops using HTML Access

2,000 (tested limit)

PCoIP Secure Gateway connections are required if you use security servers or Access Point appliances for PCoIP connections from outside the corporate network. Tunneled connections are required if you use security servers or Access Point appliances for RDP connections from outside the corporate network and for USB and multimedia redirection (MMR) acceleration with a PCoIP Secure Gateway connection. You can pair multiple security servers to a single View Connection Server instance.

Although the maximum number of simultaneous connections to security servers is also 2,000, instead of using just one security server per View Connection Server instance (with 2,000 sessions), you might choose to use 2 or 4. Monitoring of the security server might indicate that the PCoIP activity for 2,000 users is too great. The required amount of memory and CPU usage might dictate that you add more security servers per View Connection Server instance to spread the load. For example, you might use 2 security servers, with each one handling 1,000 connections, or you might use 4 security servers, with each one handling 500 connections. The ratio of security servers to View Connection Server instances depends on the requirements of the particular environment.

The number of connections per Access Point appliance is similar to those for security servers. For more information about Access Point appliances, see Deploying and Configuring Access Point.

Note:

In this example, although 5 View Connection Server instances could handle 10,000 connections, the number 7 is shown in the table for availability planning purposes, to accommodate connections coming from both inside and outside of the corporate network.

For example, if you had 10,000 users, with 8,000 of them inside the corporate network, you would need 5 View Connection Server instances inside the corporate network. That way, if one of the instances became unavailable, the 4 remaining instances could handle the load. Similarly, for the 2,000 connections coming from outside the corporate network, you would use 2 View Connection Server instances so that if one became unavailable, you would still have one instance left that could handle the load.

.