Release Notes
Standard Agent for Windows 21.01
-
The PCoIP Standard Agent 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.
-
When reporting issues to Teradici, run the SupportBundler.exe application and include the output it generates.
Release 21.01 of the Standard Agent for Windows includes:
-
A new configuration setting is now available for physical PC systems with local monitors. Previously, after disconnecting a remote PCoIP session, the physical machine's local monitors could be blank in some cases; turning this setting on causes the this setting causes the Standard Agent for Windows to restore the monitors to the local system.
-
Bug fixes and security updates.
None.
Soon to expire licenses can cause licensing failure for new host
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.
Wait until the following day in the timezone of the license server.
PCoIP single sign on will fail if a popup is shown on the secure desktop (Ctrl+Alt+Del screen)
When a popup is shown on the secure desktop e.g. "Incorrect password or username" or "Smartcard subsystem failure", PCoIP SSO cannot be started.
User will still get a PCoIP session when SSO failed, dismissing the popup and finishing logon manually will allow future connections to SSO successfully. A popup should also be dismissed automatically if no user activity is detected for 2 minutes.
PowerShell scripts cannot be executed by PCoIP Agent Installer
Folder where the PowerShell.exe binary is located is not present in the Windows system environment variable PATH.
Ensure that folders "%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\" and "%SYSTEMROOT%\System32" are present in the System variable PATH.
PCoIP Agent and PCoIP License Server commands have the same name
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.
It is advised not to install the PCoIP License Server and PCoIP Agent on the same machine
Wacom tablet bridging: Cursor issue with Windows Ink setting enabled
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.
Disable Windows Ink in Wacom Desktop Center. Applications which rely on Windows Ink feature may not work after turning off that setting.
Disabling Windows SSO disables vchan plugins
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.
Re-enable single sign on to ensure that vchan plugins start properly and both clipboard and printer plugins are available.
Wacom touch key for Display Settings does not work in a PCoIP session
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.
Do not use Wacom Display Settings touch key.
Duplicate mode in Windows is not supported with PCoIP Agent
Using "Duplicate displays" mode is not supported, and will result in unexpected behavior.
Connect to your virtual machine via RDP and change the Display settings to "Extend these displays".
Wacom drawing issues on Windows Server 2019
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.
Start Wacom Tablet Properties app, switch to Mapping tab, and uncheck "Use windows ink" option.
# For Photoshop users: Create a file “PSUserConfig.txt” with the following content. Place the file in "C:\Users*[User Name]*\AppData\Roaming\Adobe\
*# Use WinTab*
*UseSystemStylus 0***
Uninstall failure: unable to delete TeraCleanupLogs schedule task
Sometimes, PCoIP agent uninstall failed because it could not delete TeraCleanupLogs schedule task.
According to [https://superuser.com/questions/1475639/how-to-fix-broken-permissions-for-windows-scheduled-task], this is caused by security patch from Microsoft.
Go to C:\Windows\System_32\Tasks\
- Run the following command to find the hardlink to TeraCleanupLogs task.
fsutil hardlink list TeraCleanupLogs
- Delete the hardlink to the TeraCleanupLogs task.
Users are unable to connect if they do not have "Allow log on locally" permission
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.
Adjust the value for "Allow log on locally" to include the groups that include the users who need to access this machine.
PCoIP connection may appear unresponsive during Windows update
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.
In some cases, users may be able to resize the window in order to gain access to the Windows task bar, and select "Update and Restart" to complete the process. If the user is unable to access the task bar, contact a system administrator to restart the machine.
PCoIP session ends when using very large application window
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.
Do not stretch a window more than 4096 pixels, horizontally or vertically.
Cannot unlock session if Leostream credential provider installed
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.
Uninstall the Leostream credential provider.
Performance monitor errors
Errors may occur when opening performance monitor and adding performance counters.
Use the following Windows command to correct issues with the performance monitor:
lodctr.exe / R
License registration is unreliable in KVM environments
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 tablet cannot be mapped to non-primary display on Windows 7 and Server 2008
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.
If monitor mapping is required for the Wacom tablet, only map the tablet to the primary display in the Zero Client's tablet OSD and in the Wacom properties.
PCoIP Agent fails to start
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
Reboot the machine.
PCoIP Agent refuses connection with licensing error
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.
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
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.
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
Starting with Windows 10 1803, modern applications that attempt to access the microphone can be prevented from doing so.
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
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.)
- 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 tablet PTH-451 not detected
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
When USB bridging a Wacom tablet to a Windows agent the cursor position is not updated while working in Windows INK.
Starting with PCoIP Agent 2.15 and when using Zero clients with a minimum firmware of 6.2.0.a2, Teradici recommends using local termination for the Wacom tablet. This allows the cursor to be properly displayed in Windows INK.
Windows Interactive logon text interferes with PCoIP session connection
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.
You can either disable interactive logon text or you can disable the PCoIP SSO.
Installation timeout in Windows 7 when system restore is enabled
If system restore is enabled, PCoIP agent installation on windows 7 platform might fail due to time out.
Disable system restore
Windows CardSpace interferes with PCoIP
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.
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
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.
Rebooting the VM can restore proper licensing functionality.
PCoIP validate license reports unsupported version of Trusted Storage
When executing pcoip-validate-license, the following error is displayed:
This version of trusted storage is not supported.
-
Delete the contents of C:\ProgramData\Teradici\PCoIPAgent\licensing\5 in Windows, or /var/lib/pcoip-agent/licensing/5 in Linux (requires root permissions).
-
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
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.
Rebooting the machine may resolve the WMI impairment, enabling PCoIP licensing to be successfully acquired.
PCoIP connection may be blocked by existing RDP sessions
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.
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
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.
Disconnect your PCoIP session and reconnect.
Windows Filter Keys are not supported for Windows 10 and Server 2016
Enabling Windows Filter Keys will render user unable to unlock desktop.
Disable Windows Filter Keys.
Operating system re-installation requires re-installation of PCoIP Standard Agent
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
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.
To solve the issue:
- Click Start, click Run, type cmd, and then click OK.
- Type the following command, and then press Enter:
mmc.exe /32 perfmon.msc
. This command runs System Monitor in 32-bit emulation mode. - Use System Monitor to determine whether the performance counter object is available.
Relative mouse is not supported by PCoIP agent
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
When upgrading to the latest PCoIP agent, audio volume is automatically set to maximum.
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
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.
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
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.