Configure Omnissa UAG with Omnissa Horizon

Configure Omnissa UAG with Omnissa Horizon

In this post, I will show you step by step how to configure the Omnissa UAG (Unified Access Gateway) to work with Omnissa Horizon (formerly VMware Horizon).

Prerequisites

If you need to learn how, my post Install Horizon Connection Server details all the steps.

If you need to learn how, my post Install Omnissa Horizon Connection Server Certificate details all the steps.

If you need to learn how, my post Deploy Omnissa UAG on VMware vCenter details all the steps.

The Process

There are many settings on the UAG that we don’t need to configure.

If your domain ends with .local, it is recommended to use the IP instead of the FQDN.

In my example, my domain is dxt.local, so I will use the IP of my Horizon connection server. I will enter https://192.168.172.20:443.

In my example, the certificate algorithm I will use is SHA256, and the hash is c7a3e468d6d886e7c6e2d6e31dda609a357e719ef1. I will enter sha256=c7a3e468d6d886e7c6e2d6e31dda609a357e719ef1.

Blast is Horizon’s preferred remote connection method.

In my example, I will enter https://horizon.thedxt.ca:8443.

The UDP tunnel is used for poor connections.

The tunnel is used for RDP, USB, and multimedia redirection (MMR).

In my example, I will enter https://horizon.thedxt.ca:443.

It’s normal for Blast to take a bit longer than the others to come up.

For more details on installing a certificate on the UAG, see my blog post, Omnissa Unified Access Gateway Certificate Install.

In my example, the hostname is DXT-HO-UAG01. I will enter that.

For more information about the Omnissa Horizon locked.properties file, my blog post Omnissa Horizon locked.properties Settings goes into detail.

For more information on configuring the Omnissa UAG (Unified Access Gateway) to work with Omnissa Horizon, here is the Omnissa documentation.

Exit mobile version