When you change the Unified Access Gateway (UAG) deployment type to or from Basic and Advanced, the load balancer IP address might change. If it does, you must update the Unified Access Gateway FQDN DNS records with the new IP address.
The following sections show how different deployment scenarios impact the load balancer IP address after the deployment type is changed between Basic and Advanced.
UAG Advanced Mode is available across all supported platforms, including Native Desktop, Mobile, and Web clients.
UAG Deployment For Internal and External Access
- This deployment type creates an internal and external load balancer for the UAG deployment.
- External load balancer will have a public IP address as the front-end IP address, the external load balancer IP address will always be retained.
- Internal load balancer will have the VM subnet private IP address as the front-end IP address, if the VM/Desktop subnet is updated with a different subnet while changing the UAG deployment mode, the internal load balancer IP address will not be retained and a new IP address from the new VM subnet gets assigned to the load balancer.
UAG Deployment For Internal Access Over a Corporate Network
- This deployment type creates an internal load balancer for the UAG deployment.
- The internal load balancer front-end IP address is a private IP address allocated from the VM subnet.
- If the VM/Desktop subnet is updated with a different subnet while changing the UAG deployment mode, the internal load balancer IP is not retained. A new IP address from the new VM subnet gets assigned to the load balancer.
UAG Deployment For External Access Over the Internet
- This deployment type creates an external load balancer for the UAG deployment.
- The external load balancer front-end IP address is a public IP address.
- The load balancer IP address will always be retained.
UAG Deployment For Internal and External Access with “Automatic Public IP” Turned Off
- This deployment type creates an internal and external load balancer for the UAG deployment.
- External load balancer will have the DMZ subnet private IP address as the front-end IP address, if the DMZ subnet is updated with a different subnet while changing the UAG deployment mode, the external load balancer IP address will not be retained and a new IP address from the new DMZ subnet gets assigned to the load balancer.
- Internal load balancer will have the VM subnet private IP address as the front-end IP address, if the VM/Desktop subnet is updated with a different subnet while changing the UAG deployment mode, the internal load balancer IP address will not be retained and a new IP address from the new VM subnet gets assigned to the load balancer.
UAG Deployment For External Access Over the Internet with “Automatic Public IP” Turned Off
- This deployment type creates an external load balancer for the UAG deployment.
- The external load balancer front-end IP address is a private IP address allocated from the DMZ subnet.
- If the DMZ subnet is updated with a different subnet while changing the UAG deployment mode, the external load balancer IP is not retained. A new IP address from the new DMZ subnet gets assigned to the load balancer.
Was this page helpful?