AWI: PCoIP Connection Manager + Auto-Logon Session Settings¶
Select the PCoIP Connection Manager + Auto-Logon session connection type from the Configuration > Session page to configure the client to automatically enter a user’s login details when a PCoIP Connection Manager is used as the PCoIP session broker, or when connecting directly to a HP Anyware host.
Take precautions to secure PCoIP Zero Clients
Passwords are stored locally in retrievable form when PCoIP 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 – PCoIP Connection Manager + Auto-Logon
The following parameters can be found on the AWI PCoIP Connection Manager + Auto-Logon page.
AWI PCoIP Connection Manager + Auto-Logon Parameters
|Server URI||Enter the Uniform Resource Identifier (URI) for the PCoIP Connection Manager or HP Anyware host when connecting directly to HP Anyware.
The URI must be in the form https://<host FQDN> or https://<ip address>.
|Logon Username||Enter the user name for the client (maximum number of characters is 128). This user name will be sent to the specified connection server.|
|Logon Password||Enter the password for the client (maximum number of characters is 128). This password will be sent to the specified connection server.|
|Logon Domain Name||Enter the domain for the client (maximum number of characters is 256). This domain will be sent to the specified connection server.|
|Desktop Name to Select||Enter the desktop name used by the client when starting a session.
This field is case sensitive.
|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.|
|Auto Connect||This field determines the client’s auto connect behavior after startup:
Enabled: The client automatically connects with the connection server after startup and a PCoIP session ends, bypassing the OSD Connect page.
Disabled: The client does not automatically connect with the connection server.
Enabled With Retry On Error: The client will continuously attempt to contact the connection server. After a connection failure, the client waits before attempting to connect again. This wait time increases with each successive failure. The wait interval is not configurable.
Devices running firmware 4.1.1 or lower do not support Retry On Error behavior and will always perform a single attempt to contact the connection server when this option is selected.
After enabling Auto Connect, the client must be power-cycled for the change to take effect.
|Connection Server Cache Mode||This field determines whether a connection server is dynamically added to the Server drop-down menu on the OSD Connect page when a user types in a valid server URI, or whether it appears in a read-only list for the user to select.
|Auto Launch If Only One Desktop||When enabled, users are automatically connected to a provisioned desktop after user credentials are entered.
This feature only applies to users who are entitled to a single desktop. It does not apply to users entitled to multiple virtual desktops.
|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.|
|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.|
|Enable Preparing Desktop Overlay||When enabled, the 'Preparing Desktop' overlay appears on the display(s) when users log in.
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 quickly disconnect a PCoIP session. See Disconnecting from a Session for details.|
|PCoIP Utility Bar Mode||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 Tera2 PCoIP Zero Client to process mouse events for the utility bar. For all connection types, the mouse must be locally connected (that is, not bridged).
|Session Negotiation Cipher Suites||Configure the Transport Layer Security (TLS) cipher to use for negotiating the TLS session between the PCoIP client and the PCoIP host.
|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:
You can choose to display:
|Enable DSCP||When enabled, the PCoIP endpoint assigns a Differentiated Services Code Point (DSCP) value determined by the transport session priority negotiation between PCoIP endpoints using proprietary algorithms, enabling intermediate network nodes to prioritize PCoIP traffic accordingly. Additional settings can be configured via group policy for systems using PCoIP software endpoints such as HP Anyware. See your agent documentation for more information.
Sessions between Zero Clients and Remote Workstation Cards will only negotiate a medium priority.
Remote Workstation Card (medium)
Software Agent (configurable OS policy to set session priority to low, medium, or high)
Warning: We don't recommend enabling DSCP on Zero Clients. The purpose of enabling this setting is to reduce the workload on network edge devices of assigning DSCP values on PCoIP packets. Using this setting requires networking expertise and control over the whole link between PCoIP endpoints. See your network administrator and network device documentation for further information on using DSCP in your network.
|Enable Congestion Notification||When enabled, transport congestion notification is enabled to enable PCoIP endpoints to react accordingly if an intermediate network node sets the congestion notification bit in either the IP header or PCoIP transport header. For more information about the PCoIP transport header, see PCoIP Packet Format.|