Release Notes
Client SDK for Windows 20.01.2
Important Notes and Requirements
-
Use of Anyware Client SDK requires a separate agreement with HP Anwyare.
-
The SDK is intended for use cases where client customizations are required and when Anyware Software Clients, PCoIP Zero Clients, and PCoIP Mobile Clients are not sufficient.
-
The SDK is intended for customers with software development skills and knowledge, as well as a sound understanding of virtualization systems.
Release Overview
The PCoIP Client Software Development Kit (SDK) is a set of libraries and binaries provided to Teradici Cloud Access Platform customers who require the ability to customize and build a PCoIP client.
With control over how the PCoIP client is built, you can:
- Build clients that conform to your company style and branding guides.
- Build clients that adapt to customized workflows (for example, embed a PCoIP session into a software solution).
PCoIP Client SDK 20.01.2 introduces new fixes and updates to the previous release. This article provides a summary of key additions, compatibility notes, resolved issues, and known issues for this release.
To build additional functionality, such as extended peripheral support, you can utilize the Teradici PCoIP Virtual Channel SDK.
What's New in This Release
This release introduces the following features and enhancements to the PCoIP Client Software SDK 20.01.2 for Windows:
Security and Stability Enhancements
Updates around Security and Stability have been made to the PCoIP Client Software SDK 20.01.2.
Important Notes and Requirements
-
The SDK is intended for Cloud Access Software who require some client customizations when PCoIP Software Client for Windows and Mac, PCoIP Zero Clients, and PCoIP Mobile Clients do not meet their needs.
-
The SDK is intended for customers with software development skills and knowledge, as well as a sound understanding of virtualization systems.
Release Downloads
Related Documents and Software
- PCoIP Client Software Development Kit 20.01 for Windows Developers' Guide
- PCoIP Virtual Channel Software Development Kit 1.1 Release Notes
- Open-source and third-party components
Release History
| Version/Build | Date | Description |
|---|---|---|
| 3.5.0 | April 2018 | GA release |
| 3.6.1 | July 2018 | GA release |
| 3.7.0 | October 2018 | GA release |
| 3.8.0 | February 2019 | GA release |
| 19.05 | May 2019 | GA release |
| 19.08 | August 2019 | GA release |
| 19.11 | November 2019 | GA release |
| 20.01 | February 2020 | GA release |
| 20.01.2 | May 2020 | Maintenance Release |
| Supported Clients | |
|---|---|
| PCoIP Client SDK for Windows | PCoIP Client SDK for Windows is compatible with the following Windows operating systems:Note: PCoIP clients are not supported with Windows Embedded Standard 7 or Windows Embedded Standard 8 systems.
|
| Supported Hosts |
|---|
| Teradici Cloud Access Software |
Relative mouse movement allowed to extend beyond the edge of the screen
When in relative mouse mode, mouse movements are allowed to extend beyond what would be the edge of the screen.
Client Session Localization files missing
Client_session localization files missing.
Client Installation of USB components (USB hub filter driver) may fail
If the USB hub filter driver is in use when the PCoIP client is uninstalled, the subsequent install of the client will fail to install a new USB hub filter driver. The error message will state a different version of the driver is installed, however the driver is actually only partially uninstalled.
These manual steps can be used to completely remove the USB hub filter driver. # Uninstall PCoIP client # Reboot machine # Open registry key editor # Search for "fusbhub" under HKLM # Try to remove registry key containing "fusbhub". If the registry key cannot be removed, note down inf file name associated with the registry entry. The inf file name usually starts with oem, e.g. oem9.inf. Start commandline prompt, run "pnputil -f -d oem9.inf" # Keep repeating step 5 until "fusbhub" gets completely removed from registry key # Reboot machine # Install PCoIP client.
The logfile location cannot be specified
The client session binary takes an argument which overrides the default location for the logfile, however the client is always using the default location.
Fixed an issue where the logfile parameter was not being processed and the logfile was always created in the default location. Now the logfile parameter can be used to specify an alternate location for the file.
Using an invalid or corrupt branding package crashes client
If the branding package does not match the hash value specified for the branding package, the session client will terminate.
Replace the corrupt branding file or use the correct hash value.
Auto forwarding HID devices with multiple flash drives may fail
If more than one flash drive is auto forwarded along with HID devices, not all the devices may be forwarded to the remote host.
Limit auto forwarding to a single flash drive.
Bridged USB devices disconnected when switching to Windowed Mode
When the client has more than one monitor, switching from Full-screen to Windowed mode will disconnect all bridged USB devices.
Connection > USB Devices client dialog does not list any USB devices
At times, after a session starts, the Connection > USB Devices dialog does not list any of the USB devices connected to the client.
Reconnect to the session or physically unplug and reconnect the USB devices connected to the client.
Cancelling large USB file transfer fails
Cancelling a large file from being copied to, or from, a USB flash drive while bridged in PCoIP Software Client fails to function. The file will continue to copy until finished.
Allow operations on USB devices to complete prior to disconnecting the session.
USB keyboards do not work in bridged mode
Keyboards do not work when bridged. This affects both Windows and macOS PCoIP Software Client.
Do not bridge the keyboard. Keyboards function correctly when locally terminated.