Connecting to PCoIP Remote Workstation Cards¶

You can move high-performance Windows or Linux workstations with PCoIP Remote Workstation Cards into your data center, and configure sessions between Tera2 PCoIP Zero Clients and these workstation hosts over a LAN or WAN. This type of configuration provides a secure, reliable, and easy-to-manage solution that meets the needs of users who have dedicated computers with graphically demanding applications.

Direct connections with no-IP networks

While zero clients and remote workstation cards can be configured to be directly connected via a no-IP network (a cable connecting both units together with no network devices in between), it is not a configuration that is supported by Teradici. For more information see KB 1297.

This topic includes information on the following sections:

Prerequisites¶

Before connecting a Tera2 PCoIP Zero Client to a PCoIP Remote Workstation Card, ensure that the following conditions are met:

Configuration Options¶

The following session connection types are available for PCoIP Zero Client-to-PCoIP Remote Workstation Card connections:

Best Security Practices

Teradici highly recommends using custom peer-to-peer certificates to create a more secure environment when connecting to your Remote Workstation Card. Contact your IT department to ensure your deployment is in accordance with your Company's security policy. See Peering Zero Clients to Remote Workstation Cards for details.

Connecting Statically¶

To statically configure a Tera2 PCoIP Zero Client to connect directly to a specific PCoIP Remote Workstation Card, use the Direct to Host session connection type. You will need to provide the DNS name or IP address of the PCoIP Remote Workstation Card for this option.

You also need to configure a Direct from Client session connection type on the PCoIP Remote Workstation Card. You have the option of enabling the host to accept a connection request from any client or from a specific client only. If the latter, you need to provide the client’s MAC address.

For details about how to configure the session connection type, see the following topics in the GUI Reference:

Connecting Using SLP Host Discovery¶

If PCoIP Remote Workstation Cards reside on the same subnet as Tera2 PCoIP Zero Clients, you can use the Direct to Host + SLP session connection type to configure clients to use Service Location Protocol (SLP) to discover the PCoIP Remote Workstation Cards on the subnet. With this configuration, the client OSD will list the first 10 cards discovered. The end user can select the desired one and connect to it.

Do not select SLP host discovery with more than 10 hosts

SLP host discovery is not suitable for deployments with more than 10 hosts if a Tera2 PCoIP Zero Client requires an ongoing connection. In this situation, a connection broker is required.

You also need to configure a Direct from Client session connection type on the PCoIP Remote Workstation Card. You have the option of enabling the host to accept a connection request from any Tera2 PCoIP Zero Client or from a specific one only. If the latter, you need to provide the client’s MAC address.

For details about how to configure the session connection type, see the following topics in the GUI Reference:

Connecting Using a Third-Party Connection Broker¶

A third-party connection broker is a resource manager that dynamically assigns host PCs containing PCoIP Remote Workstation Cards to Tera2 PCoIP Zero Clients based on the identity of the user establishing a connection from the Tera2 PCoIP Zero Client. Connection brokers are also used to allocate a pool of hosts to a group of Tera2 PCoIP Zero Clients. They are typically used in large PCoIP deployments, or when hosts and clients do not reside on the same subnet.

Third-party brokers use the PCoIP Connection Manager session connection type.

For details about how to configure the session connection type, see the following topics in the GUI Reference:

Connecting Using the View Connection Server¶

You can also use a View Connection Server to broker a connection between Tera2 PCoIP Zero Clients and PCoIP Remote Workstation Cards.

For details about how to configure the session connection type, see the following topics in the GUI Reference:

For this option, VMware View Agent must be installed on the remote workstation, and a number of other configuration requirements for both the client and host must be in place. For complete details, refer to Using PCoIP® Host Cards with VMware View.

Connection Instructions¶

These instructions explain how to configure a Tera2 PCoIP Zero Client to connect to a PCoIP Remote Workstation Card. If you are using a broker to connect, see the documentation from your equipment supplier for instructions on how to configure the broker.

Before connecting, you will need to know the IP address or Fully Qualified Domain Name (FQDN) of your PCoIP Remote Workstation Card.

Connecting Directly Using SLP Host Discovery¶

After successfully completing the installation steps outlined in PCoIP® Tera2 Zero Client Quick Start Guide, the client will be powered on and ready to use. The next step is to initiate a PCoIP session with a PCoIP Remote Workstation Card. The easiest way to get started is to use SLP host discovery.

Tera2 PCoIP Zero Client and the host PC must reside on the same subnet

SLP host discovery requires the Tera2 PCoIP Zero Client and host PC to reside on the same subnet. You also need to know the IP address and/or MAC address of the PCoIP Remote Workstation Card so you can select it from the list of available hosts. In addition, the PCoIP Remote Workstation Card must be configured to accept any peer or to accept the specific MAC address of the Tera2 PCoIP Zero Client. You can configure this from the host AWI Configuration > Session > Direct from Client page.

To connect directly using SLP host discovery:¶

  1. From the Options > Configuration > Session menu on the Tera2 PCoIP Zero Client’s OSD, select the Direct to Host + SLP Host Discovery connection type, and click OK.
  2. Click the Connect button.
  3. When the Discovered Hosts screen appears with a list of available hosts, select your PCoIP Remote Workstation Card by its IP/MAC address pair, and click OK.
  4. When prompted, enter your remote workstation’s login credentials.

For details about advanced settings, see Direct to Host + SLP Host Discovery.

Connecting Directly Without Using SLP Host Discovery¶

To connect directly without using SLP host discovery:

  1. From the Options > Configuration > Session menu on the Tera2 PCoIP Zero Client’s OSD, select the Direct to Host connection type.
  2. Enter the DNS name or IP address of the PCoIP Remote Workstation Card, and click OK.
  3. Click the Connect button.
  4. When prompted, enter your remote workstation’s login credentials.

For details about advanced settings, see Direct to Host.

Connecting Using a Broker¶

To connect using a broker:

  1. From the Options > Configuration > Session menu on the Tera2 PCoIP Zero Client’s OSD, select one of the following connection types:
  2. Enter the DNS name or IP address of the broker, and click OK.
  3. Click the Connect button.
  4. When prompted, enter your remote workstation’s login credentials.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. -->