Release Notes

For Wacom Pen Displays, touch key for Display Settings does not work in PCoIP session. If user taps Wacom Display Settings touch key at the top right corner of the display, "Compatible display device not found" message would appear in Windows host and no response in Linux host.

The cursor mapping for the Wacom Cintiq 24 Pro P is incorrect and results in a cursor update flashing between the correct cursor position and the origin.

Using "Duplicate" mode will result in unexpected behavior around displaying your Windows desktop with the PCoIP Agent.

If uninstalling PCoIP agent in preparation for installing a newer version you must reboot before starting the new install.

PCoIP connections are made to the console, and appear as local logons to the server. For this reason, remote users must have local logon permission ("Allow log on locally") in the system's Windows configuration.

For example, if only administrators are allowed to log on locally, then only administrators could connect via PCoIP; anyone outside the administrators group could not connect.

A Windows update that has become unresponsive can show a busy cursor in the PCoIP session and prevent the user from interacting with the desktop.

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.

If the Leostream credential provider is installed, it can interfere with unlocking the desktop. The result is a lock screen with no controls to unlock the user.

Errors may occur when opening performance monitor and adding performance counters.

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.

This issue only affects Windows 7 and Windows Server 2008 SA.

After setting the Zero Client's tablet OSD setting to map to the non-primary display, pressing the Display Toggle function button on the tablet within PCoIP session does not map the Wacom tablet correctly to the monitors.

The issue can be seen in both local termination and bridged modes.

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.

After initiating certain Windows Updates, the update process may not complete until a user attempts to logon.  In these situations the PCoIP session will fail to establish while the Windows Updates completes and the WDDM driver is re-configured.

Subsequent connection attempts after the Windows Updates completes are successful.

Starting with Windows 10 1803, modern applications that attempt to access the microphone can be prevented from doing so.

A failure to upgrade the PCoIP Agent software includes the following error message in the logs:

ERROR:  An error occurred while uninstalling driver package 'C:\Program Files (x86)\Teradici\PCoIP Agent\drivers\Display\x64\tera_kmdod.inf' (Error code 0x57: The parameter is incorrect.)

c:\Program Files (x86)\Teradici\PCoIP Agent\drivers\Display\x64> pnputil.exe -i -a tera_kmdod.inf 

Wacom Cintiq 22HD does not work with Cloud Access Software PCoIP Agent for Windows with the latest Wacom Windows driver.

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.

If system restore is enabled, PCoIP agent installation on windows 7 platform might fail due to time out.

On Windows 7 and Windows Server 2008R2 there is a Microsoft feature to support digital identification called Windows Cardspace. Use of this feature will freeze your PCoIP session and prevent future connections.

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.

When executing pcoip-validate-license on either Windows or Linux an error is reported stating that 

This version of trusted storage is not supported.

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.

When using Windows Server without the RDS role installed, Windows will only support two concurrent user connections at most. If a third user attempts to initiate a PCoIP session, that login will be blocked, requiring the user to disconnect one of the other two sessions. This disconnect requires the user to have administrative rights on the machine.

If two different monitors are used and one or more displays is removed or added during a PCoIP session, there is a chance that one of the displays may get an incorrect resolution.

Enabling Windows Filter Keys will render user unable to unlock desktop.

Upgrading from Windows 10 to Windows 10 Anniversary Update (1607) performs an operating system re-install. After re-installing Microsoft Windows, only some device drivers are migrated to the new operating system. Since not all of the PCoIP Standard Agent software is migrated, it will need to be re-installed.

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.

Relative mouse is not supported by PCoIP Standard Agent, Graphics Agent, or Multi-Session Agent. The 'Relative mouse enabled' message does not display in client logs.

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

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.