

I also prefer to cache all cookies and remember to only use “Quiesce Mode” when doing maintenance so you don’t take your stuff down! This is huge early on and can be a major difference maker. In System Configuration, focus on a few key areas, such as cipher suites, TLS versions, and configuring your SysLog server to make troubleshooting easy. We focus on two key areas inside of the GUI, which will put you in a good spot early on. Let’s start by talking about the key building blocks when setting up the individual servers. The documentation isn’t exactly succinct, which can be confusing. You should slice up the UAG itself into two buckets (1) the servers and (2) the load balancer. We should start with the UAG itself because things can get really confusing quickly. Building the Initial Configuration of the Unified Access Gateway Please join me on this deep dive into the UAG and how you can make it run beautifully for your WS1 UEM deployment. I knew that if I wanted to be great at the UAG then I would be on my own. This was problematic on a few fronts (1) documentation and (2) supportability. As an EUC Champion I knew much to everyone’s dismay we would be converging all edge services to the VMWare UAG appliance. I learned a ton during that process and one of the things that I decided to take on was learning all about the Unified Access Gateway (UAG). My son had just been born and I decided to build my first ever home lab. About a year ago, I wrote an article that I really enjoyed found here for a number of reasons.
