VMware Horizon View Scanner Redirection: No Scanner Found

By | February 15, 2017

So, recently I was tasked to look into an issue at one our customers to check on a scanner redirection issue that had risen when the testing of the applications was being done on the Horizon View infrastructure.

The customer has an application that uses Twain for scanning, quick tests showed that:

  1. Scanning via Adobe Acrobat Pro was successful using Twain.
  2. Scanning via the application was not successful and the Scanner Redirection from VMware was reporting that the scanner was not found.

So the Scanner Redirection utility was introduced back in 6.02 agent and from my experience with Horizon View if you go delve into the installation directories you would always find hidden stuff, and my gem here was the “VMware Scanner Redirection for VMware Horizon 1.0.33 diagnostic utility

C:\Program Files (x86)\VMware\ScannerRedirection>”diagutil” command line specifi

VMware Scanner Redirection for VMware Horizon 1.0.33 diagnostic utility.

diagutil [help | /wks | /srv | /c | /bd | /sd “<APPNAME>” | /ds | /ic | /gr | /g
l | /q ]

help | /? – show this instruction
/wks – full workstation diagnostic
/srv – full server diagnostic
/c – copy TWAIN files
/bd – build date of components
/sd “<APPNAME>” – disable the substitution of user Windows directory for the APP
NAME. <APPNAME> – full path to the application’s executable file
/ds – set default TWAIN source
/ic – check system integrity
/gr – enumerate remote scanners and test connection state
/gl – enumerate local scanners
/iwia – install WIA driver
/q – quiet mode (without any dialog and output)

The diagnostics output upon using /wks switch which refers to full workstation diagnostics was:

C:\Program Files (x86)\VMware\ScannerRedirection>diagutil /wks

C:\Program Files (x86)\VMware\ScannerRedirection>”diagutil  /wks” command line


Local TWAIN scanners from TWAIN_32.dll DSM:
  VMware Virtual TWAIN Scanner (VMware)
  CanoScan LiDE 120 (Canon Inc.)

Local TWAIN scanners from TWAINDSM.dll DSM:
  The DSM TWAINDSM.dll could not be opened.

Local WIA scanners:


service is absent.
service is absent.
service is absent.

not running
running. PID 9336


[absent] C:\Windows\System32
[absent] C:\Windows\SysWOW64

[absent] C:\Windows\System32

[absent] C:\Windows\System32
[absent] C:\Windows\SysWOW64

[absent] C:\Windows\System32

[absent] C:\Windows\System32

[absent] C:\Program Files (x86)\VMware\ScannerRedirection

[2015.07.31] C:\Program Files (x86)\VMware\ScannerRedirection

[absent] C:\Windows\System32
[2015.07.31] C:\Windows\SysWOW64

[absent] C:\Windows\System32
[absent] C:\Windows\SysWOW64

[2015.10.15] C:\Windows\System32\drivers

[2015.03.23] C:\Windows\System32

[2015.04.9] C:\Windows\System32

[2015.03.23] C:\Windows\System32

[2015.03.23] C:\Windows\System32

[2015.07.31] C:\Windows\System32
[2015.07.31] C:\Windows\SysWOW64

[2015.07.31] C:\Windows\System32
[2015.07.31] C:\Windows\SysWOW64

[error:32] C:\Windows\en-US
[absent] C:\Users\s002\windows\en-US
[absent] U:\WINDOWS\en-US

[2015.07.31] C:\Windows\twain_32\ScannerRedirection
File Vesrion:
Product Vesrion:
[absent] C:\Users\s002\windows\twain_32\ScannerRedirection
[absent] U:\WINDOWS\twain_32\ScannerRedirection

[absent] C:\Windows\System32
[absent] C:\Windows\SysWOW64
[2010.11.20] C:\Windows
File Vesrion:
Product Vesrion:
[absent] C:\Users\s002\windows
[absent] U:\WINDOWS


  1. Logs showed that the scanner [CanoScan LiDE 120 (Canon Inc.)] was identified successfully by the redirection agent yet when attempting to scan via Twain we get that the TWAINDSM.dll cannot be opened.
  2. At that point in time Adobe was actually NOT using the scanner redirection by VMware, and I am sure it was using Twain because I had disabled the Windows Image Acquisition service.

After a fair amount of time trying to solve the issue:

  1.  To my knowledge when using WIA the scanner gets renamed to VMware WIA Scanner, and this also applies to Twain devices and as the diagnostics show the scanner is now named “VMware Virtual TWAIN Scanner“.
  2. I found an option within the scanning utility which enables us to keep the vendor names:

And you know what! It actually worked! This did the trick and the application was able to scan without any issues.

One more this, the tests were made on both the Windows endpoint and a zero client endpoint and both were successful, yet the process of configuration can be either done:

  1. Manually, upon the user login (from a Windows client, because from the SmartZero OS client the utility does not launch) the scanner redirection can be configured.
  2. Automatically, via GPO.

I hope this helps someone out there %).



954 Total Views 1 Views Today

Leave a Reply

Your email address will not be published. Required fields are marked *