You can install Horizon Connection Server either on a physical server or in a virtual machine.
Connection Server Configuration Example
This example uses a virtual machine with the specifications listed in Connection Server Virtual Machine Example. The ESXi host for this virtual machine can be part of a VMware HA cluster to guard against physical server failures.
Item | Example |
---|---|
Operating system | See supported operating systems in the Horizon Installation and Upgrade document. |
RAM | 10 GB |
Virtual CPU | 4 |
System disk capacity | 70 GB |
Virtual SCSI adapter type | Select either LSI Logic SAS or VMware Paravirtual (PVSCSI). Using PVSCSI may require more steps depending on the version of Windows you are installing. For more information, see the VMware Knowledge Base article Configuring disks to use VMware Paravirtual SCSI (PVSCSI) controllers (1010398). |
Virtual network adapter | VMXNET 3 |
Network adapter | 1 Gbps NIC |
Connection Server Cluster Design Considerations
You can deploy multiple replicated Connection Server instances in a group to support load balancing and high availability. Groups of replicated instances support clustering within a LAN-connected single-data-center environment.
Maximum Connections for Connection Server
VMware Configuration Maximums provides information about the tested limits regarding the number of simultaneous connections that a VMware Horizon deployment can accommodate.
PCoIP Secure Gateway connections are required if you use Unified Access Gateway appliances for PCoIP connections from outside the corporate network. Blast Secure Gateway connections are required if you use Unified Access Gateway appliances for Blast Extreme or HTML Access connections from outside the corporate network. Tunneled connections are required if you use Unified Access Gateway appliances for RDP connections from outside the corporate network and for USB and multimedia redirection (MMR) acceleration with a PCoIP or Blast Secure Gateway connection.
Although the Unified Access Gateway appliance can support a maximum of 2,000 simultaneous connections, you might decide to use 2 or 4. The required amount of memory and CPU usage might dictate that you add more Unified Access Gateway appliances per Connection Server instance to spread the load.
Although five Connection Server instances (suitably configured) can handle 20,000 connections, you might want to consider using six or seven Connection Servers for availability planning purposes, and to accommodate connections coming from both inside and outside of the corporate network.
For example, if you have 20,000 users, with 16,000 of them inside the corporate network, you need five Connection Server instances inside the corporate network. That way, if one of the instances became unavailable, the four remaining instances can handle the load. Similarly, for the 4,000 connections coming from outside the corporate network, you can use two Connection Server instances so if one becomes unavailable, you still have one instance left that can handle the load.
These numbers assume that external connections are presented through a gateway. In this example, each of the Connection Server instances handling external connections is paired with three Unified Access Gateway appliances, load balanced across both Connection Server instances, so that if one becomes unavailable, the two remaining appliances can handle the load.
In all cases, users need to reconnect if they are using a Connection Server or gateway that became unavailable.
Hardware Requirements for Unified Access Gateway with VMware Horizon
Item | Example |
---|---|
Operating system | OVA |
RAM | 4 GB |
Virtual CPU | 2 |
System disk capacity | 20 GB (Changing the default log level requires more space.) |
Virtual SCSI adapter type | LSI Logic Parallel (the default for OVA) |
Virtual network adapter | VMXNET 3 |
Network adapter | 1 Gbps NIC |
Network Mapping | Single NIC option |