USB redirection bloomberg keyboard 2013

[Imanb83]

Hi all,

for several clients we are managing a VDI environment with the 'old' big white keyboards the fingerprint reader redirection was working properly.

Bloomberg is currently providing new keyboards to there clients which are black (also the VID_PID id changed)

With all the default policy they keyboard functionality works naturally however the fingerprint does not, and it almost looks like if my policies don't work. (screenshots below) the policy works it is more as if the vmware agent doesn't uses these settings.

• Vmware view server: 6.1.1 build-2769403
• OS. windows 7 x64
• Agent version: 6.1.1 (I can upgrade this one if needed)

Thin clients:

• Windows based Wyse Z90S7 (primary test TC)
  • VMware horizon client 3.5.2.30397
• and also Wyse D50D

Attached is my policy for the Wyse windows thin client (gpo bloom.PNG)

But also the gpo results where is shown that the settings are there (gpo result bloom.PNG)

the relevant part of the  logfile on the same thin client looks like this:

My guess is that the hid device (interface 2) is the fingerprint reader which i would like to forward to the device.

2016-09-12T12:26:49.051+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: Device Filter got device:
2016-09-12T12:26:49.051+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: Device id: Vid-1188_Pid-9545
2016-09-12T12:26:49.051+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: Path: bus-1/2_port-01
2016-09-12T12:26:49.052+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: Config count: 1
2016-09-12T12:26:49.052+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: Config num: 0
2016-09-12T12:26:49.052+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: Interface count: 6
2016-09-12T12:26:49.052+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: Interface [0] - Family(s): keyboard
2016-09-12T12:26:49.052+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: Interface [1] - Family(s): keyboard
2016-09-12T12:26:49.053+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: Interface [2] - Family(s): hid
2016-09-12T12:26:49.053+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: Interface [3] - Family(s): audio
2016-09-12T12:26:49.053+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: Interface [4] - Family(s): audio,audio-out
2016-09-12T12:26:49.053+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: Interface [5] - Family(s): audio,audio-in
2016-09-12T12:26:49.053+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: [Combined:Phase] Starting 1(a)
2016-09-12T12:26:49.054+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: [Combined:Phase] Finished 1(a)
2016-09-12T12:26:49.054+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: [Combined:Phase] AutoDeviceSplitting blocked. Skipping 1(b)
2016-09-12T12:26:49.054+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: [Combined:Phase] Starting 2
2016-09-12T12:26:49.054+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: audio-out is blocked using AutoFilter setting. The setting is ignored as there are multiple audio interfaces which shouldnt be split
2016-09-12T12:26:49.055+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: [Combined] Device blocked by AutoFilters. Family(s): keyboard
2016-09-12T12:26:49.055+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: [Combined:Phase] Finished 2
2016-09-12T12:26:49.055+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: [Remote:Phase] Starting 3
2016-09-12T12:26:49.056+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] DevFltr: [Remote:Phase] Finished 3
2016-09-12T12:26:49.056+02:00 DEBUG (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] Filter Result: [UsbDeviceId: 4000000211889545] Device 'Bloomberg Keyboard 2013' is blocked
2016-09-12T12:26:54.640+02:00 INFO  (0AF8-0B3C) <vmware-usbd> [vmware-view-usbd] mmfw_PipeRead: called (client @ 5C53D8)

[Imanb83 · Accepted solution]

i figured out the problem, i have been trying to configure the thin client with the AGENT template, but i must use the CLIENT adm template...

really silly mistake.