In the Edit License pop-up window, enter your valid license serial number and click OK.
On the right side of the screen, click Edit License. If it does not, expand View Configuration in the left navigation panel and click Product Licensing and Usage. This issue goes away if I point the internal (of the split DNS) to the internal ip of the UAG Load-balancer but I am concerned about traffic and sending internal traffic to the dmz to come back in.Īll certs used are public and there is no internal CA. The Product Licensing and Usage page will display. I'm wondering if it is because on the horizon connection server, View Configuration, Servers, Connection Servers, Edit, General Tab, to use the UAG with reverse proxy, I need to uncheck all the external URL boxes. After acceptance, the url flips back to the connection server load-balanced URL (what the user used to connect to horizon) and the cert is accepted. Since there is no certificate with matching the ip address, there is a certificate error, which can be accepted. On initial connection to the vdi it shows the vdi's ip address port 22443. Everything works as expected.įrom internal, there are no certificate errors when using the view client.įrom internal when using html there are no certificate errors until the deskop is selected. I am using split dns, with external pointing at the UAG's, internal pointing at the connection servers.įrom external, there are no certificate errors when connecting using the view client or html. In a new horizon 7.5 deployment, we have configured load-balanced UAGs for external access pointing to load-balanced connection servers.
0 kommentar(er)
