2020 Dec 27 – updated Import OVF section for UAG 20.12 (2012).2021 Mar 23 – updated Import OVF section for UAG 2103.2021 Apr 7 – updated Import OVF section for UAG 2103.1.2021 July 6 – updated Import OVF section for UAG 2106.2021 Aug 3 – updated Import OVF section for UAG 2106.1 – security fix.2021 Aug 31 – updated Import OVF section for UAG 2106.2 – deadlock fix.2021 Sep 30 – Horizon Edge configuration – added instructions to disable CORS to fix HTML Access in Horizon 2106 and newer.
2021 Dec 2 – updated Import OVF section for UAG 2111.2021 Dec 21 – updated Import OVF section for UAG 2111.1.2022 Jan 25 – updated Import OVF section for UAG 2111.2.2022 Mar 29 – updated Import OVF section for UAG 2203.2022 July 15 – updated Import OVF section for UAG 2207.2022 Oct 21 – updated Import OVF section for UAG 2209.2023 Jan 10 – updated Import OVF section for UAG 2212.2023 Mar 14 – updated Import OVF section for UAG 2303.Other UAG Configurations – High Availability, Network Settings, System Settings.vSphere Web Client Deploy OVF method – Upgrade Existing, or Deploy New.PowerShell Deploy Script Method – both upgrade and new.You edit the locked.properties file located on EACH connection server in c:\program files\vmware\VMware View\Server\sslgateway\conf and add either the VIP (balancedHost=) OR the portalHost line which is just the broker name. The standard fix of disabling the checking completely doesn’t seem to work and now you must explicitly list either the balancedHost or portalHost must be entered into the locked.properties file.Īrmed with this knowledge, the fix is super easy. Very curious!Īfter reviewing the release notes for Horizon 8 version 2106, and it looks like CORS (Cross-Origin Resource Sharing) is now enabled by default. I thought it might have reset the locked.properties file but the checkOrigin=false line was still there. Last night, I upgraded some Connection Broker servers to Horizon 8 version 2106 and this error popped up immediately. This fixed it almost every time until last night. The fix involved adding in a checkOrigin=false line into the file and restarting the server. WHAT GIVES? Thankfully, this is a pretty simple issue to fix. This is just straight hitting the VMware broker directly. Failed to connect to the Connection Server. I have been seeing this a lot when deploying the Horizon at clients lately.
0 kommentar(er)
