Peering Remote Workstation Cards to PCoIP Zero Clients

PCoIP Remote Workstation Cards can be peered (paired) to PCoIP Zero Clients using custom certificates to establish a PCoIP peer-to-peer connection that is unique to your environment. This optional but recommended configuration allows for a more secure connection then the default connection. The Remote Workstation Card must have a root certificate and custom peer-to-peer certificate in their certificate store, and the custom certificate which trusts the other device's selected peer-to-peer certificate must be applied to the Peer-to-Peer Certificate field.

Support for Peer-to-Peer Certificates

The peer-to-peer connection using certificates supports connections between PCoIP Zero Clients and Remote Workstation Cards only.

To configure a peer-to-peer connection from a PCoIP Zero Client:

  1. Upload your custom peer-to-peer certificate and your root certificate to your Remote Workstation Card certificate store. See Uploading Certificates for details.

    PCoIP Zero Client Certificate

    Ensure the desired trusted certificate is uploaded to the connecting PCoIP Zero Client

  2. From the AWI Session page select whether one client or multiple clients can connect to your Remote Workstation Card.

    • Select Accept Any Peer if you want any properly configured PCoIP Zero Client to be able to connect to your Remote Workstation Card.

    • De-select Accept Any Peer and enter the Peer MAC Address of the specific PCoIP Zero Client you want connecting to your Remote Workstation Card.

  3. Select the TLS Security Mode option Suite B: TLS 1.2 with Suite B-compliant 192-bit elliptic curve encryption.

  4. Select the correct Peer-to-Peer Certificate from the drop down list. (If it is not displayed, you have not yet uploaded it to the certificate store)

    AWI Session Page-Peer-to-Peer Certificate Parameter

  5. Select Apply and then Continue.

Notes

  • If a custom peer to peer certificate is applied and a connection is made, and the custom certificates are removed from the certificate store on either device, a subsequent connection will not establish.

  • A connection reset is required before changes will take affect.