Release Notes

PCoIP Zero Client Firmware Version 5.5.1 | 6
Known issues
SIPR token authentication fails with multiple certificates on smart card
The zero client fails to complete SIPR token smart card authentication against VMware Horizon View
when the smart card contains more than two certificates.
Workaround: Ensure that the card only two certificates.
Change in button timing for entering manual recovery
With the firmware v5.2.1, the power button sequence to boot a zero client from powered down into the
recovery image is:
1. Press power button once to turn on the client and wait for one second
2. Press the power button three times.
3. Zero client boots into the recovery image
From firmware v5.0.0 to v5.2.0 it was possible to press the power button three times immediately after
turning on the zero client. This is no longer supported.
Mouse cursor does not work after zero client reboots
The On-Screen Display's mouse cursor does not work for a few seconds after a zero client reboot
when a web browser is connected to the zero client's Administrative Web Interface.
Zero Client is not able to connect using IPv6 VMware Horizon View when DHCPv6 is not available
If the zero client is configured for IPv6, and it cannot connect a DHCPv6 server, it will be unable to
connect to a desktop when brokered by an IPv6 VMware Horizon View Connection Server. The zero
client displays the message 'CONFIGURATION_ERROR - IPv6 capability required: Your VMware
Horizon View Client addressing configuration is not compatible with this View Server...'
Security scanners may report zero client to be susceptible to CVE-2004-0230
Security scanners may report that the zero client is susceptible to CVE-2004-0230. This CVE exists in
TCP stacks in devices that implement the Border Gateway Protocol. While this is a significant issue
for routers that implement the Border Gateway Protocol, it is not a significant issue for zero clients.
Mouse wheel problem occurs with Belkin Advanced Secure Keyboard/Mouse Switch
Mouse wheel scroll-down does not work while in a PCoIP session. This occurs when the mouse is
connected to a zero client through a Belkin Advanced Secure Keyboard/Mouse (KM) Switch. This
problem has been observed while using KM models F1DN102K, F1DN104K, and F1DN108K.
changed to PCoIP Connection Manager,
with the address of the Leostream
Connection Broker. Also ensure the
Leostream Connection Broker has had
‘Enable TLSv1.1 protocol’ enabled in the
Connection Broker Security Options
section of the Connection Broker >
System > Settings page.
Supported browsers are Firefox, Chrome,
Internet Explorer 11, and Microsoft Edge.
Versions of the browsers tested are those
that were available prior to release.
Web browsers must support TLS 1.1 or
higher to connect to the administrative
web interface (AWI).