From the OSD Certificate page, choose one of the Certificate Checking Mode options: Never connect to.

The PCoIP Zero Client’s time maybe incorrect or the certificate may have been issued in a different time zone that is in the future.įor the Teradici devices specifically, upgrading the firmware past 4.5.x would also correct this issue. From the OSD, select Options > User Settings > Certificate. The main change in the certificate will be the valid from date. If the certificate was renewed and signed by the same servers the PCoIP Zero Client will have all the required certificates in the certificate store. We found this article on the Teridici site which seems to have confirmed our issue. Once we enabled the NTP on the Zero client firmware, the issues went away. The Guest OS doesn’t really care about the local time but the certificate trust process very much does. This new certificate installed on the Horizon Broker was super new so we basically had to enable NTP on the local Zero clients to resolve the issue.

Importing the new certificate chains into the devices’ certificate store did not help any but after some intense googling, we did find some promising articles that mentioned how the Time on a local thin client can affect the trust with the certificate authorities. The new certificate was working fine on Windows Fat clients but on some of the older Zero clients, there were trust issues. Tehama Client Certificate Error on Windows 11 Desktop How to Launch Tehama Desktop using Teradici PCoIP Client (Mac OS) Using an Extended Keyboard. After upgrading some of our expiring SSL Certificates on the Horizon View Brokers, we started to receive invalid and untrusted connections on some of our Teradici PCoIP Zero Clients.

Certificate error with teradici pcoip