Slow Performance When Zooming In and Out of CAD Applications Using the Mouse Wheel

Resolved by LC8976 which fixes an issue where the Citrix graphics driver receives an incorrect mouse location from the operating system.

To enable the fix, set the following registry key:


Name: DisableAppendMouse


Data: 00000001

However, when you use the HDX session after setting the registry key, certain features that programmatically set the mouse pointer location might not work as expected. The features are:

  • Mouse Snap To feature.
  • The capability to synchronize mouse location between users with GotoMeeting screen sharing.
  • The capability to synchronize mouse location between users with Skype for Business screen sharing.


How to disable two finger and three finger gesture/tap in Citrix Reveiver for Andorid


How to disable two finger and three finger gesture/tap in Citrix Reveiver for Andorid


The two finger tap for Mouse pointer and the three finger tap for the keyboard will be disabled if the user used “Multi-Touch Mode”

In the InSession Menu, user have to toggle to Multi-Touch Mode by tapping the above shown icon twice.


  • No Related Posts

Server-rendered cursors: Performance analysis and optimization

In a Citrix Virtual Apps and Desktops environment, mouse cursors are presented to a user in one of two ways in an ICA session: client-rendered or server-rendered.

In most cases, mouse cursors are client-rendered. By default, the HDX graphics process will detect OS and application cursors on the VDA (server side), capture the cursor image and send to the Citrix Receiver or Workspace App for rendering locally on the client. A client-rendered cursor delivers the best performance and user experience as it behaves the same as with any local application running on the physical endpoint. This means there is no added latency to the mouse movement from the virtual session.

There are two special cases where client rendering of the cursor is not possible for a particular Citrix session and the mouse cursor is server-rendered as a result:

Custom cursors (non-Windows standard)

There are some applications that use proprietary cursor types and handle cursor rendering on their own. These applications do not use the standard Windows OS functions to set and render cursors on screen. In this scenario, the application cursor looks no different to the HDX graphics process than any other image on screen. Because of this, it is not possible to query the Windows OS and detect the cursor in use in order to redirect for client rendering.

AutoCAD from Autodesk is a common example of an application that uses custom cursors.

Lack of cursor compatibility with HDX Graphics and Citrix client in use

This is more of case with modern applications running in Citrix sessions configured with HDX Legacy Graphics mode and older Receiver clients. Not all cursors are created equal. Modern and more complex types such as 32-Bit color cursors may require use of new HDX graphics mode and recent/current versions of the Citrix client.

Performance Impact

Server-rendered cursors can be very costly for virtual desktops and applications. Every time the user moves the mouse, the client sends a message to the server, so the desktop or application can be redrawn and the resulting image (the new cursor position) is sent back to the client. This process may need to be executed hundreds or thousands of times to capture every change in cursor position, depending on the user movement of the mouse. This can generate high-bandwidth and, if the application is very complex (Ex. a complex CAD model where the application is recalculating the part), it can become a bottleneck. It can also result in a lot of redrawing of transient intermediate frames that are unnecessary, intermittent information that a user doesn’t need, like when scrolling or moving a window rapidly.

In this scenario, a user may perceive a slight delay when interacting with a server-rendered cursor because they are interacting with a graphical representation of the cursor that is being remoted across the network instead a local cursor rendered directly on the client hardware. The issue would be more apparent in low bandwidth and high latency network conditions. A user on a local area network may not perceive the issue compared to a user connecting over a WAN link, for example. The graphics mode and display configuration in use may also be a contributing factor. Using the H.264 video codec would perform a lot better than the lossless codec, just like a session on a 1080p display would be much better than on a 4K display.


SEPM – Block all HID devices using GUID unsuccessful for keyboard

I need a solution

Attempting to block all HID (Human Interface Devices; keyboard, mice, etc) via GUID.

In SEPM we blocked using the baked in GUID called “Human Interface Devices”. It successfully blocked the mouse.

However the keyboard, a Dell CN-0N6R8G-PRC00-83U-00CZ-A03, still worked.

Went to device manager and verified the GUID Class ID for the keyboard was the same as the baked in HID we blocked in SEPM:


Any ideas why it worked to block the mouse, but not the keyboard?

Any ideas to remedy and block the keyboard too? We want to block all keyboards, not just this specific one. We want to block them all to create a whitelist of approved devices.




External keyboard and mouse not functioning when un-dock then re-dock

Scenario – The Citrix Admin opened a case with Citrix Support when they noticed users were reporting the following:

We are using Thinkpad laptops with dock station. When we un-dock the laptop for a meeting, it works on the mouse pad and built-in keyboard. However, when we dock it back, the keyboard and mouse are detected, search for driver and then switch for Citrix Remote USB device. And they no longer function, even on the local client

The issue is not noticed with Receiver 4.5

With 4.8, it works if they plug the mouse and keyboard directly into the laptop instead of the dock station.

With 4.9, we need to reboot the laptop because they both do not work even plugged into the laptop directly.


XA 7.x: Mouse click settings in ICA session.

ICA session inherits the mouse settings that you have on your client machine where you are launching the Citrix app or desktop from.

This is irrespective of mouse settings on VDA.

For example, if I have right handed mouse settings on client and I launch app from that machine, it will redirect right handed mouse setting.

Now if I want to change the mouse to left handed mouse in ICA then I need to set the mouse setting to left handed mouse on client machine.

Making changes in registry on VDA for that particular session for mouse settings doesn’t change this behavior.


Add finger print scanner device as a default hardware device based on class

I need a solution

In our enviourment the users has finger print scanner device. We have different OU for each location as its a PAN India project. On these OU all USB is blocked expect human interface device (keyboard/mouse). But now the users have been provided with a new usb finger print scanner device.

This device is getting blocked as we insert in the system but as the application gets installed it start working without any restriction. As the policy is getting bypassed.

Kindly check this issue.