PCoIP Remote Workstation Card Agent for Windows 19.05 Release Notes¶

Release Overview

The PCoIP Remote Workstation Card Agent 19.05 for Windows introduces additional functionality to the PCoIP Remote Workstation Card with PCoIP Host Card software.

This release provides support for the PCoIP Broker Protocol, which allows connections to the Remote Workstation Card machine to be brokered by Teradici Cloud Access Manager, or by a third-party broker such as Leostream.

This is the first release of the Remote Workstation Card Agent for Windows.

Important Notes and Requirements

PCoIP Remote Workstation Card Agent 19.05 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.
You can use either a Cloud Access license or a Cloud Access Plus license to activate your PCoIP session.
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
19.05.0	May 2019	General Availability

Resolved Issues¶

None.

Known Issues¶

System may crash when uninstalling or upgrading Remote Workstation Card Agent for Windows on Windows 10 build 1803 and Windows Server 2019 VM (75664)¶

When uninstalling or upgrading Remote Workstation Card Agent for Windows on an Windows 10 build 1803 or Windows Server 2019 VM, the system may crash.

Workaround:

Reboot the system before uninstalling or upgrading Remote Workstation Card Agent for Windows.

Remote Workstation Card Agent for Windows fails to start (72726)¶

The Remote Workstation Card Agent for Windows requires port 60443 for proper operation. Unavailability of this port prevents the agent from starting.

The following Remote Workstation Card Agent for Windows 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.

Remote Workstation Card Agent for Windows refuses connection with licensing error (72286)¶

The Windows Management Instrumentation service can run into a bad state, which prevents Remote Workstation Card Agent for Windows 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 Remote Workstation Card Agent for Windows 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 Remote Workstation Card Agent for Windows 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 Remote Workstation Card Agent for Windows to restore its compoents and then re-connect.

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

If system restore is enabled, Remote Workstation Card Agent for Windows 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 Remote Workstation Card Agent for Windows licensing to be acquired. If the Remote Workstation Card Agent for Windows 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.

Operating system re-installation requires re-installation of PCoIP Remote Workstation Card Agent for Windows (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 Remote Workstation Card Agent for Windows 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.

System volume set to maximum after agent upgrade (42226)¶

When upgrading to the latest Remote Workstation Card Agent for Windows, 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.

Remote Workstation Card Agent for Windows 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.