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. No further user authentication is required. 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. With Horizon Client for Windows, when users select Log in as current user in the Options menu, the credentials that they provided when logging in to the client system are used to authenticate to the Horizon Connection Server instance and to the remote desktop. 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. To download to your desktop sign into Chrome and enable sync or send yourself a reminder. 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 Comments
Leave a Reply. |