PCoIP Software Client 3.2.0 for Windows introduces new fixes and updates and enable customers to establish a PCoIP session with:
These release notes provide a summary of key additions, compatibility notes, resolved issues, and known issues for this release.
Fullscreen One Monitor
With this release, users now have the ability to switch to full-screen mode on a single monitor or on all available monitors using the new Show Fullscreen One Monitor or Fullscreen All Monitor commands listed under the View menu. Users can also toggle between windowed mode and last full-screen mode using the Ctrl+Alt+Enter (Windows) or Ctrl+Option+Return (Mac) hotkey.
Windows 10 display topology improvements
Improved display topology for Windows 10 clients, including better handling of display rotation and issues related to mouse alignment and window offsets.
Extended supported window alignments
Previously, display topology was limited to all monitors top, center, or bottom aligned. The display topology window alignment has been extended to any alignment provided all windows are connected.
Display resolution improvements
When a host requests a resolution change in full-screen mode, the host will be presented with supported client monitor resolutions only. Additionally, multiple monitor display topology handling has been improved with monitors that have different supported resolutions.
Added secondary default port 60443
The default port used to establish connections is port 443. If this port is already in use, the client will by default establish a connection on the secondary port 60443.
|July 2017||General availability release|
|PCoIP Software Client for Windows||
PCoIP Software Client for Windows is compatible with the following Windows operating systems:
Note: PCoIP Software Client for Windows does not operate with Windows Embedded Standard 7 or Windows Embedded Standard 8 systems.
|Teradici Cloud Access Software|
|Teradici Cloud Access Platform|
|PCoIP Remote Workstation Card|
Incompatibility between PCoIP Software Client for Windows and virtual KVM application Synergy
There is a known incompatibility between PCoIP Software Client for Windows and the virtual KVM application Synergy (http://symless.com/synergy). The Synergy application can interfere with the keyboard handling of the PCoIP client and cause sometimes a single or no keypresses to be transmitted to the PCoIP agent. This issue was observed with Synergy 2016 and may be present with other Synergy releases. (52396)
Workaround: Disable Synergy when using the PCoIP client.
Connection > USB Devices client dialog does not list any USB devices
At times, after a session starts, the Connection > USB Devices dialog does not list any of the USB devices connected to the client. (42270)
Workaround: Reconnect to the session or physically unplug and reconnect the USB devices connected to the client.
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. (41045)
Workaround: Avoid bridging Intuos Pro and Intuos 5 tablets.
Logitech Touch Mouse does not work when bridged in Windows
The Logitech Touch Mouse does not work when the device is bridged. This issue affects Windows PCoIP Software Client. (40960)
Workaround: Do not bridge the device. The device works as expected with the remote host when it is not bridged.
Cancelling large USB file transfer fails
Cancelling a large file from being copied to or from a USB flash drive while bridged in PCoIP software client fails to function. The file will continue to copy until finished. (40817)
Workaround: Do not try to cancel large file transfers.
SanDisk Cruzer USB devices do not work if the PCoIP session is disconnected while a file transfer is in progress
SanDisk Cruzer USB devices do not successfully re-bridge after the PCoIP session was disconnected during an active file transfer. (40769)
If possible, avoid disconnecting the device or the session while file transfers are in progress. If a disconnection does occur while transfers are in progress, physically unplug and reconnect the device to the client. If the device fails to mount as a mass storage device after the previous step:
USB keyboards do not work in bridged mode
Keyboards do not work when bridged. This affects both Windows and macOS PCoIP Software Client. (40580)
Workaround: Do not bridge the keyboard. Keyboards function correctly when locally terminated.
Reconnecting dialog takes up to one minute to appear from sleep mode
The reconnecting dialog on the PCoIP Software Client may take up to one minute to appear after waking up laptop from sleep mode (by opening the lid). Prior to the reconnecting dialog appearing, the client displays the last session content. (36363)
Windows client crashes when IP address is used as broker address
The Windows client will crash when an IP address is used as a Host Address (broker address). (32663)
Workaround: Use FQDN instead of IP address as a broker address.
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. (32597)
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. (29862)
Workaround: 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. (26355)
PCoIP Software Client now sends correct monitor EDID in full-screen mode to host
Previously, when the client was in full-screen mode, PCoIP Software Client sent the host a default EDID that might contain resolutions that were not valid for the connected monitors. Now, when a host requests a resolution change in full-screen mode, the host will be presented with supported client monitor resolutions only. Additionally, multiple monitor display topology handling has been improved with monitors that have different supported resolutions. (62446)
Client no longer limits display to 25x16 on a 4K monitor.
Previously, in windowed mode on a 4K monitor, the client limited the size of the display to 25x16 when the window was resized to a size larger than 25x16. This issue has been fixed. (61006)
Peer software version corrected in client log
The peer's PCoIP version has been corrected in the Peer Endpoint Advertisement section of the client log. (51943)