I'm trying to find out if this is common issue or if there is something I may be missing.
I am using HP Thin Clients with WES9.
I have attempted to connect to two different USB Scanners (HP 5950 and Fujitsu 6240z). I have the drivers installed on the the Thin Client and on the Virtual Desktops.
Through VCenter I am able to connect to these scanners from my deskop using the USB direction in ESX.
I cannot however, from a Thin Client, connecting through the View Client to a virtual desktop get either of these scanners to be redirect or install for use.
If this is a common problem and I'm better off using a a network scanner, or a USB to Ethernet adapter, or a product like RemoteScan, then fine.
I've thouroughly checked the communities and knowledge base. My next step would be to call support, but I thought I would see what the community has to offer first.
Thanks for any info you may have.
If you launch VMware view client from your desktop or Laptop and connect scanner , do you see USB scanner getting redirected ? Are you using PCOIP or RDP ? Can you try redirecting USB drive ?
I’m using PCOIP. If I launch the View client a Thin Client I do not see the scanner getting redirected. Autoconnect USB devices is selected and the scanner is listed under the Connect to USB device drop down. If I select the scanner, it disappears from the thin client and the virtual desktop receives shows the “new hardware has been detected” bubble for split second then instantly gives a message that the device failed to install. When looking in device manager the new device is listed as a Generic USB Hub and is listed under devices and printers as VMware Virtual USB device 01.
USB thumb drives and printers redirect and work fine. It seems my problem is specifically with scanners (Twain or ISIS drivers)
If you launch view client from your desktop not from thin client and use RDP. Can you let me know the result.
I guess I should have mentioned that in my original post. If I launch the view client from my desktop and use PCOIP (we don’t use RDP), it does work as intended. It is only through the thin clients that the issue exists. The thin clients are HP T4750e with WES9 installs, and view client 5.1 I have tried it with view client 5.0.1 and 5.2 as well. I’ve checked the bios for anything that may cause an issue without success. I’ve disabled the firewall to be sure as well, still no luck.
I have attached the exact error message received when I click on the scanner from the dropdown of the View Client.
Then, I think it is thin client and its embedded view client is causing problem. I think it will be good if you can raise support request with thin client vendor so that they can contact VMware with there analysis for further investigation.
The view client isn’t embedded. It was downloaded from VMware and installed on the Thin client. It is the same install that I have on my desktop. However, It couldn’t hurt to get HP involved to see if they have any insight with the Thin Client.
What is underlying OS of thin client, if it is win xp, can you see if view client logs are available or not.
The location of View Client log files:
C:\Documents and Settings\%username%\Local Settings\Application Data\VMware\VDM\Logs\
In case if you have scanner drivers installed on the thin client, I can suggest you the solution.
This will work in case if the scanner is operable on the thin client (can you launch scanning software on the thin client and scan there?)
Scanner for Remote Desktop creates virtual scanner on the remote side and maps your local scanner (plugged to the Thin Client) to that virtual device.
The only requirement in such case, you need to login to remote side over RDP or Citrix.
This solution works fine in my company for a long time. What is important that is allows to redirect both TWAIN and WIA, and isolates redirected scanners within user session in multi-user environment.
I really hop this will help you.