![]() ![]() To fix the issue, try using the client in full screen as the true EDID of the software client's display is used. When a topology miss match occurs the mouse will not work correctly as the absolute co-ordinates the clients sends are incorrect. If for some reason the GPU and PCoIP Remote Workstation Card do not set the same resolution due to the GPU not supporting the resolution, the display topology will miss match. The PCoIP Remote Workstation Card and GPU will try to set the requested resolution. When the PCoIP Software client connects to the host card it sends a requested topology. If you can connect and get partial mouse movement, there maybe a display topology miss match. Without the PCoIP Host Software the local keyboard and mouse will not work on the remote machine. When connecting via the Software Client to a Remote Workstation you must ensure that the PCoIP Host Software is installed. Connecting from a Software Client The Mouse only moves on part of the display or not at all Ensure the PCoIP Zero Client is running the latest firmware if you experience issues with locally terminated mice. This means that local cursor functionality must be turned off in the PCoIP Host Software. ![]() Some mice do not work properly locally terminated and must be bridged. If other keys must be used, it is recommended to enable USB bridging for the keyboard connection through the AWI to get around this limitation. When using a locally terminated keyboard connection, the only keys can can be used as a "modifier" key for hotkey shortcuts are Ctrl, Shift, and Alt. Unable to use _ key as a modifier key for hotkey shortcuts in applications. Ensure there is enough reliable bandwidth for the PCoIP Remote Workstation Card connection to function correctly. When the available bandwidth drops due to network loss or high latency it can cause the USB data to stop and reset once conditions return to normal. The Mouse and Keyboard stop functioning intermittently before working again. The results of mouse actions such as clicking and dragging have a delay appearing on the screen but it gives an greatly improved user experience. This allows the PCoIP Zero Client to render the cursor locally so it moves in sync with the users mouse movement. This terminates the keyboard and mouse on the zero client and only transmits the keyboard input and mouse co-ordinates to the host rather than the default of bridging the USB data. In these scenarios HP Anyware recommends the installation of the PCoIP Host Software and enabling the local cursor functionality. ![]() In a WAN or Remote Access scenario the natural network latency maybe in excess of 40 ms. If you are on a LAN investigate why such a high latency exists between the PCoIP Zero Client and PCoIP Remote Workstation card. The AWI for the PCoIP Remote Workstation Card and PCoIP Zero Client indicate the round-trip latency is in excess of 40 to 60 ms. Some possible resolutions are: Remote Workstation Card Connecting from a Zero Client The Mouse cursor and keyboard input lag behind the user's input.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |