Release Notes
Client SDK for Linux 22.09
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.
This release introduces the following features and enhancements to the PCoIP Client SDK for Windows:
-
The Session Client Binary is no longer packaged with the SDK. In previous releases, the Client SDK for Windows included a session client binary package that was invoked by the SDK. This functionality is now provided by the standard PCoIP Software Client for Windows, which must be downloaded and installed separately.
Important: Existing Implementations must be updated
If you are upgrading from a previous version of the SDK, you will need to update your calls to point to the installed software client. For more information, see Session Client in the administrators guide.
For specific details about client functionality and capabilities, refer to the PCoIP Software Client for Windows Administrators' Guide.
-
Adds support for Windows 10 IoT. Windows 10 IoT 64 21H2 Enterprise LTSC is now supported.
-
Bug fixes and stability enhancements.
New Product ID for Intuos for Pro Small (PTH-640) Wacom Tablet is now supported
A new hardware revision of the Intuos Pro Small (PTH-640) Wacom Tablet has a different product ID than earlier hardware revisions. Support for this new product id has been added to the PCoIP client.
PCoIP client no longer tries to connect to the internet in closed network environments
Fixed an issue where the PCoIP client could attempt to make a connection to the internet at startup, and when establishing a connection.
Audio now works when connected to a Remote Workstation Card
Fixed an issue where audio in/out was not working when connected to a remote PCoIP Remote Workstation Card.
Audio output may stop working when switching devices
After switching to a different audio output device while connected to a remote desktop, audio output from the PCoIP client may stop.
Disconnect and reconnect the session after switching audio devices.
Audio disappears when audio-in is enabled
Audio output to speakers or a headset would stop after using audio input from a microphone.
Audio output may randomly stop
While connected to a remote desktop the audio output on the PCoIP client may stop.
Disconnect and reconnect the session after switching audio devices.
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.
Display arrangement appears different on remote hosts in DPI-unaware application
Windows applications that are DPI-unaware are presented with a scaled display resolution if the display has text and icon scaling enabled. This may result in display arrangements on the remote host appearing in different positions.
Windows remaps the display positions fixing the top left corner of a display at the same position if possible. If the reduced size of the display results disconnected displays, the display positions will be shifted so the displays remain connected.
Leave the client SDK configured as a DPI-aware application.
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.