VMware Horizon Community

Scanning issues via USB redirection

Hello! Posting this in the hope someone can shed some light on this issue as ive been struggling with it for the past few weeks now! We are currently experiencing an issue with Scanners connecting via USB Redirection. (Yes, I know we should be using 'Scanner Redirection'! However this doesn’t appear to be compatible with the main scanning software we use which is Kofax)


Scenario as follows:

  1. USB Scanner is connected to host via USB and scanner is powered on

  2. The Scanner in question is usually a Fujitsu scanner (This issue is not affecting all scanners, or even all Fujitsu Scanners, but is affecting Fujitsu FI 7160 and Fujitsu FI 7180 scanners among others models and manufacturers)

  3. User logs onto Horizon desktop session

  4. USB scanner is automatically passed through successfully to the VM

  5. Once logged on, the scanner appears both as a device within 'printers and scanners' and within device manager.

However the following symptoms are then present:

  1. Upon launching our scanning software (ie. Kofax, or any of our other software that relies on Kofax) and then attempting to scan, the user receives an error 'Mini Port driver not present' or ‘no device found’

  2. If the driver is manually reinstalled within device manager with admin credentials within that session, it will then function correctly.

  3. If the scanner is not plugged in via USB to the thin client when the Horizon session is launched, and is then plugged in after a couple of minutes or so, it will occasionally work (but this is intermittent)


Probably the most important thing I have found so far when investigating is that the issue seems to at least be linked in some way to the App Volumes Client version in use on our system. If using App Volumes Agent version 2.18.4 and above, we have this issue. But when I created a duplicate pool and rolled back the client to version 2.18.1, it worked fine. I have found a thread on the VMWare communities where someone else is experiencing this issue but there’s no fixes or solutions in that thread: https://communities.vmware.com/t5/App-Volumes/AppVolumes-2-18-4-Broke-USB-Redirection-for-Scanners/m...

The version of the App Volumes Client that we are currently running in our live environment is version 2.18.6. I have also since tested App Volumes Client version 2.18.10 (ie. the latest 2.x.x version) and this presents the same issue as 2.18.6, meaning upgrading does not look like an option.

The drivers are currently installed within an appstack, but I have also recently tried installing the drivers into the golden image and I still had the same issue.

Thanks for reading this, any help whatsoever would be extremely appreciated!

Our current live environment is as follows:

OS: Windows 10 Enterprise LTSC v1809
App Volumes Agent Version: 2.18.6
Horizon Agent Version: 7.13.1

App Volumes Server Version: 2.18.6
Horizon Server Version: 7.13.1

OS: Windows 10 Enterprise LTSC v1809
Horizon Client: 5.5.2

0 Kudos
1 Reply

Use scanner redirection rather than USB redirection and a good TWAIN driver.  (we also have a bunch of  Fi7160s)  Initial deployment was USB redirection (bad advice!)  and we ran into similar issues.

in Appvols review your logs and exclusion lists to exclude the vmware paths specifically to the usb arbitration service. 

0 Kudos