Release Notes
Client SDK for Windows 23.06
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.
In addition to bug fixes and stability enhancements, the Client SDK for Windows introduces the following:
High Performance Client Mode is Now Default
The Client SDK for Windows's high performance client mode is now enabled by default, and recommended for most users. Previously, this mode was available as a technology preview. The previous standard mode can still be enabled by switching to Standard Performance Mode, if desired. For more information, see Client Modes in the Software Client for Windows guide.
Collaboration Manager Opens from In-Session Menu
The Collaboration Manager can now be launched from a new Collaboration menu option in the Client SDK for Windows's menu, in addition to launching from the system menu bar. For more information, see Sharing Your Session With Collaborators in the Software Client for Windows guide.
New Anyware Modes Information Dialog
Information related to PCoIP Ultra acceleration modes is now available via the Connection Health Indicator on the Client SDK for Windows interface. A tooltip has been added next to Mode on the Anyware Health window, which opens the Anyware Modes dialog containing a brief description on the PCoIP Ultra acceleration modes.
PCoIP Ultra modes are configured on the PCoIP agent. For more information, see PCoIP Ultra Modes in the Software Client for Windows guide.
Bloomberg Keyboard Support
Bloomberg Keyboards 4 and 5 are now supported when connecting a Client SDK for Windows to PCoIP Agents for Windows. For more information, see Bloomberg Keyboard Support in the Software Client for Windows guide.
None.
Microphone Does not Function with Kaspersky Anti-Virus
On Windows Client running on a desktop with Kaspersky Anti-Virus installed, forwarding of a local microphone to the remote desktop may be blocked. If this happens, the microphone cannot be used in the PCoIP session and Kaspersky Anti-Virus shows that {}"{}Receiving the audio stream for the application is blocked."
The PCoIP Client must be whitelisted in Kaspersky Anti-Virus in order to allow the audio stream for the application to be forwarded. Refer to Kaspersky for instructions on how to whitelist an application for audio stream access.
The name of network shown in Anyware Health Monitor does not change during a session
In Anyware Health Monitor, the name of network shown will not change during a session even if the actual network changes.
For example, if an ethernet cable is pulled out and the system switches to WiFi, the name of network will not change in the Anyware Health Monitor display until the session is disconnected and reconnected.
Intel UHD driver causes Windows memory leak
Intel UHD driver version 30.0.101.2079 causes a memory leak with PCoIP Software Client for Windows. When this occurs, the client system will slow significantly and may require a restart to recover.
This issue impacts Intel Integrated GPUs when used with 4k (UHD) monitors.
Other driver versions may also have this issue.
To avoid this issue, install an Intel UHD driver that is not affected:
- Version 30.0.101.1069 or earlier, or
- version 31.0.101.3729 or later.
Updating the driver to a version that is not affected resolves the issue.
Audio Input from microphone may stop after a long period of inactivity.
The microphone for a remote session may stop working if not used for a long period of time.
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.