Release Notes

Graphics Agent for Windows is only supported when running on Windows for x86/x64 hardware. Windows for ARM is currently not supported.

Following a successful smartcard authentication, the PCoIP Agent process may crash if the smartcard is removed while the session is being established.

When connected to a Windows Agent using a smartcard and the network latency is greater than 50 milliseconds (ms), the smartcard reader may appear as "card not inserted" while the card is inserted.

When this occurs, the user may be able to use the smartcard to connect to the session but is unable to or inconsistently able to use the smartcard in-session.

Wacom tablets hot plugged to Zero Clients that are connected to Windows Agents might not appear in the USB menu. If tablets, are repeatedly hot plugged, the sessions might stop responding.

When the Bloomberg Keyboard 5 firmware upgrade process starts, the Bloomberg Biometric module gets disconnected from the PCoIP session, and the upgrade becomes unresponsive.

A resolution mismatch might occur in connections to Windows Graphics Agents where the main display is on the right and the orientation of a secondary display is set to portrait.

When connecting/disconnecting repeatedly without logging out of the session, multiple instances of the collaboration manager icon may appear in the system tray.

Re-sizing the PCoIP Client window while participating in a PCoIP Ultra Collaboration session may cause the PCoIP client to crash.

When the collaborator client window is resized, cursor artifacts may be seen on the collaborator client momentarily.

When a guest collaborator connects to the host's session, the host's cursor may not be visible to the guest until it moves.

When a webcam is connected to a remote desktop, the browser on the remote desktop may terminate.

When a session started with a wired connection is switched to a wireless network, the multi-channel audio quality deteriorates. The audio quality does not improve after switching back from the wireless network to a wired connection.

Power save is an operating system feature where the screen goes black after some time to save power. This event will cause the PCoIP Graphics Agent to crash.

If a license server is operating in a different timezone than the PCoIP Agent and a license is still valid in the timezone of the PCoIP license server but considered expired in the timezone of the PCoIP Agent, then a PCoIP session can be denied with a licensing error.

This issue only affects hosts that do NOT have a valid license granted previously.

If you are unable to start a session with PCoIP Ultra GPU Offload or Auto Offload enabled it may be due to a lack of GPU memory. This can be verified by looking for "out of memory" in the PCoIP server log.

When a popup is shown on the secure desktop, for example "Incorrect password or username" or "Smartcard subsystem failure", PCoIP SSO cannot be started.

During normal operation the PCoIP Graphics Agent for Windows will populate information about remoted displays into the NVIDIA graphics stack. This information is provided by PCoIP clients either for the real displays they have attached or a virtual display when the client is run windowed.

This information is left populated in the NVIDIA driver between PCoIP sessions to improve re-connection times. It is also left populated if the Agent software is uninstalled.

Folder where the PowerShell.exe binary is located is not present in the Windows system environment variable PATH.

ZoomText cursor and magnification features get internally disabled when launched with Windows Graphics Agent versions post 20.01.

When both the PCoIP Agent and PCoIP License Server are installed on the same machine, they will both try and create the command pcoip-list-licenses and pcoip-support-bundle, which causes one to overwrite the other's command. Whichever is installed or updated last will be the one that the command will map to.

When a Wacom tablet is running in bridged mode in a PCoIP session, the cursor may not be shown correctly with Windows Ink setting enabled in the Wacom Desktop Center.

After connecting Wacom tablet in local termination mode, display toggle is not supported in the PCoIP session.

It has been observed that in a a dual display scenario, with one display rotated the NVIDIA driver version 44166 (branch 441_58) does not apply custom resolution to the right display. As a result, the rotated display comes up as black.

NVIDIA licensing limits the size and number of displays that can be connected. This document: [https://docs.nvidia.com/grid/latest/grid-vgpu-user-guide/index.html#physical-gpu-display-resolution-handling] shows that the GPU may enforce a maximum of 1, 2, or 4 displays and may limit resolution as low as 1280×1024 for a single display.

Using the Windows-P key combination to adjust projector display types is not supported. Using this key combination and selecting "duplicate" may cause secondary displays to turn black.

Enabling the Wacom tablet's force proportions setting will limit the tablet area to match the aspect ratio of the display, but the PCoIP Client misinterprets the cursor location and displays the cursor in the wrong place.

Using a display topology outside of the what the AMD GPU instance supports, display problems can occur. These issues include:

• Non functional displays
• Imaging artifacts
• Loss of accelerated capture support

Portrait-oriented displays with a vertical resolution greater than 2160px are not currently supported by Cloud Access Software on AMD GPUs.

Display resolution may not work correctly on Windows Server 2019 instances when using the GRID 9.1 driver.

Vchan plugins are launched when the PCoIP session begins. If the system has single sign on disabled, then the PCoIP session cannot login the user desktop and the vchan plugins cannot start properly. This causes multiple issues including loss of clipboard synchronization and lack of printing support.

The "Display Settings" touch key for Wacom Pen Displays does not work in a PCoIP session. Windows hosts display a "Compatible display device not found" message when the user taps the touch key. Linux hosts do not display a message.

While using a Wacom tablet in a PCoIP session on Windows Server 2019, pen pressure is detected but drawing with the Wacom stylus does not work.

*# Use WinTab*
        *UseSystemStylus 0***
        

Sometimes, PCoIP agent uninstall failed because it could not delete TeraCleanupLogs schedule task.

fsutil hardlink list TeraCleanupLogs
        

In some cases, the graphics driver may not be ready when the initial PCoIP connection is established on an AMD GPU Microsoft Azure instance. When this occurs, not all expected displays will be available.

PCoIP supports a maximum application window width of 4096 pixels.  If an application window is stretched across multiple displays with a total width or height greater than 4096, the PCoIP session will end.

Retrieval of the VM_UUID can be unreliable when running under KVM. This can cause licensing failures when attempting to validate a license or start a session.

Wacom functions like clicking with the pen, side-buttons on tablet, and pen pressure sensitivity, do not work.

The PCoIP Agent requires port 60443 for proper operation. Unavailability of this port prevents the agent from starting.

The following PCoIP Agent log message can appear: AGENT :0894 Failed to bind required address ssl://127.0.0.1:60443: Cannot bind to port

The Windows Management Instrumentation service can run into a bad state, which prevents PCoIP Agent from checking out a valid license. When this problem occurs, user will see the "no license" error on the client and should see the following error message in the PCoIP agent log:

Exception caught ( Error processing FNE capability response: [1,7E2,5,0[7000001B,0,C03F9]]  Response does not match system hostid. ) while sending a request for license renewal.

wmic csproduct get UUID
        Node - TERVDIW10DEV22
        ERROR:
        Description = The paging file is too small for this operation to complete.

Windows display settings to change resolution are grayed out after uninstalling the PCoIP agent.

Wacom tablet PTH-451 may not be detected correctly when USB bridged to Cloud Access Software Agent for Windows with PCoIP software client for Windows. Software client for macOS and PCoIP Zero Clients work as expected.

When USB bridging a Wacom tablet to a Windows agent the cursor position is not updated while working in Windows INK.

Configuring Windows logon text will cause a PCoIP user to be unable to connect using the PCoIP client.  This is because the Single Sign-On implementation within PCoIP needs to be able to authenticate directly to the user desktop.

When moving the Wacom pen across the desktop some program controls do not highlight properly.

Connection via PCoIP can fail stating a lack of license even though the system is properly licensed.  Additionally, issuing the pcoip-validate-license.ps1 command can fail resulting in a crash dump.

Windows infrastructure failures can prevent PCoIP agent licensing to be acquired. If the PCoIP agent is not licensed, the user will not be able to connect to the remote machine.