Release Notes

On 22.07.2  PCoIP Ultra GPU offload PCoIP sessions may experience lower FPS than previous builds. This symptom is more commonly seen on systems with resolution higher than 1920x1080.

22.07.0 Graphics Agent with GPU offload might experience following performance issues: 

• image pixelation due to image quality dropping to very low
• Bandwidth use dropping to very low results in low session FPS

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.

Fixes an issue where PCoIP connection would fail due to long connection time. Affected versions are:

• PCoIP Agent for Windows 21.01.0
• PCoIP Agent for Windows 21.01.1
• PCoIP Agent for Windows 21.01.2

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.

Drawing with a Wacom tablet can introduce sharp edges when quickly drawing curves. This is more likely to happen under any of the following conditions:

• Network latency greater than 25ms
• Using large tablets such as Intuous Pro (L) or Cintiq 24 pro or larger
• Drawing quickly

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.

Some applications may not be able to handle resolution change when they are running in full-screen mode.

Rarely, a user may be presented with the lock screen when connecting via PCoIP.

After starting (re-allocating) a previously stopped (de-allocated) VM in Azure, NVIDIA GRID licensing is not always enabled following VM boot up. This results in PCoIP sessions being limited to a single display with a maximum resolution of 2560x1600 pixels. Contact Microsoft Azure for help.

Display of cursors larger than 64x64 pixels can become truncated and can terminate the PCoIP session.

If you manually download a new version of the PCoIP Graphics Agent and run it from a mapped drive from within a PCoIP session, the update will show an error and plan to continue the update offline while the user is disconnected. If the software installer is located on a mapped drive that the local system account does not have access to, the update will fail.

If NVIDIA GRID is not properly licensed, connecting with multiple displays to a remote machine running PCoIP Graphics Agent may result in only one display being optimized with GRID performance. The other displays will work but will not be optimized with GRID, resulting in lower frames per second.

If an application sets the displays to 'duplicate', the user will be unable to restore the configuration to extend across multiple displays due to the controls being disabled.

A small number of occurrences have been reported where Windows will crash (resulting in BSOD) when resuming from Windows Hibernate, when installed on a virtual machine equipped with NVIDIA GPUs. For details on sleep and hibernate behaviors supported by NVIDIA, contact and visit http://www.nvidia.com/object/support.html.

'Enable pointer shadow' is not supported in a PCoIP session to Windows 10 PCoIP Graphics Agent.

In some cases, even though the performance counters have been installed correctly, it may appear as if they are not collecting data. This occurs due to the fact that the user may have opened the 64-bit version of the performance monitor, while Teradici's performance counters are 32-bit only. As the counters cannot be loaded into the 64-bit version, Windows will disable data collection. A corresponding message in the Windows Event Log should indicate this as well.

When upgrading to the latest PCoIP agent, audio volume is automatically set to maximum.

NVIDIA K520 cards with Video BIOS (VBIOS) 80.04.ED.00.07 are known to cause a GRID capture failure resulting in the PCoIP Graphics Agent falling back to BitBLT capture. The VBIOS version currently installed on the NVIDIA card can be found via the NVIDIA Control Panel under System Information.

When a host computer has more than one network adapter, the system must be configured to inform which adapter to use for inbound PCoIP connections. You can do so by populating the PCoIPConnectionAddress registry value with your desired network interface.

Some software applications such as Npcap can create a virtual network adapter that will present additional Ethernet adapters. These configurations also require populating the PCoIPConnectionAddress registry value with your desired network interface.

Teradici installs Microsoft Visual Studio 2013 C/C++ runtimes as part of the agent installation. Runtime installers create a system restore point which, on systems such as Windows 8, can take over 15 minutes. If the installer appears to be stalled when installing the C/C++ runtimes, it may simply be the runtime installers creating a system restore point.

The mouse pointer shadow, which gives the mouse pointer a 3D appearance, is not available during PCoIP sessions.