Node deployment and standard operations require specific types and sizes of virtual machines (VMs) in your Microsoft Azure cloud capacity. Your subscription needs the appropriate quotas and configuration to support these VMs.

The node deployment wizard validates that your Microsoft Azure environment has sufficient quota of cores to build the node.

Table 1. Horizon Cloud Node Virtual Machine Requirements

VM

Microsoft Azure VM Specification

Quantity

Description

Jumpbox

F-Series size:

Standard_F2 (2 cores, 4 GB memory)

1 per node

A VM created in your Microsoft Azure environment and used during initial node creation, and during subsequent software updates on the environment. One jumpbox VM for each node you deploy. This jumpbox VM is deleted automatically when the node creation or update process are finished and the VM is no longer needed.

Management node instances

Dv2-Series:

Standard_D2_v2 (2 cores, 7 GB memory)

1 per node during steady-state operations

2 per node while a software upgrade is being performed

Your environment needs to be sized to accommodate both these instances running during an upgrade process.

During steady-state operations, one VM exists, is powered on, and runs the node. When an upgrade is being performed on the node, an additional instance is created and powered on to run software updates on the environment. After the upgrade is completed, the node migrates to using the newly created VM for steady-state operations and the previous one is deleted.

Unified Access Gateway instances

Av2-Series:

Standard_A4_v2 (4 cores, 8 GB memory)

2 per node during steady-state operations

4 per node while a software upgrade is being performed

Unified Access Gateway is an optional feature that is deployed when you select Yes to have Internet-enabled desktops. If you choose to have Unified Access Gateway for the node, your environment needs to be sized to accommodate these instances running during an upgrade process.

During steady-state operations, two instances exist, are powered on, and provide the Unified Access Gateway capabilities. During an upgrade process, two additional instances are created and powered on to run the software updates on Unified Access Gateway. After the upgrade is completed, the node migrates to using the newly created instances and the previous ones are deleted.

Base image

You choose the sizes that you want to use for your base server images. Unless you want GPU-enabled desktops, D2_v2 is recommended for the base image.

To have server farms with GPU-enabled, use Standard_NV6 for your base image so that you can install the GPU drivers into it.

Varied, based on your needs

A base image is an RDS-enabled Microsoft Windows server operating system VM configured with the Horizon Agent and DaaS Agents. This VM provides the base that the environment then uses to create the RDSH farms that provide session-based desktops and remote applications to your end users. One VM is required per Microsoft Windows Server operating system.

The system automatically powers off the base image when it is published (when you perform the Convert to Image action on the base image in the Administration Console). When you update a published image, the system powers the VM on again.

RDSH farm

Options:

Dv2-Series:

  • Standard_D2_v2 (2 cores, 7 GB memory)

  • Standard_D3_v2 (4 cores, 14 GB memory)

  • Standard_D4_v2 (8 cores, 28 GB memory)

NV instances, GPU-enabled:

  • Standard_NV6 (6 cores, 56 GB memory, 1 GPU)

Note:

GPU-enabled VMs are only available in some Microsoft Azure regions. See Microsoft Azure Products by region for details.

Varied, based on your needs

RDSH farm VMs are the server instances that provide session-based desktops and remote applications to your end users. You need at least one RDSH farm to deliver session desktops and an additional farm to deliver remote applications. To meet administrator or end user needs, you can choose to deploy additional farms.

The power state of these VMs varies, depending on the farm configuration settings and the end user demand.