Release Notes
Graphics Agent for Windows 24.10.0
-
The PCoIP Graphics 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.
Version 24.10 of the Graphics Agent for Windows contains bug fixes and stability enhancements. Additionally, it also includes the following features and changes:
Improvements to Bandwidth Utilization & Frame Rate Consistency
Version 24.10 introduces improvements to bandwidth utilization and frame rate consistency. When PCoIP Ultra is set to CPU Offload, Auto Offload, or GPU Offload, image quality is dynamically adapted to ensure consistent frame rates within specified ranges. This results in enhanced frame rate performance through improved image quality and optimized bandwidth consumption.
Improved Wacom and Xencelabs Tablet Responsiveness in High Latency Networks
Version 24.10 introduces improvements to the responsiveness of Wacom tablets and Xencelabs tablets operating in high latency networks. For this purpose, a new parameter has been introduced:
Improve graphics tablet responsiveness on high latency network
This parameter must be set on the host. Enabling it ensures smooth and consistent drawing on graphics tablets, even in high-latency network environments. This results in improved performance even if occasional packet drops are experienced.
For more information on enabling this parameter, see the Configuration Guide.
Note:
This parameter is only available if both the Anyware Client and the Anyware Agent are running version 24.10 or later.
New GPO Variable for SSO Access Control
In version 24.10, a new GPO variable has been introduced for controlling SSO access.
- Allow long user login times
When this setting is enabled, single sign-on does not wait for the Windows to start. Instead, the Windows loading screen is displayed.
Additional information about this variable is available in the Configuration topic of the Graphics Agent for Windows Administrators' Guide.
Windows agent Installation failed on OS with Finnish locale
Windows Agent installation failed on Windows with Finnish locale. This issue has now been fixed.
PCoIP Crashed at Startup When the Preferred Connection Address Was Unspecified
PCoIP session could not be established when the preferred connection address was not specified. The issue has now been resolved.
Packet Loss Due to GPU Decoding Errors Caused Blank Screens
Sometimes, sessions failed to start if network data was lost during the initiation of a PCoIP Ultra GPU offload session. This issue has been fixed.
Windows Graphics agent Deskside Displays Remained Blank
On some systems, it took longer to restore the visibility of the local displays causing them to remain blank even after the PCoIP session ended. Displays will now be restored at the end of PCoIP sessions even on systems that require more time.
Windows Agent SSO Failed On hosts With Many Network Printers
Sometimes, Single Sign-On login attempts timed out and failed on Windows host mapped to a large number of network printers. This issue was observed when the Allow long user login times GPO is enabled, and occurred because it took longer to find a printer, copy and install drivers and map it locally. This issue has now been fixed.
Session Bandwidth floor can now be set to a maximum of 900 mpbs
The maximum value that can be set for pcoip.devicebandwidthfloor has been increased to 900000 to enable configuring the PCoIP session to always assume it has 900 mbps of available bandwidth on the network. Setting such a high value can improve responsiveness and quality of imaging for situations where there is a very high quality, high speed network. Setting the bandwidth floor above the available networking infrastructure can lead to image artifacts and a poor session experience.
PCoIP Bandwidth floor maximum increased to 900 mpbs
The PCoIP bandwidth floor maximum has been increased to 900 mbps.
HP Anyware Connection Displayed Black Screen
Sometimes, black displays were observed on remote PCoIP connections after extended periods. This issue has been fixed.
HP Anyware Connection Displayed Black Screen
Sometimes, remote PCoIP connections would display a black screen after prolonged periods of inactivity. This issue has been fixed.
Anyware Session Failure with 144 Hz Displays
Connecting to an Anyware session from a client computer with a 144 Hz monitor attached might cause the Anyware connection to fail when a locally connected display cannot support that resolution.
- Remove all monitors connected to the host computer to enable connection.
- Set a limit maximum_framerate on the host to 60 to enable connection.
Data Protection Software on the Client Might Interfere with USB Forwarding Functionality
Data protection software, such as EgoSecure, which is installed on client machines might interfere with the USB forwarding functionality in PCoIP sessions.
Uninstall the data protection software.
Incorrect Japanese Characters on Windows host When Connecting from Linux or macOS Clients
When connecting to a Windows agent from a Linux or macOS client, the Japanese character "vu" is displayed in Katakana, even if the client and host are set to Hiragana. Other Hiragana characters work as expected.
No known workaround.
Caps Lock and Kana state can go out-of-sync when a Japanese keyboard is used
When a Japanese keyboard is used on the client side in a PCoIP session, the Caps Lock state can be out-of-sync on the host side if the Caps Lock key is pressed outside of the PCoIP client window.
On the client machine, set the input language to non-Japanese when a Japanese keyboard is used.
Do not press the Caps Lock key outside of the PCoIP client window when a Japanese keyboard is used.
If the Caps Lock state is out-of-sync inside a PCoIP session, disconnect and reconnect to the host.
Cursor Might Not Follow the Wacom Stylus on a Ventura macOS Client
When a Wacom tablet is forwarded from a Ventura macOS client, the cursor on the client might not follow the movement of the Wacom stylus.
On the Ventura macOS client: # Go to Apple menu > {}System Settings > Privacy & Security{}. # Click {}Input Monitoring{}. # Add the PCoIP Client app to the list, and turn on the ability to monitor your input devices.
Microsoft Teams Dialogs Do Not Appear on Windows Graphics Agents
On Windows Graphics Agents, Microsoft Teams dialogs for granting remote control are not visible on the desktop.
Disable accelerated capture and topology handling with pcoip.efe_enable_nvidia_grid set to 0 under the following registry folder: "Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Teradici\PCoIP\pcoip_admin. In addition to the poorer handling of topology changes, performance may also suffer.
Note: Classic Teams does not exhibit the same symptoms and can render the "share screen" elements correctly. Where possible, downgrade to Classic Teams.
PCoIP Client quits unexpectedly when exiting full screen while audio source is running (MacBook Pro)
Exiting full screen mode while an audio source is running may cause the session to quit unexpectedly. This issue affects clients running on recent MacBook Pro hardware.
Stop audio sources, including video with audio, before leaving full-screen mode to avoid this issue.
If the session does disconnect, reconnecting will resume the session.
The name of network shown in Anyware Health Monitor does not change during a session
In Anyware Health Monitor, the name of network shown will not change during a session even if the actual network changes.
For example, if an ethernet cable is pulled out and the system switches to WiFi, the name of network will not change in the Anyware Health Monitor display until the session is disconnected and reconnected.
USB flash drives cannot be connected to a remote PCoIP Agent
Starting with macOS Big Sur, mass storage devices are no longer permitted to be remotely connected to an external system via USB.
File sharing services can be used to share files.
Resizing collaboration session window causes crash
Re-sizing the PCoIP Client window while participating in a PCoIP Ultra Collaboration session may cause the PCoIP client to crash.
Avoid re-sizing client window size while participating in a PCoIP Ultra Collaboration session.
If this occurs, re-start the collaboration session by sending a new invitation to the Guest Collaborator.
MacOS support bundler issues
Several issues have been identified with the support bundler for the macOS client.
Upgrade to 22.07 onward & multi-monitor scenario
From release 22.07, multi-monitor scenario relies on the "Displays have separate Spaces" in Mission Control preferences on macOS client. "Displays have separate Spaces" must be selected for Anyware PCoIP session to work properly in full screen.
!MissionControlPreferences.png|thumbnail!
If it's unchecked then other displays may go to black in full screen mode.
Keyboard and Mouse Freeze when Connected to Remote Workstation Card in Windowed Mode
Keyboard and Mouse can freeze when connected to a Remote Workstation Card while the Soft Client is in windowed mode.
If this occurs, switch the client to full-screen mode to reestablish Keyboard and Mouse functionality.
Black Screen on Full Screen All Monitors
The PCoIP Client for macOS can generate an additional black desktop when going to full-screen all monitors on certain hardware configurations. This can appear as a black desktop in Mission Control, and one of your monitors may appear black.
Revert to PCoIP Client 22.04, or check "Displays have separated Spaces" in Mission Control Preferences on 22.07.0+.
!image-2022-07-18-12-00-21-601.png|thumbnail!
Starting a PCoIP session using a browser URI while another instance is running
If a PCoIP client instance is already running, attempting to launch a new PCoIP sesion with a browser URI will not work.
Close the running instance before launching a new instance.
In-session menu bar not hiding on MacOS
If the MacOS System Preferences option to "Never Hide Menu Bars" is enabled, the menu-bar will remain visible in the PCoIP session and results in a scroll-bar on the right side of the screen.
Disable the "Never Hide Menu Bars" System Preference on MacOS.
Menu can only be brought up on primary display
On the Software Client for macOS, when in full-screen all monitors mode, the in-session menu may only be available from the primary monitor.
If you are unable to make the menu appear on a secondary monitor, use local mission control, select full screen on that monitor to re-set focus on that screen.
Local spotlight search may not function
Local Spotlight Search may not function on the local machine while the PCoIP Client has an active session.
Client machine reboot interrupted while session is in progress
If you attempt to re-start your client Mac while your PCoIP client is in session, the session will terminate, but the Mac restart will be disrupted. When this occurs, you will have to close the PCoIP Client application and initiate the OS restart a second time.
Unresponsive Screen while Switching between Full Screen Modes
On the macOS Client, frequent switching between the Full Screen All Monitors mode, the Full Screen One Monitor mode, and the Windowed mode might result in one or more screens becoming unresponsive.
To fix the unresponsive screen issue, do the following:
- From the macOS Client menu bar, select View > {}Detect Monitors{}.
If this fails to fix the issue, end the PCoIP session and connect again.
Changing the audio sample rate during session
Changing the audio sample rate when using a media application while connected to a PCoIP session will cause distorted audio quality. To correct this audio quality issue, you will need to disconnect and re-establish the PCoIP connection.
Disconnect and re-establish the PCoIP connection to correct this audio quality issue.
Caps lock key does not work while in Legacy High Performance Mode
Caps Lock does not currently work in the PCoIP Client for macOS while in Legacy High Performance Mode
Use the Shift key instead.
Increased memory usage when switching between windowed and full screen modes
Frequent switching between window and full screen modes can result in increased memory usage.
macOS client only detects audio output device at session start
The macOS client will not detect a change in the audio output device while in session.
Disconnect and reconnect to the session when changing the audio output device.
PCoIP Client in window mode can be limited to 30 fps
For high resolution displays with dimensions larger than 3840x1600 the maximum fps will be limited to 30.
To enable up to 60 fps either set the client in full screen mode or reduce the window size to dimensions less than 1600 pixels.
Quitting Mac client while in-session, returns to the pre-session window.
The Mac client cannot be exit while connected to a PCoIP Agent. Selecting the Quit Teradici PCoIP Client system menu will disconnect the client and return to the pre-session window, but not quit the application. The client application will instead return to the saved desktop selection screen.
To quit the Mac client, first disconnect the session and then quit the client.
macOS client may only minimize one display on OS X 10.11
If you launch the PCoIP Software Client in OS X 10.11 and you have not clicked anywhere within the display before using the minimize hot key (Ctrl+Alt+M), the display that has not been used will not be minimized. This does not occur in macOS 10.12 (Sierra) or 10.13 (High Sierra).
Click with the mouse on both displays of the client any time before pressing Ctrl+Alt+M, and both displays will be minimized.
USB Flash drives fail to bridge at times
USB Devices dialog (from Connection > USB Devices menu) may freeze for a few seconds after clicking the connect or disconnect button associated with a USB Flash drive. When this happens after clicking connect, the device fails to connect. When this happens after clicking disconnect, the device is successfully disconnected.
USB DVD drive unavailable on client USB Devices dialog in macOS
If a DVD drive is connected to a client via a USB hub and the device is bridged quickly after connecting to a host, or if the device is unplugged from the hub and re-plugged, its status will be Unavailable and users will not be able to bridge the device.
macOS French localization disables View > Show Fullscreen toolbar menu
When the client locale is set to French in macOS, the View > Show Fullscreen/Leave Fullscreen dropdown menus may not be accessible.
Enter the Ctrl-Alt-Enter key sequence to toggle between fullscreen and windowed modes.
Datalogic barcode scanner cannot be redirected when bridged in macOS
The Datalogic Quickscan QS6500 barcode scanner does not work when the device is bridged.
Do not bridge the device. The device works as expected with the remote host when it is not bridged.
Wacom Intuos Pro and Intuos 5 tablets cannot be bridged
These tablets work as a pointing device when a session is not active, and when the tablet is not bridged while a session is active. When the tablet is bridged, the device manager application running on the remote host displays a warning icon next to the tablet and the tablet does not work.
Intuos PTH-660 and PTH-860 tablets are not impacted by this issue.
Avoid bridging Intuos Pro and Intuos 5 tablets.
USB keyboards do not work in bridged mode
Keyboards do not work when bridged. This affects both Windows and macOS PCoIP Software Client.
Do not bridge the keyboard. Keyboards function correctly when locally terminated.
Client window size is not remembered when crossing multiple monitors
When stretching the client window across multiple monitors, client window size is not remembered for session reconnects.
Zooming in macOS while connected to hard host throws local and remote mouse out of sync
Using the zoom button on PCoIP Software Client for Mac will result in a desynchronization of mouse pointers when connected to hard hosts. Teradici recommends not using the zoom button on macOS while in a PCoIP Software Client session connecting to hard hosts.
Mouse out of sync due to scaling in dual high-resolution displays
Connecting a PCoIP Software Client session with dual high-resolution displays in full-screen mode (2560x1600 for example) to a hard host that does not support high-resolution displays may result in unexpected behavior. For example, one or both displays may be scaled to single link DVI resolutions without the client also scaling, resulting in unsynchronized mouse movement.
Set client desktop to single link DVI resolutions. Alternatively, upgrade host GPU to support dual-link resolutions (Tera2 hosts only)
Audio input in PCoIP Software Client with PCoIP Remote Workstation Card does not work
When in session with a PCoIP Remote Workstation Card, PCoIP Software Client supports audio out from the host, but not audio into the host.