Yes, this can explain why the content scroll one time( because the first move event is sent to vdi desktop) and then stop( because the vdi desktop is un-grabbed, so mouse event is not sent to vdi desktop). From your description, it seems a native application(Google Chrome on your Win) steal focus from the Horizon vdi desktop window while scrolling, so the vdi desktop window is un-grabbed.
Thanks very much for your detailed investigation.
#Vmware horizon view client 4.0 update
Will try to update VMWare tools on the master to the latest, but I know we then have a ping issue ( ping loss vmware tools 11 ) I'm seeing on my current desktop 3 mice in the device manager: 2 using VMware driver 12.5.7.0, one using MS driver 3.1
#Vmware horizon view client 4.0 drivers
Looks like we have narrowed it down to this single Desktop, running W2K19.Īll VDI desktops are running vmware tools 10.3.5, but the W2K19 got a driver update on the NIC and VMIC drivers via MS Update Tried a published app on an W2K19 RDSH and there scrolling works fine.Īlso tried a VDI Desktop running Windows Server 2008R2 and also there scrolling works fine. I can see this because I'm typing now, then scrolling, then trying to type again and just hear the "error" sound like you're trying to click behind a modal form if you understand what I mean? When I keep moving my mouse while scrolling, it works fine and I can continue to type in the textboxīy default BLAST protocol is used, I just changed to PCoIP, but same problem persist. I also noticed while typing in this textbox and trying to scroll I'm loosing focus on the current window, which would explain why the scrolling stops. If I click again in the window I can scroll again one time again. When you scroll, the contents move one time then stop. Desktop = Windows 2019 Server with latest updates. Same issue in any application (Outlook, Chrome, Explorer. Until now I only tested on full Desktop (single user, no RDSH). Local computer = Win with latest updates Tried multiple mice, both wireless and wired, all have the same issue (rules out HW)
0 kommentar(er)
