![]() ![]() Overridable Administrator Defaults PCoIP Session Variables VMware Blast VMware Horizon. 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. Administrative Templates (Computers) PCoIP Client Session Variables. 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. The Horizon Console appears to show that LACU is enabled, though it is not enabled practically. EZ Schedule Login for Ajax Pickering Staff StaffRemote Access - VMWare Horizon. After upgrading to Horizon 7.13, Horizon 2006, or Horizon 2012, and 'Login as current user' (LACU) had previously been enabled, users are asked for their credentials when connecting to the Connection Server. Failed to connect to the Connection Server. Staff must log-in to VMWare to access these forms. I have been seeing this a lot when deploying the Horizon at clients lately. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |