PCoIP Standard Agent for Windows 2.14 Release Notes¶

Release Overview

PCoIP Standard Agent 2.14.0 for Windows consolidates a number of new features and includes 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 Standard 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 Standard Agent 2.14 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, be sure to run the SupportBundler.exe application and include the output it generates.

Release Downloads and Documentation

Release History

Version/Build	Date	Description
2.14.0	August 2018	Beta Release

Compatibility

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

Resolved Issues¶

None.

Known Issues¶

Windows 10 version 1809 blue screen with Standard Agent (76528)¶

Standard Agent for Windows is not compatible with Windows 10 1809.

Workaround:

Do not upgrade to Windows 10 1809.

To recover after installing to Windows 10 1809:

Boot machine in safe mode.
Uninstall PCoIP Standard Agent.
Restart machine. Restore to previous windows 10 (refer link: [Go back to your previous version of Windows|https://support.microsoft.com/en-ca/help/12415/windows-10-recovery-options] )
After machine is up again. Run winver command to make sure windows has been reverted to previous version.
Check Control Panel and make sure PCoIP Standard Agent is no longer listed in Programs and Features.
Open Task Scheduler and delete TeraCleanupLogs task and TeraRestoreWDDMDriver task.
Install PCoIP agent

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.

First connection fails to connect after Windows update (72116)¶

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.

Workaround:

Attempt to login via PCoIP after a Windows 10 update. If the connection fails, then wait a few minutes for Windows Update to complete and for the PCoIP agent to restore its compoents and then re-connect.

Windows privacy settings can block microphone access (72039)¶

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

Workaround:

Through Windows Microphone privacy settings you may need to enable access to the microphone and allow the desired application to access it.

PCoIP Agent upgrade fails due to failure to uninstall the display driver (71940)¶

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.)

Workaround:

Issue the following command:

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

From the windows device manager, uninstall the Teradici PCoIP WDDM driver.
Reboot the VM.
Run the PCoIP Agent installer

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.

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.

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

Windows CardSpace interferes with PCoIP (66833)¶

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.

Workaround:

If you are unable to connect to your PCoIP session due to launching Windows Cardspace then you can connect to your virtual machine using RDP and close Windows Cardspace to re-enable PCoIP connectivity.

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:

Delete the contents of C:\ProgramData\Teradici\PCoIPAgent\licensing\5 in Windows, or /var/lib/pcoip-agent/licensing/5 (requires root permissions) in Linux
Restart the appropriate agent service (PCoIP Graphics Agent or PCoIP Standard Agent on Windows, or pcoip-agent on Linux)
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.

PCoIP connection may be blocked by existing RDP sessions (63331)¶

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.

Workaround:

Do not attempt to connect more than two users to a Windows Server system that does not have the RDS role installed.

Invalid resolution when hotplugging monitors (59421)¶

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.

Workaround:

Disconnect your PCoIP session and reconnect.

Windows Filter Keys are not supported for Windows 10 and Server 2016 (55978)¶

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

Workaround:

Disable Windows Filter Keys.

Operating system re-installation requires re-installation of PCoIP Standard Agent (54456)¶

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.

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.

Relative mouse is not supported by PCoIP agent (44176)¶

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.

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.

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.