Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all articles
Browse latest Browse all 179681

Horizon View - USB Check Scanner

$
0
0

We are attempting to implement USB check scanners in our VDI environment, and having significant issues. I was hoping anyone that has implemented this in an environment like ours may have some helpful advice.

 

All end users connect to our Horizon View environment through a Wyse P25 zero client. They log into a Windows 10 v 1803 desktop that has View Agent v. 7.8 installed (with scanner redirection and USB redirection enabled).  We are testing three different vendor models of USB check scanners (Digital Check, Panini, Burroughs). For each check scanner, we are getting different results. Sometimes the scanners will work successfully, some times they receive errors, sometimes not at all.

 

To add further confusion, after logging into the Windows desktop, Windows device manager does recognize the scanner and labels it “VMware Virtual WIA Scanner”. The issue we are having is the vendor image capture software that uses the scanner – has a prepopulated list of scanners you have to select. So if we plug in a Digital Check TS240 and select Digital Check TS240 in the application, it does not recognize that this scanner is attached to the virtual desktop.

 

After looking up some older threads, our initial thought was to use the VMware "Scanner Redirection Preferences" system tray icon and  enable the option "“Use vendor defined names for TWAIN scanners”. After working with VMware support, they stated that a Wyse P25 zero client is not supported with Horizon View scanner redirection. This was somewhat verified since we do not see the "Scanner Redirection" system tray icon when logging into Windows. But confuses even more because how the scanning will "sometimes" work.

 

Any help would be greatly appreciated.


Viewing all articles
Browse latest Browse all 179681

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>