Release date: May 30th 2019
Welcome to my VMware Unified Access Gateway series. This topic will cover setting up routing. In my initial set up, my Horizon Desktops were deployed in the same ip subnet and portgroup as the UAG’s prod-facing nic. Routing was therefore not necessary. But, as this is almost never the case in a production environment, I will in this session document the setup with routing. I have set up a separate VLAN, portgroup and subnet for my Horizon Desktops, 10.0.23.0. This subnet is firewalled to work with existing MS Active Directory and I have a set up DHCP for these clients.
For this session I change the portgroup on my template, take snapshot and push the new image to my desktop pool.
After the new image is pushed, the new desktops are available.
If I check in vSphere, I can verify that the new desktops have IP-addresses in the new VLAN
The easiest way to set up routing, is to either do this at initial deployment, or redeploy after adding routes to the ini-file used. I will do the ladder in this session. I add the route to 10.0.23.0/24 via the production subnet gateway 172.16.0.1 in my ini-files.
I redeploy my UAG’s with the updated ini-files, one at a time
“.\uagdeploy.ps1 .\view-uag02.ini PASSWORD PASSWORD false false no”
Once the UAG is powered up, I run through the configuration steps described here: VMware Unified Access Gateway – Configuration
I verify in network settings that my routing is added
After redeployment of my UAG’s, I also make sure to enable the HA-settings
Finally, I test logging in to my new desktops located in my 10.0.23.0 subnet and VLAN and verify hostname and IP address.
I have exported my ini-file to PDF and attached here:
Disclaimer: Every tips/tricks/posting I have published here, is tried and tested in different it-solutions. It is not guaranteed to work everywhere, but is meant as a tip for other users out there. Remember, Google is your friend and don’t be afraid to steal with pride! Feel free to comment below as needed.