How it works

Special tool from VirtualHere company for USB redirection. One device for each thin client for free
Post Reply
akatik
SUPPORT
SUPPORT
Posts: 417
Joined: Mon Jan 17, 2005 6:30 pm
Contact:

How it works

Post by akatik » Mon Apr 08, 2019 3:18 pm

USB devices redirection is complicated! If you need tor edirect USB flash, specify in configuration file:

Code: Select all

disk=usb
Smartcard or USB-token may be redirected only by special smartcard redirection via RDP. Windows won't work with smartcard redirected as USB device. Here's the manual about smartcard redirection: https://wtware.com/docs5/smartcard.html

Common USB printer redirection is easier by one of printer redirection ways: https://wtware.com/docs5/printer.html

USB varcode scenners: http://wtware.com/docs5/config.html#serial

USB scanners: http://wtware.com/docs5/config.html#scanner

USB devices redirection is needed for:
* Multifunction devices, scanners and barcode scanners, if there's no driver in WTware for such device,
* Canon CAPT printers,
* cameras, mobile phones and tablets,
* techological devices etc.

VirtualHere allows to redirect single USB device from each thin client for free. VirtualHere is easier and in some cases works better thaт Windows-embedded USB redirection via RDP.

Attention! We are not VirtualHere developers. We don't know how VirtualHere works and we can't advise on possible ambiguities with redirected devices. Not any USB device may be redirected over network. Before USB redirection of your device on WTware thin client, test how this USB device is redirected via VirtualHere to your terminal server from any other Windows computer.

1. On the page "Linux USB Server" download "Generic VirtualHere USB Server Builds" for needed architecture. WTware works on three architectures: i386, AMD64, ARM.

All Raspberry Pi versions are ARM architecture. So for Raspberry you are to download VirtualHere USB Server for Linux (ARM), file vhusbdarm.

Common x86-compatible computer may be i386 or AMD64. Boot WTware on needed computer, place mouse in the right bottom corner and look at popup window. If near WTware version you see UEFI word, it's 64-bit WTware, and you are to download VirtualHere USB Server for Linux (AMD64), file vhusbdx86_64.

If there's no UEFI word near WTware version and logo, then WTware for i386 architecture works on this computer. You are to download VirtualHere USB Server for Linux (i386), file vhusbdi386.


2. WTware terminal must receive the file you downloaded. If terminal boots by network or from local disk, but downloads it's configuration files by network, you should save this file into Everyone directory in TFTP server root. By default it's:

Code: Select all

C:\Program Files (x86)\WTware\TFTPDROOT\Everyone
If WTware terminal boots from it's local disk and stores configuration on local disk, open terminal we-interface and place the file into configs directory.

3. IN terminal configuration file you are to specify:

Code: Select all

vhusb = on
That's all. Now terminal during boot will download from TFTP/HTTP or from it's local disk the file with VirtualHere and will run it. On Windows terminal server run VirtualHere and specify terminal IP. You will see the list of all terminal USB devices, that may be redirected.

Additional options

You may tell VirtualHere to redirect definite USB device:

Code: Select all

vhusb = 1234:ABCD
USB IDs of all connected to terminal devices you may see on terminal web-interface in USB bus section.

Broadcast messages, in order not to enter terminal IP:

Code: Select all

vhusb = UseAVAHI
In VirtualHere there are many options: https://www.virtualhere.com/configuration_faq To use them you are to create your own package and specify needed options in your config.ini in this package: viewtopic.php?f=27&t=48783

Post Reply