Skip to content

PCoIP Graphics Agent for Windows 2.14.0 Release Notes

Release Overviev

PCoIP Graphics Agent 2.14.0 for Windows consolidates a number of new features as well as including product and security updates.

These release notes provide a summary of key feature additions, compatibility notes, resolved issues, and known issues for this release.

What's New in This Release

Release 2.14.0 of the PCoIP Graphics Agent for Windows includes the following new features:

  • Improved framerates for low bandwidth video playback
  • additional imaging controls for choosing between high framerate and high quality in bandwidth contrained environments
  • ability to enable or disable the synchronization of timezone from the client
  • introduce support for Bloomberg STB100 and FRE100 keyboards when used with PCoIP Zero clients
  • improved diagnostics for when sessions can't be started

Important Notes and Requirements

  • PCoIP Graphics Agent 2.14.0 for Windows requires a license registration code (for Teradici Cloud Licensing), or a license activation code (for Local License Servers). If you are a new user, request a registratration code for a full evaluation.

  • New Cloud Access Software license purchases or renewals can only be activated using PCoIP Agent 2.11 or newer (any agent type).

  • When reporting issues to Teradici, run the SupportBundler.exe application and include the output it generates.

Release Downloads

Related Documents and Software

Release History

Version/Build

Date

Description

2.14.0October 2018General Availability


For compatibility details, refer to System Requirements in the administrators' guide.

Resolved Issues

NVidia driver signing mismatch causes degraded connection (75268)

Now fixed a fully optimized session can be established.

PCoIP Agent can now read the pcoip-agent.conf configuration file. (73200)

File permissions for /etc/pcoip-agent/pcoip-agent.conf will now automatically be set to the required values.

Known Issues

PCoIP Agent fails to start (72726)

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

Workaround:

Reboot the machine.

PCoIP Agent refuses connection with licensing error (72286)

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.

Workaround:

This problem was caused by WMI's inability to get host UUID. When running

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

The workaround is to restart Windows Management Instrumentation and PCoIP Agent for Windows service in sequence in Control Panel -> Administrative Tools -> Services. If the services won't restart then restarting Windows will resolve the issue.

Wacom Cintiq 22HD does not work with Cloud Access Software (71924)

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

Workaround:

Use a Wacom Intuos Pro tablet instead of the Cintiq display model.

Windows resolution change options are disabled after uninstalling PCoIP agent (71751)

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

Workaround:

open regedit.exe , navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System and set the value NoDispCpl to 0.

Wacom tablet PTH-451 not detected (71425)

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.

Windows INK cursor location not updated (70173)

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

Workaround:

None

Windows Interactive logon text interferes with PCoIP session connection (69794)

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.

Workaround:

You can either disable interactive logon text or you can disable the PCoIP SSO.

Wacom tablet cursor fails to highlight some UI elements (68947)

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

Workaround:

Remove long right mouse click from the pen settings in Windows.

Installation timeout in Windows 7 when system restore is enabled (67818)

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

Workaround:

Disable system restore

Cloud Access Software indicates no license (66566)

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.

Workaround:

Rebooting the VM can restore proper licensing functionality.

PCoIP validate license reports unsupported version of Trusted Storage (66075)

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

This version of trusted storage is not supported.

Workaround:

  1. Delete the contents of C:\ProgramData\Teradici\PCoIPAgent\licensing\5 in Windows, or /var/lib/pcoip-agent/licensing/5 (requires root permissions) in Linux

  2. Restart the appropriate agent service (PCoIP Graphics Agent or PCoIP Standard Agent on Windows, or pcoip-agent on Linux)

  3. If using Teradici Cloud Licensing (not using a local license server), re-register the host.

Licensing can fail if Windows WMI infrastructure is impaired (65660)

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.

Workaround:

Rebooting the machine may resolve the WMI impairment, enabling PCoIP licensing to be successfully acquired.

Changing window resolution while running a full-screen application may cause issues (63089)

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

Workaround:

Exit affected applications before changing desktop resolution.

Initial PCoIP connection on Azure may result in blank display (62483)

With PCoIP Graphics Agent on Azure, display may not be properly initialized on the first connection. You may get a blank display.

Workaround:

Disconnect and reconnect, or resize your PCoIP client window.

User may be required to log on twice (61632)

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

Workaround:

Authenticate a second time to gain access to the desktop.

GRID licensing fails after disabling then enabling GRID capture. (61247)

GRID licensing fails after disabling NVFBEnable -disable then enabling NVFBEnable -enabling GRID capture, resulting in limitations in the number of monitors and resolutions available.

Workaround:

Teradici has included, as part of the PCoIP Graphics Agent install, a reset script to reset the graphics driver to a good state:

C:\Program Files (x86)\Teradici\PCoIP Agent\GRID\reset_grid.bat

You'll need administrator permissions to run the script. Before running the script, close all other applications, especially those that utilize the GPU. Teradici also recommends you disconnect and reconnect once the script has completed.

GRID licensing not enabled after re-allocating an Azure VM with GRID 4.2 (369.95) driver (61088)

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

Workaround:

Restart Windows.

Cursor size larger than 64x64 pixels does not display correctly (57721)

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

PCoIP Graphics Agent upgrade after disconnecting may not work on mapped drives (55408)

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.

Workaround:

Copy the installer to a local drive first.

Multiple display issue occurs when NVIDIA GRID is not properly licensed (52157)

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.

Workaround:

Ensure NVIDIA GRID GPU is properly licensed.

Duplicated screens in-session (51912)

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.

Workaround:

Open the Projector Menu by pressing Windows key + P, then select Extend.

NVIDIA GPUs do not support Windows Sleep and Hibernate system power states (S3/S4 respectively) (51788)

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.

Workaround:

Avoid sleeping and hibernating PCoIP Graphics Agent that is configured to utilize NVIDIA GPUs.

Cursor pointer shadow is not supported with Windows 10 (45095)

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

Performance counters do not appear to collect data (45092)

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.

Workaround:

To solve the issue: 1. Click Start, click Run, type cmd, and then click OK. 2. Type the following command, and then press Enter: mmc.exe /32 perfmon.msc. This command runs System Monitor in 32-bit emulation mode. 3. Use System Monitor to determine whether the performance counter object is available.

System volume set to maximum after agent upgrade (42226)

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

Workaround:

Manually set the audio to the desired volume after upgrading. Once set manually, the audio volume is maintained. The change in audio volume only happens at upgrade.

GRID capture fails with K520 card using VBIOS 80.04.ED.00.07 (42099)

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.

Workaround:

Update the VBIOS on the K520 card to the latest version. VBIOS 80.04.D4.00.03 is known to work.

PCoIP agent fails to connect when host has multiple NICs (40825)

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.

Workaround:

In HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Teradici\PCoIPAgent, set the PCoIPConnectionAddress registry value:

"PCoIPConnectionAddress"="a.b.c.d"

Where a.b.c.d is your desired network interface). The type of the reg key is a string value: REG_SZ.

Agent installation may take a long time (22702)

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.

Mouse pointer shadow is missing (1870)

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