Connecting to a Session¶
The OSD enables users 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.
Connecting to a Session from the Connect Window¶
Enter the requested information (for example, server name or IP address for Auto Detect, PCoIP Connection Manager, View Connection Server) and click Connect. If your Tera2 PCoIP Zero Client is configured to cache servers in Last servers used mode, this server name will subsequently appear in the Server drop-down list after a successful connection is made.
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.
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 VMware View 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 startup—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:
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.
If required, type your credentials.
Making a Trusted HTTPS Connection¶
After connecting to the connection server, a user authentication page displays to enable the user to enter 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 VMware 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 the user clicks Continue at this warning, 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 VMware 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 users from 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 users from changing this setting.
Authenticating the User¶
After the user sends the 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 the user is not configured to connect automatically to a desktop, a list of one or more desktops to which the user is entitled displays. The user may select the desired one and click Connect.
Selecting an entitlement
If the desktop is available, a message displays on the Connect screen to inform the user that the server is preparing the desktop. After a few seconds, the PCoIP session is established and the user connected.
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 to inform the user that the assigned desktop source for this desktop is not currently available. The firmware continuously attempts to connect until the desktop is ready or the user clicks Cancel to cancel the operation.
If a PCoIP Connection Manager provides the estimated remaining time to connect to a user's desktop, the zero client will display the remaining time to the user.
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 user’s session during startup or after a session has been established, see About Overlay Windows.