This includes your Unified Access Gateway (UAG). You want to make sure you have a trusted certificate in place before placing any web facing solution into production. I hope this post helps some other poor chap that has to do a View upgrade which includes a UAG as well.Getting certificates squared away for your UAG configuration sitting in front of your Horizon infrastructure is a great task to get completed before going into production. I assume between the version the code has changed that if the Proxy Pattern item does not include the /portal URI then those assets from the connection server will be resolved through the UAG (reverse proxy). The page loaded correctly and HTML access /w Blast was working perfectly. (/|/view-client(.*)|/portal(.*)|/downloads(.*))Īnd, Viola! That fixed the reverse proxying issue with View 2203 UAG. When I could see from the logs proxying was not working, I changed the proxy pattern setting to the following:
On version 2006 of the UAG the following proxy pattern was configured: No proxying rules for http request GET /portal/nativeclientīit of a dead give away here that something wasn’t quite right with the new UAGs proxy pattern setting! No proxying rules for http request GET /portal/favicon.ico?v=19431065 No proxying rules for http request GET /portal/webclient/icons-19431065/icon_html_access.svg No proxying rules for http request GET /portal/webclient/icons-19431065/ I was sat scratching my head on this one for a while, when I finally checked esmanager.log in the UAG – specifically the I was able to see that proxying for the assets and images of the connection server were giving the error ‘No proxying rules for http request’: At first everything was sweet (all working via the horizon client), however the UAG upgrade broke the reverse proxying of assets such as the view splash page and HTML access login. The current UAG version is 2203 – I was upgrading from 2006.
When it came time to upgrade the Unified Access Gateways, the simplest way is to just deploy the new OVA and export the settings from the existing and then import them to the new one. I recently went through a VMware View upgrade from branch verison 2006 to 2111.
0 kommentar(er)
