Hi All, This one is entertaining me! I have a nice new Horizon 7.4 Connection Server (no load balancer) set up with a single pool of a handful of desktops. It's all working fine if you use...
See more...
Hi All, This one is entertaining me! I have a nice new Horizon 7.4 Connection Server (no load balancer) set up with a single pool of a handful of desktops. It's all working fine if you use HTML5 or traditional clients. However, the customer has some old Tera1 based Wyse P20 zero clients. Now, with previous releases, Tera1 based clients would log onto the broker without much difficulty, but couldn't load a session - the fix was to enable TLSv1 in PCoIP. Less than ideal, but it worked. With more recent releases (at least 7.4, but I've heard 7.3 too), however, the situation is worse. The problem now starts at the Connection server itself, before we even try to launch a session. At first, the zero client was being prevented from connecting to the Connection Server at all. I isolated this to a TLS error - adding TLSv1 to Locked.properties (using secureProtocols.1=TLSv1) moved me forward - the client will now connect to the Connection server enough to provide a Domain logon box. However, if I try and log on with an entitled user (directly assigned to the pool or Cloud Pod Entitlement), the client states 'not authenticated' and drops you back to the logon screen. The Events database happily says that the user is authenticated. If I put in a bad password, it tells me I've got a bad username or password - so the client is being passed authentication information properly when there's an intentional failed attempt. Any ideas before I look at tearing it down and go for 7.1 (the earliest that supports vSphere 6.5U1 and might work)? And before you ask - yes, I know the Tera1 chipset hasn't been supported since 6.0.....