You can select the security protocols and cryptographic algorithms that are used to encrypt communications between Horizon Client and Horizon servers or between Horizon Client and the agent in the remote desktop.
In Horizon Client 3.1 and later, these options are also used to encrypt the USB channel (communication between the USB service daemon and the agent).
With the default setting, cipher suites use 128- or 256-bit AES, remove anonymous DH algorithms, and then sort the current cipher list in order of encryption algorithm key length.
- In Horizon Client 4.0 and later, by default, TLS v1.1 and TLS v1.2 are enabled. (TLS v1.0 is disabled. SSL v2.0 and v3.0 are removed.)
- In Horizon Client 3.5, by default, TLS v1.0, TLS v1.1, and TLS v1.2 are enabled. (SSL v2.0 and v3.0 are disabled.)
- In Horizon Client 3.3 and 3.4, by default, TLS v1.0 and TLS v1.1 are enabled. (SSL v2.0 and v3.0, and TLS v1.2 are disabled.)
- In Horizon Client 3.2 and earlier, by default, SSL v3.0 is also enabled. (SSL v2.0 and TLS v1.2 are disabled.)
You should change the security protocols in Horizon Client only if your View server does not support the current settings. If you configure a security protocol for Horizon Client that is not enabled on the View server to which the client connects, a TLS/SSL error occurs and the connection fails.
On the client system, you can use either a group policy setting or a Windows Registry setting to change the default ciphers and protocols. For information about using a GPO, see the setting called "Configures SSL protocols and cryptographic algorithms," in Security Settings for Client GPOs. For information about using the SSLCipherList setting in the Windows Registry, see Using the Windows Registry to Configure Horizon Client.