This means I deployed VMware Unified Access Gateway 3.2.0. On a side note, I also deleted my VMware Unified Access Gateways VMs and deployed the updated version that ship with Horizon 7.4.0. If you have multiple UAG/Access Points, populate the file with:
If you have a single UAG/Access Point, populate this file with: On the view connection server, create a file called “locked.properties” in “ install_directory\VMware\VMware View\Server\sslgateway\conf\”.
The VMware document is here: To resolve this: It took me hours to find out what was causing this as virtually nothing popped up when searching for a solution.įinally I stumbled across a VMware document that mentions on View Connection Server instances and security servers that reside behind a gateway (such as a UAG, or Access Point), the instance must be aware of the address in which browsers will connect to the gateway for HTML access. If you connect using Chrome to the connection server itself, this issue will not occur. If you use a different browser (Firefox, IE), this issue will not occur. This error pops up ONLY when using Chrome, and ONLY when connecting through the UAG. When connecting with Google Chrome to VMware Horizon HTML Access via the UAG (Unified Access Gateway), an error pops up after pressing the button saying “Failed to connected to the connection server”. For the most part the upgrade went smooth, however I discovered an issue (probably unrelated to the upgrade itself, and more so just previously overlooked). Last night I updated my VMware VDI envionrment to VMware Horizon 7.4.0.
0 kommentar(er)
