![]() ![]() ![]() 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. Bridging USB Keyboard and Mouse devices over high latency networks.Poor network conditions from the client to host.There are many causes for Keyboard and Mouse issues. MAC: If it is your first time connecting into a mac, you'll have to enable the security and privacy settings on the mac in order to gain keyboard and mouse functionalities.When connecting to a remote session the keyboard and mouse do not work, the input is sporadic, the input lags, the cursor doesn't appear or the mouse is out of position.Open the Streamer application on the remote computer -> Advanced -> Checkbox hardware accelerator. Enabling the hardware accelerator setting in the Streamer may help as well.If it is connected, try disconnecting and reconnecting. If the remote computer has a wireless (bluetooth) keyboard and mouse connected, check to see if it is currently connected.To check, you can toggle your monitor to switch between the two. When utilizing the multi-monitor feature, if there is one monitor on your end (local) and two monitors on the remote end, it is important to make sure that you are on the correct monitor.If this is the case, please refer to the tips below: Often times users may run into an issue where they initially connect into their remote computers using Splashtop but are unable to control the mouse and keyboard. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |