In my case upgrading to VMware Horizon View 7 cause connections to throw a TLS error on the Zero Client when users tried to connect. It was a simple fix by running a script "TLS_1.0_Regedit.reg" to mortify the Master image registry & also Disabling "PCoIP Secure Gateway" in the Horizon 7 Administrator, then recomposing the pools.
1. Disable "PCoIP Secure Gateway" in the Horizon 7 Administrator
View Configuration > Servers > Connection Servers > Connection Server > Edit > Uncheck "PCoIP Secure Gateway"
2. Copy & Paste the following to a text file & save it with the ext .reg > It's really quite simple, you just need to change the .txt extension to TLS_1.0_Regedit.reg
Windows Registry Editor Version 5.00
; Horizon View TLS1.0 for legacy Zero Clients
[HKEY_LOCAL_MACHINE\SOFTWARE\Teradici\PCoIP\pcoip_admin]
"pcoip.ssl_protocol"="TLS1.0:TLS1.1:TLS1.2"
LINK: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=21307...
NOTE:
This solution may or may not work for you, sometimes it depend on the Zero Client type & PCoIP .Ver you might have.
The new Zero & Thin clients VDI / DaaS didn't have this problem.
LINK: http://www.samsung.com/us/business/computing/zero-clients-and-thin-clients
Raul.
VMware VDI Administrator
Help The VMTN Communities by: Like, Share, Comment, Reply, Helpful, Answered. Thanks!
http://ITCloudStream.com/
www.ITSA.Cloud
