Key Resolved Issues: |
Products |
Platforms |
Tera2 |
Workstation |
VMware Horizon |
Amazon WorkSpaces |
24761 - Resolved an issue where Zero Client displays black screen(s) and does not respond to keyboard and mouse input after a session has ended.
|
✔ |
✔ |
✔ |
✔ |
23606 - Zero client failed to acquire a DHCP lease from the Redhat ISC-DHCP server version 3.0.5.23.el5_5.2 due to an incorrect Hardware Type byte in DHCP Discovery packet's Option 61 (client identifier) value.
|
✔ |
✔ |
✔ |
✔ |
23223 - Fixed an issue where the common name string length of the SCEP request was larger than the actual string size, causing invalid characters to show up with certain SCEP servers (e.g. OpenTrust SCEP server).
|
✔ |
✔ |
✔ |
✔ |
21815 - During certificate validation, zero clients may fail to validate the hostname of a connection broker when the hostname is expected to match a wildcard name in the certificate's list of Subject Alternative Names.
|
✔ |
|
✔ |
✔ |
21499 - The CMI (management protocol) client in the PCoIP firmware now establishes connections to a CMI management server (e.g. the PCoIP Management Console) utilizing TLS versions above TLS 1.0. Starting with firmware 4.0.0, this connection was constrained to TLS 1.0. This restriction is removed and the firmware can now establish management connections using TLS 1.0, TLS 1.1 and TLS 1.2.
|
✔
|
✔ |
✔ |
✔ |
20717 - Logitech Extreme 3D Pro Joystick, and potentially other USB devices, will now properly enumerate when attached to a USB hub.
|
✔ |
✔ |
✔ |
|
20180 - Resolved an issue where .NET smart card authentication fails.
|
✔ |
|
✔ |
|
19861 - The PCoIP Connection Manager desktop allocation timeout value has been increased from 120 seconds to 200 seconds in order to allow more time for a successful session connection.
|
✔ |
|
|
✔ |
19615 - Imprivata OneSign questions are no longer truncated in the OSD. |
✔ |
|
✔ |
|
19614 - Resolved an issue where modifier keys (e.g. ctrl, alt) are active in the PCoIP host upon session reconnect. |
✔ |
|
✔ |
|
19053 - Pre-session authentication using Access Client smart cards with uncompressed certificates now succeeds. |
✔ |
|
✔ |
|
18754 - The screensaver is now activated when a PCoIP session ends using an Amazon WorkSpaces host.
|
✔ |
|
|
✔ |
18033 - Resolved an issue processing USB device identifiers that prevented the Digilent Nexys 3 from working. |
✔ |
✔ |
✔ |
|
17857 - The domain drop down width no longer exceeds the username/password authentication dialog box. |
✔ |
|
✔ |
✔ |
14542 - Enabling or Disabling the Low Bandwidth Text Codec now takes effect on the next session. |
✔ |
|
✔ |
✔ |
14509 - HP z27i monitors no longer remain blank after being disconnected from a PCoIP session. |
✔ |
✔ |
✔ |
✔ |
14409 - Zero Clients will no longer display a black screen when a user disconnects their session with an active webcam. |
✔ |
|
✔ |
|
13981 - The zero client will attempt to re-establish communication with the Epson ES-D350 scanner if a session is disconnected and the scanner goes to sleep after being idle for ~15 minutes. This affects only the Epson ES-D350 scanner with VID=0x04b8 PID=0x0144. |
✔ |
|
✔ |
|
13357 - During smart card authentication, the zero client may reset if the smart card reader is disconnected after entering the correct PIN. |
✔ |
|
✔ |
|
12948 - Zero Clients no longer exhibit "tearing effects" on certain high-resolution displays (such as 2560x1600@60 Hz) when the source content is updating faster than 30 Hz. |
✔ |
✔ |
|
|
12899 - Zero Clients will no longer display a black screen when a user disconnects their session while transferring data from a USB storage device. |
✔ |
|
✔ |
|
12531 - Resolved erratic cursor behaviour with devices using absolute coordinates. This improves use of devices such as the Belkin F1DN104K and F1DN108K. |
✔ |
✔ |
✔ |
|
11856 - Resolved an issue where an attached HID device may become unresponsive and stop working. |
✔ |
|
✔ |
|
10370 - Zero Clients now properly fetch DNS SRV records (pcoip-broker, pcoip-tool, pcoip-vcs) that were added after they have been reset. |
✔ |
✔ |
✔ |
✔ |
9573 - Resolved an issue where a zero client with the Auto Connect feature set to Enabled with Retry on Error would stop attempting to connect to the broker after completing touchscreen calibration. |
✔ |
|
✔ |
|