Release Notes
Client SDK for Windows 21.07
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 21.07 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 21.07 for Windows:
Security and Stability Updates
Increased security and stability updates and enhancements around the PCoIP Client.
TLS 1.1 Deprecation
The PCoIP Client SDK for Windows will no longer negotiate PCoIP connections using TLS 1.1.
Webcam Support
USB webcams now supported in a PCoIP session when connecting to PCoIP Agents for Windows. Use webcams with conference applications such as Microsoft Teams or Zoom in the remote desktop. For more information on this, see Webcam Support.
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 History
|
Version/Build |
Date |
Description |
|---|---|---|
|
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 | January 2020 | GA release |
| 20.04 | April 2020 | GA release |
| 20.07 | July 2020 | GA release |
| 20.10 | October 2020 | GA release |
| 21.01 | January 2021 | GA release |
| 21.03 | April 2021 | GA release |
|
|
Supported Clients |
|---|---|
| PCoIP Client SDK for Windows |
PCoIP Client SDK for Windows is compatible with the following Windows operating systems:
|
|
Supported Hosts |
|---|
| Teradici Cloud Access Software |
Fixed issue with client connecting to Cloud Access Connector (CAS Manager) that was configured for external access
Fixed an issue that prevented the client from connecting to a Cloud Access Connector server that is configured for external access.
Fixed issue with relative mouse that prevented moving windows.
Fixed an issue where the mouse position was fixed when attempting to drag a window with relative mouse enabled.
Fixed mouse coordinates for specific display topologies
There were a number of display topologies where the mouse coordinates were not accurately calculated. This resulted in the mouse pointer being drawn at the wrong locations. Some of these conditions occurred only when relative mouse was enabled.
USB driver conflicts with NoMachine software
The USB driver installed with the PCoIP Software Client for Windows has a driver conflict with the USB driver used by the NoMachine remoting software.
Remove the NoMachine software before installing the PCoIP client.
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.
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.
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.
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.
Audio input in PCoIP Software Client with PCoIP Remote Workstation Card does not work
When in session with a PCoIP Remote Workstation Card, PCoIP Software Client supports audio out from the host, but not audio into the host.