1. Scanner redirection does not create a device on your virtual desktop that matches the name of the actual scanner. It creates a generic scanner in Device Manager called VMWare Virtual WIA Scanner (or VMWare Virtual TWAIN Scanner I am assuming). For us this stinks because the image capture software our client uses (Vertex by Jack Henry), has a prepopulated list of scanners you can select. So if we plug in a Canon-CR50 and select Canon CR50/80 in the application, it does not recognize that this scanner is attached to the virtual desktop.
2. You must install a TWAIN or WIA driver on your thin client. If you can't find a TWAIN or WIA driver, you are out of luck. For teller check image scanners, we have found no TWAIN or WIA drivers for the TellerScan TS-230, TS-240, or the Canon CR-55. We have found a TWAIN driver for the Canon CR-50 (from the Canon Europe site no less), but issue #1 above means we are out of luck.
there is a tick box option in the scanner preferences dialog box titled "Use vendor defined names for TWAIN scanners". This should solve the issue you mention and we added it specifically to cover the problematic use case you mention.
This only applies to TWAIN scans, WIA can't use the vendor name.
let me know how you get on,
Hey Peter is there anyway to enable this option by default so that no matter what user logs into a pool they will have the "Use vendor defined names for TWAIN scanners" on by default?
there is a scanner gpo file available in the gpo bundle. Im pretty sure (sorry not able to access it from here) but im pretty sure it allows you to push this setting as a gpo (eg for user/group/pool etc).
let me know how you get on,
Hey Peter I did try the "vdm_agent_scanner" template however it only gives me the ability to set the "Default Scanner" and "Hide Webcam" I don't see any options to force it to use the "Vendor Name" by default. Am I missing something?
hmm, yeah, you are right - sorry. just saw that myself...
however, ive done some digging and looks like you might be able to fix this through a policy that you create and push out:
HKCU\Software\VMware, Inc.\VMware VDM\ScannerRedirection TwainUseRealScannerName gets set to a DWORD = 1 when you click that tick box.
so, whilst this isn't supported in the current GPO provided you can push out this key then it should work for you.
Did you ever get this issue resolved. We are working with Vertex\Jack Henry and have the TS240 scanners. The issue we have is that the view desktop locks up after the scanner is initialized and then kicks the user out of view. The user can log right back in and their session is still open and they can use the scanner. If you have any ideas I would greatly appreciate your reply.
We have an unsupported fix, if you are into those!
We found that the issue is that Vertex calls the Orbograph engine and when Orbograph first initializes it will attempt to kill any processes that have a "p" and an "_" in its name. This was a poorly designed way for the program to ensure that another instance of Orbograph isn't already running. Of course you can see the problem is that since the pcoip_server_win32 has a "p" and an "_" it gets terminated and your session is disconnected. It will start right back up when you reconnect, and unless Vertex is launched again, you are fine.
The unsupported fix (from VMWare's perspective) is to rename the PCOIP_SERVER_WIN32.exe file to something like PCOIP-SERVER-WIN32.exe, and then do a search and replace in the registry, replacing the old file name with the new. I believe there is only one registry value that has to be changed.
I would strongly recommended that you contact Orbograph about this specific issue. We are no longer working with the client that experienced this issue, so it possible that Orbograph has released a patch.
Response from Orbograph support:
This is caused by a known bug in an older version of our
software. Please contact Jack Henry Vertex Support for an upgrade or hotfix.
Thanks and let me know if you have any questions.
Support Engineer | 978-667-6037 x5194 (O) | 888-ORBOGRA (Support)
peterbrown05 You seem to be very knowlegable about scanner redirection feature. Could you please explain what the normal operation of scanner redirection should look like. I am interested in TWAIN scanner redirection, since wia is working.
1) When you install scanner redirection functionality as part of view agent installation you get VMware virtual WIA scanner device in device manager, should you also get something like VMware virtual TWAIN scanner ?
2) when you connect to the VDI you have selected both WIA and TWAIN scanner redirection, but under all posible applications you see only Mware virtual WIA scanner as avaliable device.
Environment is Horizon view 7.0.2 and both VDI and client OS are Win7sp1 x64 and fully patched.
from what I remember... (it has been some time since i last worked with scanner redirection)...
the wia is a virtual driver which gets registered in device manager. However, the twain driver is a soft-driver and therefore doesnt appear in control manager
different apps will/wont work with twain (or wia), so I believe you will only see the twain option in an application if it explicitly supports it
for sure, the scanner redirection feature supports both twain and wia.
Peter is correct. Further more, I'd suggest you to try some applications which support TWAIN scan, like XnView, IrfanView. When you click "File -> Select TWAIN source" from the application menu, you should be able to see "VMware Virtual TWAIN Scanner 1.0" in the list. I attached a screenshot for your reference.
FYI, MSpaint and Windows Fax and scan only support WIA scan.