I like the PowerShell script over deploying the appliance through vCenter because the appliance is ready to use on first boot.
This method consists of a PowerShell Deployment Script and an INI file that contains the configuration for each appliance that you’re deploying. Typically, I prefer using the PowerShell deployment method. The second option is the PowerShell deployment method, where a PowerShell script and OVFTool are used to automatically deploy the OVA file, and the appliance’s configuration is injected from an INI file during deployment. The first is a manual deployment where the UAG’s OVA file is manually deployed through vCenter, and then the appliance is configured through the built-in Admin interface. There are two main ways to deploy the UAG. If you want to learn more about the Unified Access Gateway, including a deeper dive on its capabilities, sizing, and deployment architectures, please check out the Unified Access Gateway Architecture guide on VMware Techzone. I won’t be covering any of the other options in this post. There have also been a couple of 3rd-party options that could be used with Horizon. The UAG can utilize multiple forms of MFA, including RSA, RADIUS, and SAML-based solutions, and setting up MFA on the UAG does not require any changes to the connection servers. When multi-factor authentication is enabled, users are prompted for that second factor first, and they are only prompted for their Active Directory credentials if this authentication is successful. Second, the UAG is not tightly coupled to a connection server, so you can use a load balancer between the UAG and the Connection Server to eliminate single points of failure.Īnd finally, multifactor authentication is validated on the UAG in the DMZ. The UAG is built on Photon, VMware’s lightweight Linux distribution, and it is distributed as an appliance. First, it does not require a Windows license. The UAG has some benefits over the Security Server.
The Security Server was a Windows Server running a stripped-down version of the Horizon Connection Server, and this component was deprecated and removed with Horizon 2006. This wasn’t always the case – previous Horizon releases the Horizon Security Server. The appliance is hardened for deployment in a DMZ scenario, and it is designed to only pass authorized traffic from authenticated users into a secure network.Īs of Horizon 2006, the UAG is the primary remote access component for Horizon.
The Unified Access Gateway (also abbreviated as UAG) is a purpose built virtual appliance that is designed to be the remote access component for VMware Horizon and Workspace One. And we’re back…this week with the final part of deploying a Horizon 2006 environment – deploying the Unified Access Gateway to enable remote access to desktops.īefore we go into the deployment process, let’s dive into the background on the appliance.
0 kommentar(er)
