Select the View Connection Server + Kiosk session connection type from the Configuration > Session page to configure the client to use Kiosk mode when a View Connection Server is used to connect to a VMware desktop.
Important! Passwords are stored locally in retrievable form when zero clients are configured with this session connection type. For this reason, it should not be used in high security environments. Ensure that you take precautions to prevent theft of the zero client if you do use this session connection type.
AWI Session Connection Type – View Connection Server + Kiosk
AWI Session Page Parameters
Parameter | Description |
---|---|
DNS Name or IP Address |
Enter the View Connection Server's DNS name or IP address. |
Username Type |
Select the type of username that matches the naming you use for the devices on the View Connection Server.
|
Username |
When Custom is selected as the username type, enter the value for this component of the custom username. This field is limited to 13 characters. |
Password |
To password protect the virtual machine for the kiosk, enter a password in this field. This password must match the one entered for the device in the View Connection Server. |
Port |
By default, port 443 is used to communicate with the connection server. If your network is set up to use a non-standard port for secure connections, enter the port number. |
Certificate Check Mode |
Select the level of verification performed on the certificate presented by the connection server:
|
Certificate Check Mode Lockout |
When enabled, prevents users from changing the Certificate Check Mode settings from the OSD or AWI. |
Trusted View Connection Servers |
Click the Show button to display View Connection Servers for which the client has received a valid certificate. Click the Clear button to clear this cache. |
Use OSD Logo for Login Banner |
When enabled, the OSD logo banner appears at the top of login screens in place of the default banner. You can upload an OSD logo from the OSD Logo Upload page. |
Enable Peer Loss Overlay |
When enabled, the “Network Connection Lost” overlay appears on the display(s) when a loss of network connectivity is detected. Normal hypervisor scheduling delays can falsely trigger this message. Note: This option is only available for a zero client. Desktop applications that require the peer loss notification should re-enable the feature through the OSD, AWI, or MC. |
Enable Preparing Desktop Overlay |
When enabled, the "Preparing Desktop" overlay appears on the display(s) when users log in. Note: This overlay provides assurance that login is proceeding if the desktop takes more than a few seconds to appear. |
Enable Session Disconnect Hotkey |
When enabled, users can press the Ctrl+Alt+F12 hotkey sequence to pop up the "Zero Client Control Panel" overlay, which lets them disconnect the current session on the workstation or power off the workstation. Note: Before users can use this disconnect hotkey sequence, certain other configuration options must be in place. See Disconnecting from a Session for details. |
Enable RDS Application Access |
When enabled and users connect to a VMware Horizon View Connection Server that offers applications, a list of available applications will be presented. Note: Applications open in full-screen mode, but can be re-sized once users are in session. |
PCoIP Utility Bar Mode (Tera2 zero clients only) |
When enabled, the PCoIP Utility Bar appears at the top of the primary display when a user is in session and moves the cursor directly under the bar. The utility bar can be used to disconnect a session or to shut down a remote workstation. For Direct to Host session connection types, Local Cursor and Keyboard must be enabled in order for the zero client to process mouse events for the utility bar. For all connection types, the mouse must be locally connected (i.e., not bridged).
Note: This feature is configurable from the MC and AWI only. It requires firmware version 4.2.0 or newer. |
Session Negotiation Cipher |
Important: In release 4.8.0, the security cipher features listed below are supported on Tera2 zero clients only. In order to use a non-SHA-1 cipher, both the client and host endpoints must support it. Note: For sessions with software hosts, the zero client should be configured to use the Maximum Compatibility option. For Tera2 zero clients: Configure the Transport Layer Security (TLS) cipher to use for negotiating the TLS session between the PCoIP client and the PCoIP host.
For Tera1 zero clients: Configure the Transport Layer Security (TLS) cipher to use for negotiating the TLS session between the PCoIP client and the PCoIP host.
|
Enabled Session Ciphers |
Enable or disable an encryption mode for the device. By default, all encryption modes that pertain to a device are enabled.
Note: For more information about connecting to VMware Horizon virtual desktops, see “Using PCoIP® Zero Clients with VMware View User Guide” (TER0904005) in the Teradici Support Documentation Center. Note: The enabled encryption mode must match between the host and client for a session to be established. If more than one mode is enabled, the firmware selects the following:
|
Disconnect Message Filter |
This field lets you control what type of messages appear when a session is disconnected. There are three categories: Information: User- or administrator-initiated actions affecting the session:
Warning: System-initiated, but expected actions affecting the session:
Error: Unexpected system-initiated actions causing session to fail:
Note: For detailed information about the above session disconnect codes, please see KB 15134-872 in the Teradici Support Site. You can choose to display:
|
Custom Session SNI |
When enabled, sets a customized Server Name Indication (SNI) string on authorized man-in-the-middle-enabled clients. The SNI string is appended to the SSL/TLS HELLO when the client initates an SSL connection with the host. |
Enable DSCP |
When enabled, the device populates the Differentiated Services Code Point (DSCP) field in the IP header, allowing intermediate network nodes to prioritize PCoIP traffic accordingly. |
Enable Transport Congestion Notification |
When enabled, transport congestion notification is enabled to allow PCoIP endpoints to react accordingly if an intermediate network node sets the congestion notification bit in either the IP header or PCoIP transport header. Note: For more information about the PCoIP transport header, see PCoIP Packet Format. |