Release Notes

Re-sizing the PCoIP Client window while participating in a PCoIP Ultra Collaboration session may cause the PCoIP client to crash.

When the collaborator client window is resized, cursor artifacts may be seen on the collaborator client momentarily.

The user will see significant screen artifacts if a PCoIP Collaboration session is started and PCoIP Ultra is not enabled.  Collaboration is only supported when PCoIP Ultra is enabled.

When connecting a Wacom tablet to a remote Apple silicon-based Mac, and when the host machine has a physical display that is not disabled, a mismatch can occur in the mapping of the locally rendered cursor to the remote cursor. This can cause the Wacom tablet to span all displays, including unusable local displays.

When upgrading PCoIP Graphics Agent for macOS through a remote PCoIP session, input from the user's mouse can be interrupted making it difficult to click the close button on the installer or restart the macOS machine.

When a guest collaborator connects to the host's session, the host's cursor may not be visible to the guest until it moves.

There are a number of limitations when remotely connecting to an Apple Silicon machine running Big Sur, including mouse input problems that prevent interaction with operating system.

When establishing a PCoIP connection to a macOS agent, the user provides their username and password in the PCoIP client. Once connected, the user is shown the macOS lock screen, which requires them to provide their password a second time.

When a session started with a wired connection is switched to a wireless network, the multi-channel audio quality deteriorates. The audio quality does not improve after switching back from the wireless network to a wired connection.

The remote macOS system does not automatically update its time zone to match the client's location.

Using a horizontal scroll wheel on a mouse or a horizontal gesture on a trackpad has no effect.

If a network interruption of greater than 60 seconds occurs during a PCoIP session to the PCoIP Graphics Agent for macOS, a dialog will appear indicating the session is reconnecting, but the connection is never restored.

Certain key combination, such as ctrl+arrow, are not sent correctly to the remote system.

Occasionally, a user may not be able to connect to a remote macOS agent.

Login prompts on the remote system will prevent a PCoIP session from starting.

The remote and client machines must be able to reach one another. If the firewall blocks network messages then a connection will not be established.

PCoIP connections will be denied if another user is already logged into the remote machine (for example, via the remote machine's user interface). This is true whether the logged-in user is using PCoIP or not.

In a PCoIP session using a PCoIP Client for macOS and a PCoIP Agent for macOS, and while the client is in focus, all keystrokes are sent to the remote system. Since Spotlight does not take focus when invoked, it will not receive keystrokes while the PCoIP client is in use.

Multi-media keys apply to the local client machine, and are not sent to the remote. This includes keys such as:

F7 - RWND/Previous  F8 - Play/Pause F9 - FFWD/Next song F10 - Mute F11 - Volume Down F12 - Volume Up

If the macOS agent machine's pcoip.connectionaddress_ value is set to the wrong IP address, PCoIP clients will not be able to connect.

Displays connected to the remote macOS machine are disabled during remote PCoIP sessions. In some cases, they may not be restored correctly after the PCoIP session is disconnected.

Changing mouse preferences (such as size) on the remote macOS agent machine has no effect. This happens because mouse settings are controlled by the client computer, not the remote host.

Copying images and text in a single action between the local and remote machines may not work as expected. This occurs in either direction, from the PCoIP client to the PCoIP agent or the reverse.

If your remote username contains spaces, the PCoIP agent will not be able to connect to it.