In 2013 I created a blog post with some tips for implementing a VMware Horizon View Security Server (link)”. Now the Unified Access Gateway (UAG) is replacing the VMware Security Server. So it’s time for a new blog post with some implementation tips about VMware Access Point / Unified Access Gateway (UAG). Here’s an overview of the tips:
- The Unified Access Gateway (UAG) provides secure access to the following environments:
- VMware Horizon desktops and applications
- VMware Identity Manager
- VMware AirWatch or VMware Workspace ONE per-app tunnels and tunnel proxy
- VMware Content Gateway service to allow VMware Content Locker access to internal file shares and Microsoft SharePoint
- In version 2.9 Access Point is renamed to Unified Access Gateway (UAG)
- UAG is included in the Horizon standard, advanced and enterprise license
- The use cases listed above can be mixed on the same UAG or seperated on multiple UAGs
- UAG 2.9 supports Horizon 6.2.3, 6.2.4 and 7.1.0
- UAG includes some improvements (such as blast Extreme) that are not available in the Horizon Security Server
- UAG is deployed in the DMZ and replaces the Horizon Security Server (Windows based)
- UAG is packaged as an OVF. It’s a hardened Linux appliance based on SUSE Enterprise Linux. So there no need for Windows OSes in the DMZ which improves security!
- Hardware specifications for the UAG are:
- 2 vCPU
- 4 GB memory
- 20 GB harddisk
- 1,2 or 3 Network adapters
- Create an IP pool before deploying the UAG
- Below is an overview of the VMware UAG firewall ports configuration:
The documentation about the the firewall ports can be found here.
(*1) When using Blast Extreme over port 443, port 8443 is not needed
- The administration user interface (UI) can be used to set up and manage the Unified Access Gateway environment. To access to the management interface go to: https://ipaddress:9443/admin
- Upgrading UAG is not supported. Install a new appliance. It’s highly recommend to create a PowerShell script for the deployment that can be used everytime when installinging a new UAG.
- When deploying UAG using PowerShell, download the latest deployment scripts, link
- The following certificates can be used:
- Single-Server Name Certificate
- Subject Alternative Name (SAN)
- Wildcard Certificate
- Convert the certificate into PEM-format files for the certificate chain and the private key, then convert the .pem files to a one-line format that includes embedded newline characters
- If your certificate is in PKCS#12 (.p12 or .pfx) format, or after the certificate is converted to PKCS#12 format, use Openssl to convert the certificate to .pem files
- There is NO need to pair Horizon Connection Servers with Access Point or UAG. Uncheck the boxes in the Connection Server:
- Before configuring Radius authentication, first test if PCoIP and Blast access works:
- Test a native Horizon Client using PCoIP.
Test a native Horizon Client using Blast.
Test the HTML Access Client (which also uses Blast)
- Test a native Horizon Client using PCoIP.
- Some browsers have problems with Client HTML access (link). To solve this problem change the checkorigin property.
- On each Horizon Connection Server
- Add a line in the “locked.properties” file (C:\Program Files\VMware\VMware View\Server\sslgateway\conf)
- Restart the VMware Horizon View Connection Server service.
I prefer the create a PowerShell script for the deployment of the UAG. This script deploys a single UAG with a single NIC and provide secure access to the Horizon View environment. The certificate will be generated automatically and is self-signed (in production environments use an signed certificate).
When re-deploying an UAG with PowerShell there is no need to manually remove the appliance. When the config is the same the old appliance is automatically removed.
Before using PowerShell make sure the following requirements are met, link.
[General] # # UAG virtual appliance unique name (between 1 and 32 characters). # If name is not specified, the script will prompt for it. # name=UAG01 # # Full path filename of the UAG .ova virtual machine image # The file can be obtained from VMware # source=C:\temp\euc-access-point-22.214.171.124-5202536_OVF10.ova # # target refers to the vCenter username and address/hostname and the ESXi host for deployment # Refer to the ovftool documentation for information about the target syntax. # See https://www.vmware.com/support/developer/ovf/ # PASSWORD in upper case results in a password prompt during deployment so that passwords do not need # to specified in this .INI file. # In this example, the vCenter username is email@example.com # the vCenter server is 192.168.0.21 (this can be a hostname or IP address) # the ESXi hostname is esx1.myco.int (this can be a hostname or IP address) # target=vi://firstname.lastname@example.org:PASSWORD@192.168.250.30/dc-beerens-01/host/mgnt # # vSphere datastore name # ds=NFS-01 # # vSphere Network names. A vSphere Network Protocol Profile must be associated with every referenced network name. This specifies # network settings such as IPv4 subnet mask, gateway etc. # netInternet=dmz-vlan100 netManagementNetwork=dmz-vlan100 netBackendNetwork=dmz-vlan100 deploymentOption=onenic ip0=192.168.250.32 netmask0=255.255.255.0 dns=192.168.250.2 #syslogUrl=syslog://server.example.com:514 # # Setting honorCipherOrder to true forces the TLS cipher order to be the order specified by the server. This can be set on # UAG 2.7.2 and newer to force the Forward Secrecy ciphers to be presented first to improve security. # honorCipherOrder=true [Horizon] # # proxyDestinationUrl refers to the backend Connection Server to which this UAG appliance will connect. # It can either specify the name or IP address of an individual Connection Server or of a load balanced alias to connect # via a load balancer in front of multiple Connection Servers. # proxyDestinationUrl=https://192.168.250.71 # # proxyDestinationUrlThumbprints only needs to be specified if the backend Connection Servers do not have # a trusted CA signed SSL server certificate installed (e.g. if it has the default self-signed certificate only). # This is a comma separated list of thumbprints in the format shown here. # proxyDestinationUrlThumbprints=sha1:f1 c2 b8 0a 3f 7b 87 df 33 96 22 49 66 40 70 1a 11 74 9e b1 tunnelExternalUrl=https://vdi.ivobeerens.nl:443 blastExternalUrl=https://vdi.ivobeerens.nl:443 # # pcoipExternalUrl must contain an IPv4 address (not a DNS name) # pcoipExternalUrl=126.96.36.199:4172
- name: The name of the Unified Access Gateway (UAG)
- source: The location of the OVF file
- target: Specifies the vCenter Server information and target ESX host.
- ds: datastore to deploy the UAG
- vSphere Network names: This section contains the network settings such as:
- IP Address
- Amount of NICs
- DNS server(s)
- honorCipherOrder: This allows forward secrecy ciphers to be presented first in the cipher list to improve security.
- proxyDestinationUrl: URL representing the Horizon backend server (internal Connection server)
- proxyDestinationUrlThumbprints: This contains the thumbprint of the Connection Server
- tunnelExternalUrl: URL used by Horizon Clients to connect the secure tunnel to this UAG appliance
- blastExternalUrl: URL used by HTML Access Clients to connect to this UAG appliance
- pcoipExternalUrl: URL used by Horizon Clients to connect using PCoIP to this UAG appliance (external IP address)
When the UAG deployment successfully executes other configuration (UI or PowerShell) options can be added such as:
- Trusted certificates
- Radius authentication
- Identity Manager
5 thoughts on “Horizon Access Point / Unified Access Gateway (UAG) implementation tips”
Thanks for this clear post!
One thing I don’t understand is why the Secure Gateways have to be disabled on the Connection Server.
In our old configuration we’ve had a Security Server in the DMZ with our external URLs configured (as secure gatewyas, like vdi-external.domain.com).
The connection server also had the secure gateway enabled but with internal URLs (like vdi-internal.domain.com).
Last weekend we’ve uninstalled the Security Server and replaced it with the VMware UAG 3.0 Appliance and followed your blog to configure this. The UAG is working fine and all external connections are possible (HTML Access through UAG, PCoIP and Blast).
Interal Blast and PCoIP connection to the Connection Server with the client are also possible, but the HTML Access through the webpage of the connection server tries to deliver a certificate named “BLAST” while trying to connect to the direct IP address of the Horizon VDI machine (linked clone).
In the previous configuration with the Security server we didn’t had this problem because the Blast Secure Gateway was enabled on the Connection Server. Now since we switched the Blast Secure Gateway off in the Connection Server it seems that the HTML Access Blast connection are made directly to the VDI machines.
Is it really nessacery to disable the Secure Gateways inside the Connection Server?
I’m a bit late, but I’ve always been curious about the same thing… I believe your comment about the security certificates is unrelated, but I do understand the issue you’re having with disabling the gateways.
When I first started using the UAG’s, I had issues getting anything to work at all until I disabled the gateways on the Connection Server. But even after disabling it, I notice that it still works, so I have no idea what this change is, or if it’s even required?
I couldn’t find anything in the VMware documentation.
In addition to my previous comment, I just found this.
Quote: “Disable the secure gateways (Blast Secure Gateway and PCoIP Secure Gateway) on Horizon
Connection Server instances and enable these gateways on the Unified Access Gateway appliances.”
I guess we are supposed to do this.
You’re issue is a certificate issue I believe.
today was my first UAG Installation and this ended with big disappointment: I had a lot of problems: two of the were very strange – if I set up Edge nad Horizon Configuration, everything is green but the destination Server red – Down! We opened Firewall completly to be sure, ther is no failure config. But it stays still red.
The second strange thing was, if I configure RSA Secure ID and save the configuration it’s showing me a message like “Your password is expired, you will be disconected”.. Is that a bug?
I ran into the same issue like Daniel. I have the UAG running and fully configured. Two-factor-authentication is working as well, but when I try to start a VDI-Client, I get ‘failed to resolve proxying route for request’.
After I Switch off the currently activated settings on the Connection Servers (according to the guide) it seems to be working from external Connections, but with internal Blast-Connections I have the browser showing certificate Errors and showing https://ip.address.of.vdi:22443/… which is unacceptable for our internal customers! Wildcard certificates are not wanted by our IT security department. What now?
@Robert: I experienced your second issue with the RSA Secure ID as well and it seems like a ‘bug’ to me. Have you configured two different servers at the same time? Try configuring one Server at first and see if that works (worked for me). Did you use the same shared-secret-key for both Servers? Try using two different keys.