Connecting to a Session

The OSD enables you to create a PCoIP session between the client and a remote resource by clicking the green Connect button in the center of the Connect window.

Info

Tera2 Zero Clients support session failover in a Connection Manager and Security Gateway deployment. If the primary gateway used to establish a PCoIP session fails unexpectedly, the session is automatically transferred to the next available gateway.

Session failover is only available if failover gateways are configured on the machines where the Connection Manager and/or Security Gateway are installed. No additional configuration is required on the Tera2 Zero Clients.

Connecting to a Session from the Connect Window

1. Enter the requested information (for example, server name or IP address for Auto Detect, PCoIP Connection Manager, View Connection Server) and click Connect.

2. If you have already connected to a server, it will appear in the Server drop-down list if your Tera2 PCoIP Zero Client is configured to connect to this server or if it is configured to cache servers in Last servers used mode. Select the server from the drop-down list and click Connect.

3. If your Tera2 PCoIP Zero Client is configured to connect directly to a PCoIP Remote Workstation Card, you only need to click Connect.

The Connect window differs slightly depending on the session connection type you configure. The following examples show the Connect window for the Auto Detect and Direct to Host session connection type.

OSD Auto Detect window

OSD Direct to Host connect window

While the network connection is initializing, various status messages are displayed above the button to indicate the progress. If problems are experienced during startup, for example, if the connection cannot be made or a DHCP lease fails—other messages display in this area to indicate the nature of the problem.

Once the connection is established, the local GUI disappears, and the session image appears.

Connecting to a Session Using Smart Cards

Users can connect to a session using smart cards when connected to Omnissa Horizon virtual desktops or a PCoIP Connection Manager that supports this feature.

This section addresses using smart cards when connected to a PCoIP Connection Manager.

Before connecting to a session using a smart card, connect the USB smart card reader into the Tera2 PCoIP Zero Client.

While the network connection is initializing, various status messages are displayed to indicate the progress. If problems are experienced during start-up, for example, if the connection cannot be made—other messages display in this area to indicate the nature of the problem. Once the connection is established, the local GUI disappears, and the session image appears.

To connect to a session using a smart card:

1. Insert a supported smart card into a supported USB smart card reader. The Connect window appears. The Connect window may differ slightly depending on your configuration: for example, the User name and Domain fields may be read-only.
   

2. If required, type your credentials.

Making a Trusted HTTPS Connection

After connecting to the connection server, a user authentication page is displayed for providing login credentials. The banner on this page indicates the type of connection.

If the correct trusted SSL root certificate for the server has been installed in the Tera2 PCoIP Zero Client and all other certificate requirements are met for the configured certificate checking mode (see Requirements for Trusted Server Connections), the icon at the top of this page shows a closed padlock symbol with a green check mark, and the 'https' in the server’s URI also displays in green text.

The following image shows the user authentication screen when the Tera2 PCoIP Zero Client trusts the server’s certificate. When connecting to other host types, such as Omnissa Horizon and Amazon WorkSpaces, you will see a similar authentication screen.

Tera2 PCoIP Zero Client trusted HTTPS connection

Making an Untrusted HTTPS Connection

If the correct trusted SSL root certificate for a connection server has not been installed in the Tera2 PCoIP Zero Client, or if other certificate requirements are not met (see Requirements for Trusted Server Connections), a warning such as the following appears if your Tera2 PCoIP Zero Client is configured to warn before connecting to untrusted servers.

View Connection Server Certificate Warning

PCoIP Connection Manager Certificate Warning

If you click Continue, the connection will still be secured with HTTPS, but an open padlock icon with a red 'x' will display on the login screen, along with red 'https' text with strikethrough formatting, as seen in the top row of the following image. When connecting to other host types, such as Omnissa Horizon and Amazon WorkSpaces, you will see a similar screen.

Tera2 PCoIP Zero Client untrusted HTTPS connection

As an administrator, you can use the Options > User Settings > Certificate page to prevent initiating untrusted server sessions by configuring the Tera2 PCoIP Zero Client to refuse a connection to a server that cannot be verified. Depending on the configured server type, this page has a different banner.

VMware Horizon Certificate Checking Mode page

PCoIP Certificate Checking Mode

Using the AWI, you can enable Certificate Check Mode Lockout from the Session – View Connection Server or Session – PCoIP Connection Manager page to prevent changes to this setting.

Authenticating the User

After you provide login credentials, the server performs authentication. If the user name and password are not entered correctly, or if the Caps Lock key is on, a message displays on this page to indicate these problems.

Unknown user name or password

All connections support the down-level logon user name format (DOMAIN\user) in the User name field. If using a compatible PCoIP Connection Manager (see its release details for more information), UPN (user@domain) is also supported in the User name field.

Tera2 PCoIP Zero Client with domain field hidden

Tera2 PCoIP Zero Client with domain field hidden

Connecting to a Desktop

If you are not configured to connect automatically to a desktop, a list of one or more desktops to which you are entitled displays.

To connect to a desktop of your interest:

1. Launch the Tera2 PCoIP Zero Client. If your Tera2 PCoIP Zero Client is configured to cache servers in Last servers used mode, desktops that you previously connected to will appear in the drop-down list.

2. Use the search bar at the top of the connection window to locate the desktop of your interest.

   
   Selecting an entitlement

3. Click Connect to connect to the desktop.

You'll see a message on the Connect screen indicating the server is preparing your desktop when it is available. After a few seconds, the PCoIP session is established.

If the desktop is not available (for example, if the desktop is in the process of rebooting), a second message also flashes on the Connect screen indicating that the assigned desktop source for this desktop is not currently available. The firmware continuously attempts to connect until the desktop is ready or you click Cancel to cancel the operation.

You will see the estimated connection time on the zero client if the PCoIP Connection Manager provides it.

Notification with estimated length of time before connecting

Uploading certificates to a single device

For information on how to upload certificates to a single device using the AWI, see Uploading Firmware.

OSD messages on startup or after a session has been established

For information on other OSD messages that may appear on top of a session during startup or after a session has been established, see About Overlay Windows.

Connecting from a Broker

If using an HP Connection Manager or a third-party broker, use the broker's URI credentials for either an Auto Detect or PCoIP Connection Manager session type.