Horizon Cloud with On-Premises Infrastructure is supported on specific hyper-converged infrastructure hardware.

The following hardware environments are supported.

Hyper-Converged Infrastructure

Requirements

vSAN Ready Node

A minimum of four servers and two 10GBASE uplinks per server are required for a production deployment. Check with your vendor to determine models recommended for Horizon Cloud with On-Premises Infrastructure.

Dell EMC VxRail

A minimum of one hardware appliance containing four servers where each server has two 10GBASE uplinks is required.

Installation and configuration of Horizon Cloud with On-Premises Infrastructure involves the following steps.

Networking Requirements

The following information about networks, addresses, host names, device names, and other items provides a consistent example for a vSAN Ready Node cluster. Use this information as both a guide for building this specific configuration and also as a reference or a blueprint when building clusters of increased size or resources.

See Appendix A - Static IP Addresses and Host Names for vSAN Ready Node Cluster Setup for a full list of static IP addresses, host names, and DNS domains used throughout the Horizon Cloud with On-Premises Infrastructure installation instructions.

When using a vSAN Ready Node cluster for your Horizon Cloud with On-Premises Infrastructure environment, ensure that cluster meets the following networking requirements.

Switch Configuration

  • Two 10GBASE switch ports are required per vSAN Ready Node. The steps in this guide reflect this minimum requirement. Additional 10GBASE connections can be used as desired to complement cluster performance and redundancy.

  • All switch ports used for the vSAN Ready Node cluster must have LACP disabled.

  • All switch ports used for the vSAN Ready Node cluster must provide access to the VLANs listed in the table that follows.

VLANs

The following table of VLAN IDs, prefix lengths, and routers provides a consistent reference example that applies throughout this guide. You are not required to use the numbering scheme verbatim, only to provide a functionally equivalent configuration tailored to the site.

VLAN

TYPE

PREFIX

ROUTER

USE

1000

routed

/24

172.16.0.1

Management network for the vSphere and Horizon Cloud with On-Premises Infrastructure infrastructure

1001

routed

/24

172.16.1.1

Desktop network used by the Horizon Cloud with On-Premises Infrastructure tenant software components and desktop virtual machines

4001

private

/24

none

vSAN

The VLAN used for vSAN traffic requires IGMP snooping and IGMP querier enabled.

4002

private

/24

none

vSphere vMotion

DNS

  • All systems on routed networks must use the FQDNs used during vSAN Ready Node cluster and Horizon Cloud with On-Premises Infrastructure configuration. Ensure that all host names resolve with forward and reverse lookups before proceeding.

  • The appliances deployed for the Horizon Cloud with On-Premises Infrastructure environment, such as the Horizon Air Link, must be able to resolve external host names, such as cloud.horizon.vmware.com, to contact the cloud service environment, Horizon Cloud.

NTP

All vSphere and Horizon Cloud with On-Premises Infrastructure systems require time synchronization over NTP. An accurate time source must be present and reachable by all systems.

Note:

In the example commands documented here for configuring a vSAN Ready Node cluster, IP address 172.16.1.3 (host name vrn-dc1) is used as the address for the DNS and NTP server settings for the ESXi hosts in the cluster. When a Horizon Cloud with On-Premises Infrastructure environment is deployed in the cluster, the deployment relies on having an Active Directory Domain Controller that meets configuration requirements that correspond to the configured DNS and NTP server settings, as outlined in Appendix B - Active Directory Details for vSAN Ready Node Cluster Setup. When you deploy the Horizon Cloud with On-Premises Infrastructure environment, ensure the Active Directory Domain Controller requirements are met.

Transparent Page Sharing

During deployment, Horizon Cloud with On-Premises Infrastructure enables the Transparent Page Sharing (TPS) configuration option in ESXi.

Deploying Horizon Cloud with On-Premises Infrastructure automatically changes the TPS configuration option in ESXi from the default setting of disabled to enabled. TPS is enabled to improve memory sharing between virtual machines, which increases the density of desktops per host. If you disable TPS, you might need to decrease the number of desktops you provision to the cluster to prevent a decrease in performance.

The Horizon Cloud with On-Premises Infrastructure capacity algorithms function with the assumption that TPS is enabled. If you disable TPS but deploy the full number of desktops recommended for provisioning, the host RAM might become overcommitted, resulting in poor desktop performance. Although RAM is often the limiting factor in virtual desktop infrastructure use cases, other factors, such as CPU and disk space, might limit the recommended desktop capacity. In such cases, disabling TPS might not impact the overall capacity of the node.

Therefore, you can disable TPS if necessary. See KB 2146823. However, Horizon Cloud with On-Premises Infrastructure performs best when TPS is enabled.