Administrators and sometimes end users can configure whether client connections are rejected if any or some server certificate checks fail.
Certificate checking occurs for SSL connections between Connection Server and Horizon Client. Certificate verification includes the following checks:
Has the certificate been revoked?
Is the certificate intended for a purpose other than verifying the identity of the sender and encrypting server communications? That is, is it the correct type of certificate?
Has the certificate expired, or is it valid only in the future? That is, is the certificate valid according to the computer clock?
Does the common name on the certificate match the host name of the server that sends it? A mismatch can occur if a load balancer redirects Horizon Client to a server that has a certificate that does not match the host name entered in Horizon Client. Another reason a mismatch can occur is if you enter an IP address rather than a host name in the client.
Is the certificate signed by an unknown or untrusted certificate authority (CA)? Self-signed certificates are one type of untrusted CA.
To pass this check, the certificate's chain of trust must be rooted in the device's local certificate store.
If your administrator has allowed it, you can set the certificate checking mode. On the Horizon Client home window, tap the Option menu in the upper-left corner of the menu bar and expand the Certificate Checking Mode section. You have the following choices:
Never connect to untrusted servers. If any of the certificate checks fails, the client cannot connect to the server. An error message lists the checks that failed.
Attempt to connect regardless of server identity certificates. This setting means that no certificate checking occurs.
Because the certificate mechanism used in Windows 10 UWP apps is more limited than for Windows desktop applications, the certification check can fail even if the level is set to Attempt to connect regardless of server identity certificates. For example, the certification check can fail for the following reasons:
The certificate signed by the root CA has been revoked.
The certificate signed by the intermediate CA has been revoked.
The certificate is valid but the intermediate CA has been revoked.
The certificate in the chain contains an unknown extension that is marked "critical".