Horizon 8 on Azure VMware Solution Configuration

This chapter is one of a series that make up the Omnissa Workspace ONE and Horizon Reference Architecture, a framework that provides guidance on the architecture, design considerations, and deployment of Omnissa Workspace ONE and Omnissa Horizon solutions. This chapter provides information about common configuration and deployment tasks for Omnissa Horizon 8 on Azure VMware Solution (referred to as AVS throughout this document).

A companion chapter, Horizon 8 on Azure VMware Solution Architecture, provides guidance on the architecture and design.

Deploying Horizon 8 with Azure VMware Solution

This section covers specific information for deploying Omnissa Horizon 8 on Azure VMware Solution (AVS). It contains separate guidance on the two supported deployment architectures, which are explained in Deployment Options.

• All-in-SDDC Architecture - A consolidated design with all the Horizon components located inside each SDDC.
• Federated Architecture – A design where the Horizon management components are located in Azure and the Horizon resources (desktops and RDS Hosts for published applications) are located in the AVS SDDCs.

At a high level, the following steps are required to deploy Horizon with AVS:

1. Create a Private Cloud. See the AVS documentation. The recommendation for a production environment is to use a minimum of three hosts in a cluster.
2. Deploy Horizon 8 on the AVS, following the architecture described in Scaling Deployments.
   • See the Horizon 8 documentation and Horizon Installation and Configuration.
   • See the Knowledge Base article Horizon on Azure VMware Solution (AVS) Support (80850) for features and versions supported on AVS.
3. Set up the Horizon environment on AVS.

SDDC Creation

Create a Private Cloud. See the AVS documentation. The recommendation for a production environment is to use a minimum of three hosts in a cluster.

Gather SDDC Credentials

1. Gather the VMware vCenter and VMware NSX URLs and credentials.
2. In the Azure Portal, go to Azure VMware Solution.
3. Go to your AVS Private cloud, then select VMware credentials under the Manage section of the middle menu.
4. Copy the vCenter Web Client URL, vCenter admin user, vCenter admin password, NSX Data Center Manager URL, NSX Manager admin user, and NSX Manager admin password.

All-in-SDDC Deployment

In an All-in-SDDC architecture deployment, all the Horizon components are located inside the AVS SDDC and run on vSphere. To prepare the SDDC, several tasks need to be completed before installing Horizon, including creating network segments and resource pools.

Create Network Segments

As covered in All-In-SDDC Architecture Networking, to allow for proper isolation of resources, several network segments need to be created inside the SDDC.

Figure 1: Network Diagram with All-In-SDDC Architecture (Subnets are for Illustrative Purposes Only)

Network segments can be added using the NSX-T admin console:

1. Select the Networking tab.
2. Using the left-hand menu, navigate to Connectivity > Segments.
3. Under Segments, select Add Segment.
4. Add segments for the following networks, defining a Segment Name and Subnet. The Type should be left as the default Routed.

• Add segments for External-DMZ, Internal-DMZ, Horizon-Management, VDI, and RDSH.
• For the VDI and RDSH segments, also launch and complete the Set DHCP Config wizard.

Create Resource Pools

Two vSphere resource groups are automatically created when the SDDC is created. It is recommended that the Compute-Resource Pool has child resource pools created in it to allow prioritization of the management servers and desktops/ RDS Hosts.

Figure 2: Resource Pools for All-in-SDDC Architecture of Horizon 8 on AVS

In the vSphere Client:

1. Click Menu and select Hosts and Clusters.
2. Browse to and expand vCenter > SDDC-Datacenter > Cluster-1 > Compute-ResourcePool.
3. Right-click and select New Resource Pool.
4. Create two new resource pools for Horizon-Management and Horizon-User.

See Managing Resource Pools for more information.

Window Server Template

To facilitate the creation of Windows servers for the various Horizon management components, either import an existing vSphere VM template or create a new VM and convert it to a template.

• Upload VM template or Windows Server ISO.
• Import customization specifications.

All-in-SDCC Firewall Rules

The firewall service on AVS is based on NSX and provides both Distributed (Micro-segmentation) and Gateway Firewall Services.

To simplify the management of the Gateway Firewall, it is recommended to use Groups (located under Networking & Security -- Inventory).

• Pre-create groups for your on-premises vSphere management components, VDI components, and applications to be accessible from Azure.
• Do the same for VDI components deployed in the AVS SDDC. Groups for vSphere management components are already pre-created. While creating a group, you need to specify IP addresses using CIDR notation.
• You can include a single host as a member by specifying a /32 mask or a continuous range of IPs using relevant CIDR (such as /24 to include all IPs within a 24-bit subnet).

Note: Default behavior of both Management and Gateway Firewall is set to deny all traffic not explicitly enabled.

External Horizon Traffic

There are different options for providing inbound traffic in Azure. In this reference architecture implementation, a Virtual WAN secured hub with Azure Firewall, with L4 and DNAT, was used. There are other options available for allowing inbound traffic. See the External Access to All-in-SDDC Deployments section of All-In-SDDC Architecture Networking.

External Horizon sessions connect through the Unified Access Gateways (UAGs). In the deployment carried out for this reference architecture, the Unified Access Gateways (UAGs) were configured using high availability (HA). When using UAG high availability, n+1 public IP addresses are required:

• One IP address for the load-balanced floating virtual IP address (VIP) used for the XML-API

• An additional one per Unified Access Gateway appliance for the secondary Horizon protocol traffic (Blast, PCoIP, tunnel)

The required number of public IP addresses were configured in the Azure Firewall Manager Virtual Hub. External DNS records were created for each these.

Azure Firewall Destination Network Address Translation (DNAT) rules were added to the Azure Firewall Policy to route and allow the required network ports from the public IP addresses to the UAG VIP and individual UAG appliances. To understand the required ports for Horizon 8, see Network Ports in Horizon 8.

Federated Deployment

In a federated architecture deployment, the Horizon management components are located in Azure.

Instance Types for Federated Deployment

The following table lists the Azure instances used based on a 2,000-desktop deployment example. Different Azure instance sizes can be used, although consideration should be given to the vCPU, memory, and expected network bandwidth available on the different instance sizes. This can have an impact on the number of sessions a management component can support. See Dsv4-series for details on other Azure instance sizes.

Table 1 gives example sizing for the server components that were used at the time of writing.

Table 1: Horizon Component Instance Types on Azure (Example)

*Size according to your environment

Connection Rules

Use the Azure portal to create an ExpressRoute in the vNet to connect to your on-premises management network. Finally, specify DNS server addresses for the management network.

Federated Firewall Rules

To set up a successful hybrid cloud deployment, you must follow these firewall rules. The following table describes firewall rules for the Azure vNet.

Table 2: Management Inbound Security Rules

Table 3: Management and Internal DMZ Outbound Security Rules

Table 4: Internal DMZ Inbound Security Rules

Table 5: External Inbound Security Rules

Table 6: External DMZ Outbound Security Rules

Federated Load Balancers

For redundancy, load balancers are used for Unified Access Gateways, Connection Servers, and App Volumes Managers. In Azure, when adding a load balancer, outbound NAT is no longer working for internal load balancers. As such, every component behind a load balancer also gets connected to an outbound-only load balancer for Internet access. Internet access is useful for certificate revocation list checking and updates.

Table 7: Load Balancer Rules Settings

Horizon 8 Installation

When you set up the Omnissa Horizon 8 environment on AVS, you must install and configure the following components:

1. Install Active Directory, DNS, DHCP, and KMS servers.
2. Optionally, install RDS license servers.
3. Install one or more Omnissa Horizon Connection Servers. See Connection Server Deployment.
4. Install one or more Omnissa Unified Access Gateways. See Unified Access Gateway Deployment.
5. Connect to Omnissa Horizon Cloud Service using either the Horizon Edge Gateway or the Horizon Cloud Connector. See Connecting to Horizon Cloud Service.

Connection Server Deployment

With Horizon 8, when deploying the first Connection Server in the SDDC, make sure to choose Azure as the deployment type. This sets the proper configuration and permissions on the Connection Server and Virtual Center. This choice is only made on the first Connection Server in a pod.

Figure 3: Horizon Connection Server Installation Platform Choice

• Version 8 2006 or later should be used.
• Optionally, install a Horizon event database on a Microsoft SQL Server.

Unified Access Gateway Deployment

Deploy Unified Access Gateway (UAG) appliances and connect them to the Connection Servers if your deployment supports external users.

• All-in-SDDC deployments - UAGs are deployed onto vSphere in the SDDC. Follow the  documentation and instructions in Deploying and Configuring Unified Access Gateway and the tutorial Deploying Unified Access Gateway on vSphere with Two NICs Through PowerShell.
• Federated deployments - UAGs are deployed into Microsoft Azure. Follow the documentation and instructions in PowerShell deployment to Microsoft Azure and the tutorial in Deploying Unified Access Gateway on Microsoft Azure.

Further deployment guidance can be found in Deployment Methods in the Unified Access Gateway Architecture chapter and in the Unified Access Gateway product page.

General deployment guidance:

• Use Unified Access Gateway version 20.06 or later.
• Use the PowerShell script to include the password and encode special characters in the INI configuration file. For more information, see the Unified Access Gateway documentation.
• Specify static routes for the NIC connected to the Internal DMZ and specify the appropriate RFC1918 networks with the Internal DMZ gateway.
  • For example: routes1=10.0.0.0/8 10.6.4.1,172.16.0.0/12 10.6.4.1,192.168.0.0/16 10.6.4.1
  • Where: 10.6.4.1 is the Internal DMZ gateway.

Connecting to Horizon Cloud Service

There are currently two versions of Omnissa Horizon Cloud Service. Depending on which you intend to connect the Horizon pod to, you will need to deploy the corresponding connector appliance, one per Horizon pod.

• Horizon Cloud Service - next-gen uses the Horizon Edge Gateway.
• First-gen Horizon Cloud Service uses the Horizon Cloud Connector.

Horizon Edge Gateway Deployment

To connect to the Horizon Cloud Service - next-gen, one Horizon Edge Gateway appliance is deployed per Horizon Pod. See the following documentation resources to assist in the Horizon Edge Gateway deployment:

• Onboarding for Horizon Cloud Service - next-gen Administrators
• Requirements Checklist for Deploying a Horizon 8 Edge
• Horizon 8 Edge Deployments
• Deploying a Horizon 8 Edge for Use with Horizon 8 Deployments and the Horizon Cloud - next-gen Control Plane

Horizon Cloud Connector Deployment

To connect to the first-gen Horizon Cloud Service, one Horizon Cloud Connector is deployed per Horizon Pod. For more information, see First-Gen Tenants - Onboarding a Horizon Pod to First-Gen Horizon Cloud Control Plane.

For the latest guidance on sizing the Horizon Cloud Connector when deploying on AVS, see Horizon 8 Pods with First-Gen Horizon Control Plane - Requirements Checklist - Starting November 2, 2023.

Deploying Horizon over Hybrid Cloud

You might already have Horizon environments on-premises or on another cloud platform. The Horizon pod on-premises and your Horizon 8 pod with AVS can be managed separately. Alternatively, you can extend your other Horizon environments by linking them with your Horizon with AVS environment using Cloud Pod Architecture (CPA). Deploying your Horizon environment over a hybrid cloud enables you to manage your on-premises deployment and your cloud deployment in a single federated space.

For hybrid cloud deployment, follow these steps.

1. Configure ExpressRoute and firewall rules to enable the Connection Server instance with AVS to communicate with the Connection Server instance on-premises.
2. Prepare Microsoft Active Directory (AD) and choose to set up a one-way trust or a two-way trust.
3. Ensure that your on-premises Horizon version is 7.5 or later.  
   Note: The Horizon version deployed on-premises does not have to match the Horizon version deployed on AVS. However, you cannot mix a Horizon 7.4 pod (or earlier) with a Horizon 8 or 7 pod within the same CPA.
4. Use Cloud Pod Architecture to connect the other Horizon pods against the Horizon pod with AVS.
5. For easy sharing of VM images and ISO images, you can use the vCenter Content Library on each vCenter Server.

Summary and Additional Resources

Now that you have come to the end of this configuration chapter on Omnissa Horizon 8 on Azure VMware Solution, you can return to the reference architecture landing page and use the tabs, search, or scroll to select further chapter in one of the following sections:

• Overview chapters provide understanding of business drivers, use cases, and service definitions.
• Architecture chapters give design guidance on the Omnissa products you are interested in including in your deployment, including Workspace ONE UEM, Access, Intelligence, Workspace ONE Assist, Horizon Cloud Service, Horizon 8, App Volumes, Dynamic Environment Manager, and Unified Access Gateway.
• Integration chapters cover the integration of products, components, and services you need to create the environment capable of delivering the services that you want to deliver to your users.
• Configuration chapters provide reference for specific tasks as you deploy your environment, such as installation, deployment, and configuration processes for Omnissa Workspace ONE, Horizon Cloud Service, Horizon 8, App Volumes, Dynamic Environment Management, and more.

Additional Resources

For more information about Horizon 8 on Azure VMware Solution, you can explore the following resources:

• Azure VMware Solution product page
• VMware Tech Zone page for Azure VMware Solution
• Deploying Horizon 8 on Azure VMware Solution

• Knowledge Base

Changelog

The following updates were made to this guide:

Author and Contributors

This chapter was written by:

• Hilko Lantinga is a Staff Engineer 2, Omnissa.
• Graeme Gordon is a Senior Staff Architect, Omnissa.

Feedback

Your feedback is valuable. To comment on this paper, either use the feedback button or contact us at tech_content_feedback@omnissa.com.