It appears that the Teradici Firmware is expecting content in certain fields of the Certificate, and GoDaddy is not providing them in this case. , 16:15:26> LVL:0 RC: 12 MGMT_CMI :Error serving SOAP request! , 16:15:26> LVL:2 RC: 0 GSOAP :'Failed to add certificate to certificate store' Detail: Installing Root CA Certificates in the PCoIP. , 16:15:26> LVL:2 RC: 0 GSOAP :SOAP 1.2 fault: SOAP-ENV:Sender Your root CA certificate must be installed in any PCoIP client that will be used to connect to the PCoIP Agent. , 16:15:25> LVL:1 RC:-510 MGMT_CMI :ERROR: tera_mgmt_cert_add_certificate failed! For the Teradici devices specifically, upgrading the firmware past 4.5.x would also correct this issue. 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. , 16:15:25> LVL:1 RC:-510 MGMT_CERT :ERROR: certificate is not valid (tera_mgmt_cert_add_certificate_by_index) The main change in the certificate will be the valid from date. , 16:15:25> LVL:1 RC:-510 MGMT_CERT :ERROR: tera_x509_util_get_tree failed for certificate 1

I think that these messages in the thin client log are the link to the problem

If you do not you'll see an error message when connecting to your connection servers saying 'the certificate is not rooted'. Typically when you see this message all you have to do is locate the intermediate and rootCA that signed your broker certificate and upload it, however people are seeing issue with some intermediate/root CA's. Teradici, the company behind VMwares PC over IP (PCoIP) remote display. As described in previous posts you need to upload your Root and Intermediate certificates to the PCoIP devices connecting to VIEW. PCoIP Management Console User Manual TER0812002 Issue 12 5 4 September 17.

I came across an interesting issue with a certificate.

Certificate error with teradici pcoip