VMware Horizon Community
lfavreto
Contributor
Contributor

Issues with USB pass-through - RFID pad

Hi there,

I work for a Library and we use RFID gates / Pads for our items.

We use Horizon View 7, some Windows thin clients (10Zig 5800) and some Teradici Zero Clients (PCOIP). We are trying to implement RFID pads to a new branch, and the USB pass-through is giving me a hard time.

I have it set at the branch were I work from, and it does work without any issues. If I apply the same settings (local policy adm) to another thin client at the new branch, the device does not connect. Even if I bring the same working computer from my branch to the new branch, it fails to connect. Thin Clients have the latest version of Horizon View.

More pieces to the puzzle, the Zero clients at the new branch work perfectly. Only issue is with the 10Zig thin clients.

The device It is a FEIG RFID pad (VID-0AB1_PID-0002) USB composite device with 2 interfaces, a keyboard (which I am splitting) and an HID input (Vendor - allowed Vip/Pid). I got this info from the debug logs.

Policies are all set on the host side, USBs to auto connect and so on.

-----------------

2018-02-22T16:30:50.797-05:00 DEBUG (15B4-1174) <vmware-usbd> [vmware-remotemks] LookupDeducedFamily(): found 2

2018-02-22T16:30:50.797-05:00 DEBUG (15B4-1174) <vmware-usbd> [vmware-remotemks] LookupDeducedFamily(): Called for non vendor specific

2018-02-22T16:30:50.797-05:00 DEBUG (15B4-1174) <vmware-usbd> [vmware-remotemks] DevFltr: Device Filter got device:

2018-02-22T16:30:50.797-05:00 DEBUG (15B4-1174) <vmware-usbd> [vmware-remotemks] DevFltr: Device id: Vid-0ab1_Pid-0002

2018-02-22T16:30:50.798-05:00 DEBUG (15B4-1174) <vmware-usbd> [vmware-remotemks] DevFltr: Path: bus-1/1/0/0_port-01

2018-02-22T16:30:50.798-05:00 DEBUG (15B4-1174) <vmware-usbd> [vmware-remotemks] DevFltr: Config count: 1

2018-02-22T16:30:50.798-05:00 DEBUG (15B4-1174) <vmware-usbd> [vmware-remotemks] DevFltr: Config num: 0

2018-02-22T16:30:50.798-05:00 DEBUG (15B4-1174) <vmware-usbd> [vmware-remotemks] DevFltr: Interface count: 2

2018-02-22T16:30:50.798-05:00 DEBUG (15B4-1174) <vmware-usbd> [vmware-remotemks] DevFltr: Interface [0] - Family(s): vendor

2018-02-22T16:30:50.798-05:00 DEBUG (15B4-1174) <vmware-usbd> [vmware-remotemks] DevFltr: Interface [1] - Family(s): keyboard

------------------

The sites are connected by TLS from ISP. Port 32111 is allowed on out end.

I have a case opened with support, but logs are taking some time. I've been working on this for a bit now, and cannot wrap my head around it.

Any suggestions would be appreciated.

Thank you in advanced!

0 Kudos
2 Replies
JeffSchaef
Contributor
Contributor

We are dong something similar.  And found we had to add the Vendor ID (VID) and Product ID (PID) to the z-client USB Bridged area.  You can do this through the teradici manager and set it through the profiles or if you connect to the Web GUI of the z-client it is in the Permissions then select the USB drop down menu and you will see the 2nd Image.  Then just add the values of your device.  Ours is for a badge reader and I think we got these values from the manufacturer and i do know they are also available in Windows device manager - somewhere buried in the device details.  If you can't find these reply back and I will see if I can help.  Good Luck

pastedImage_0.png

pastedImage_1.png

0 Kudos
lfavreto
Contributor
Contributor

Thank you.

Our Teradici Zero clients run without problem, by allowing any / any.

Our issue is with the Windows Thin Clients.

Cheers

0 Kudos