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. User password: Password when logging on to the VMware Horizon server. 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. VMware Horizon 8 - Fix to Error Failed to connect to the Connection Server using. Supported on: VMware View Client vdmclient. If this option is set to off, the user will not be able to override the Default value of Log in as current user checkbox option. 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. VMware Horizon You can connect to your desktop and applications by using the VMware Horizon Client or through the browser. Display option to Log in as current user Determines if the Log in as current user checkbox is visible in the Windows View Client. 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)
