Most connection types are configured from the Configuration > Session menu in the AWI or OSD and the Profiles > Session Configuration menu in the MC. One exception is the Zero Client-to-Bria Softphone Caller Endpoint connection type, which is configured from the Configuration > Unified Communications menu in the AWI and the Profiles > Unified Communications Configuration menu in the MC.
The zero client supports the following session connection types:
You can move high-performance Windows or Linux workstations with PCoIP Remote Workstation Cards into your data center, and then configure sessions between 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.
Depending on the size of your PCoIP deployment, you may wish to use the MC or a connection broker to manage connections between remote workstation cards and zero clients, or you may use the AWI to configure individual hosts and clients remotely. You can even use the OSD to configure settings for a specific zero client.
The following session connection types are available for zero client-to-remote workstation card connections:
For information on the prerequisites for these connection types, see Zero Client–to–Remote Workstation Card Prequisites.
To statically configure a zero client to connect directly to a specific remote workstation card, use the Direct to Host session connection type. You will need to provide the DNS name or IP address of the remote workstation card for this option.
You also need to configure a Direct from Client session connection type on the remote workstation card. You have the option of allowing 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 on how to configure this option, see the following topics in the GUI Reference:
If remote workstation cards reside on the same subnet as 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 remote workstation cards on the subnet. With this configuration, the client OSD will list the first 10 cards discovered. The user can then select the desired one and connect to it.
Note: SLP host discovery is not suitable for deployments with more than 10 hosts if a zero client needs to connect to a specific host all the time. In this situation, a 3rd party connection broker is required.
You also need to configure a Direct from Client session connection type on the remote workstation card. You have the option of allowing the host to accept a connection request from any zero client or from a specific one only. If the latter, you need to provide the client's MAC address.
For details on how to configure this option, see the following topics in the GUI Reference:
A 3rd party connection broker is a resource manager that dynamically assigns host PCs containing remote workstation cards to zero clients based on the identity of the user establishing a connection from the zero client. Connection brokers are also used to allocate a pool of hosts to a group of zero clients. They are typically used in large PCoIP deployments, or when hosts and clients do not reside on the same subnet.
Use the Connection Management Interface session connection type on both the host and client for this option. You need to provide the DNS name or IP address for the 3rd party connection broker.
Note: For information about 3rd party connection brokers, see KB 15134-24 in the Teradici Support Site.
For details on how to configure this option, see the following topics in the GUI Reference:
You can also use a View Connection Server to broker a connection between zero clients and remote workstation cards.
Note: This is not the same thing as configuring a zero client to connect to a VMware Horizon virtual desktop using a View Connection Server.
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, please refer to “Using PCoIP® Host Cards with VMware View” (TER0911004) in the Teradici Support Documentation Center.
The PCoIP Connection Manager implements the PCoIP Broker Protocol for authentication and session initiation. The PCoIP Connection Manager session connection type can be used to connect Tera2 zero clients to the following types of remote PCoIP endpoints:
The following session connection types are available for zero client-to-PCoIP Connection Manager connections:
To configure a Tera2 zero client to automatically detect the right broker to use on the OSD Connect screen, use the Auto Detect session connection type and configure the URI for your broker (e.g., a PCoIP Connection Manager or View Connection Server). After making a successful connection, you can select this URI from the Server drop-down list on the OSD Connect screen.
For details on how to configure this option, see the following topics in the GUI Reference:
To configure a zero client to connect to a PCoIP Access Software instance that is installed in a remote workstation or to an Amazon WorkSpaces desktop, use the PCoIP Connection Manager session connection type. You will need to provide the appropriate server URI for the connection type. For instructions, please see “Teradici PCoIP® Workstation Access Software User Guide" (TER1405004) and "Connecting PCoIP® Zero Clients to Amazon WorkSpaces" (TER1408002), respectively.
For details on how to configure this option, see the following topics in the GUI Reference:
You can also use the PCoIP Connection Manager + Auto-Logon session connection type to automatically enter user login details when connecting in PCoIP Connection Manager mode. Besides the appropriate server URI, you will need to provide a user name, user password, and domain name.
For details on how to configure this option, see the following topics in the GUI Reference:
You can configure zero clients to use the PCoIP protocol when connecting to desktops in a VMware Horizon VDI or DaaS environment, or when connecting to VMware Horizon app-remoting desktops and applications published on an RDS server.
Note: VMWare Horizon RDS-hosted application connections are supported on the View Connection Server, View Connection Server + Auto-Logon, View Connection Server + Kiosk, and View Connection Server + Imprivata OneSign session types for Tera2 zero clients. After configuring your View Connection Server, select the Enable RDS Application Access check box in Advanced Options on the Session page.
Depending on the size of your PCoIP deployment, you may wish to use the MC to configure a profile with a View Connection Server session connection type, or you may use the AWI or the OSD to configure an individual zero client to use a View Connection Server session connection type.
The following session connection types are available for zero client-to-VMware Horizon VDI connections:
For information on the prerequisites for these connection types, see Zero Client–to–VMware Horizon Prerequisites.
To configure a Tera2 zero client to automatically detect the right broker to use on the OSD Connect screen, use the Auto Detect session connection type and configure the URI for your broker (e.g., a PCoIP Connection Manager or View Connection Server). After making a successful connection, you can select this URI from the Server drop-down list on the OSD Connect screen.
For details on how to configure this option, see the following topics in the GUI Reference:
To configure a zero client to connect to a VMware virtual desktop with a manual logon, use the View Connection Server session connection type. You will need to provide the DNS name or IP address of the View Connection Server.
For details on how to configure this option, see the following topics in the GUI Reference:
To configure zero clients to automatically enter user login details when zero clients connect to a virtual desktop, use the View Connection Server + Auto-Logon session connection type. You will need to provide the DNS name or IP address of the View Connection Server, and also the user name, user password, and the domain name to send to the server.
For details on how to configure this option, see the following topics in the GUI Reference:
View Connection Server + Kiosk mode allows you to configure zero clients to connect to a desktop that will be used for a kiosk implementation, such as when multiple users connect to a desktop to obtain information that is not specific to any one individual. At minimum, you will need to provide the DNS name or IP address of the View Connection Server and the kiosk user name—either a custom user name for the kiosk or its MAC address.
For details on how to configure this option, see the following topics in the GUI Reference:
View Connection Server + Imprivata OneSign mode allows you to configure zero clients to use Imprivata OneSign proximity card support when connecting to a virtual desktop via a View Connection Server. You will need to provide the DNS name or IP address of the View Connection Server and the bootstrap URL for the OneSign server.
For details on how to configure this option, see the following topics in the GUI Reference:
The zero client supports interoperability with CounterPath's Bria Virtualized Edition for PCoIP Zero Clients softphone client installed on a VMware Horizon View or Horizon DaaS desktop.
After using a zero client to connect to a Horizon desktop or an Amazon WorkSpaces desktop, users can initiate Unified Communications (UC) services (e.g., voice, messaging, presence information, and contacts) to caller endpoints using a Bria Virtualized Edition softphone client that is installed on their desktop. Once the Bria client establishes the connection, call traffic is routed directly between the zero client and the caller endpoint, thus offloading this traffic from the data center.
This feature is configured from the Configuration > Unified Communications menu in the AWI and the Profiles > Unified Communications Configuration menu in the MC. See AWI Tera2 Client: Unified Communications and MC: Unified Communications for details.
For information on the prerequisites for this connection type, see Zero Client–to–Bria Softphone Client Caller Endpoint Prerequisites.
For information on how to troubleshoot softphone calls, see AWI Tera2 Client: Packet Capture.