Redirect only buttons\HID from usb headset into virtual machine

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #43953
    bartlomiej.belko
    Participant
    • Total Post: 14
    • Regular Joe
    • ★★

    Is it possible redirects only pushbuttons Human Interface Device (HID, not the same headphone audio) to the virtual machine? We want inside the virtual machine the possibility of using these buttons, for instance to mute a conversation in Lync or also perform connection through headphones to press the key that is “on cable” headphones or drop a call.
    It is possible when using HDX RealTime Optimization Pack (RTOP) but using it we have another problems with audio and video

    What we have already tested (settings in WNOS.ini):
    Option 1 – Try to force the entire device (Audio and controls) into the VM
    Device=vusb ForceRedirect=0x047f,0xc01c,0x01,0x01,0x00 Type=HDX
    Device=vusb ForceRedirect=0x047f,0xc01c,0x03,0x00,0x00 Type=HDX
    Audio and HID is redirected into VM and there is a poor audio quality – about 4times more bandwidth usage during Lync call when compare it with no redirection. We cannot accept it

    Option 2 – Audio local and try to force the interface into the VM via HDX
    Device=vusb ForceRedirect=0x047f,0xc01c,0x03,0x00,0x00 Type=HDX
    Audio and HID is redirected into VM which provides poor audio quality as in option 1

    Option 3 – Audio local and try to force the interface into the VM via HDX
    Device=vusb ForceLocal=0x047f,0xc01c,0x01,0x01,0x00
    Device=vusb ForceRedirect=0x047f,0xc01c,0x03,0x00,0x00 Type=HDX
    Audio and HID is redirected into VM

    #43956
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    If the device has more than one USB ID (one for audio, one for HID), then it should be possible.
    You can also try with InterfaceRedirect=yes (Device=vusb ForceRedirect=0x1,0x1,0x1,0x1,0x1 Type=HDX InterfaceRedirect=yes)

    Other than that, no way.

    CG

    #43967
    bartlomiej.belko
    Participant
    • Total Post: 14
    • Regular Joe
    • ★★

    I tried this:
    Device=vusb ForceRedirect=0x047F,0xC01C,0x03,0x00,0x00 Type=HDX InterfaceRedirect=yes
    and this:
    Device=vusb ForceRedirect=0x047F,0xC01C,0x01,0x01,0x00 Type=HDX InterfaceRedirect=yes

    but in both cases the whole device was redirected into VM – both audio and HID part. Anyone has ever been able to do this?

    #43971
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    That was the only option I could think of.

    CG

    #49480
    Axell
    Participant
    • Total Post: 9
    • Regular Joe
    • ★★

    bartlomiej.belko, ConfGen hello.

    We have the same case and the same result. (redirect Jabra Evolve 20 into VM through Wyse thin client)

    We also try ForceLocal, but in all options the same result. So as we guess in all options there is only full device redirection.

    #49485
    Twilley
    Participant
    • Total Post: 33
    • Frequent Flyer
    • ★★★

    VMware Solution: This is an example of a PowerMic II

    You could SPLIT the composite device, so we can leave some of the components locally on the ThinOS device.  Group Policy settings are required.

    Horizon Agent:

    We turned off “Allow Auto Device Splitting” so we could control the process.

    We setup the GPO to “Split Vid/Pid Device.

    o:vid-0554_pid-1001(exintf:00;exintf:01;exintf:02)

     

    How did we determine the Interface numbers?

    From the VMware Client debug logs (on a Windows PC) you can determine the sub-interfaces of a composite device.  C:\ProgramData\VMware\VDM\logs\debug-*.txt

     

    In this example, we see the four interfaces of a Nuance PowerMicIII.

     

    <vmware-usbd> [vmware-remotemks] DevFltr: Interface [0] – Family(s): audio

    <vmware-usbd> [vmware-remotemks] DevFltr: Interface [1] – Family(s): audio,audio-in

    <vmware-usbd> [vmware-remotemks] DevFltr: Interface [2] – Family(s): audio,audio-out

    <vmware-usbd> [vmware-remotemks] DevFltr: Interface [3] – Family(s): hid

    In WNOS.ini (Or MAC.ini / SN.ini) add the following line to FORCE the USB redirection.  Note, the USB Redirection must be installed in the VDI desktop as part of the Horizon Agent.

    Device=vusb ForceRedirect=0x0554,0x1001,0x00,0x00,0x00 Type=PCoip

     

    FROM A THINOS device:  you see the following.

    ThinOS Device logs.  Insert a PowerMic II device…

    Event logs show the following.

    13:18:04 VUSB: Local Device 0x0451,0x2036,0x09,0x00,0x00)

    13:18:04 USB: Found a new 12Mbps device “HUB” on port 9

    13:18:04 VUSB: Redirectable Device(0x0554,0x1001,0x01,0x01,0x00)

    13:18:05 USB: Found a new 12Mbps device “USB AUDIO” on port 1

    13:18:05 USB: Found a new 12Mbps device “usbhid” on port 1

    13:18:05 AUDIO: Change record device to PowerMicII-NS

    13:18:05 AUDIO: Change playback device to PowerMicII-NS

    13:18:06 VUSB: Local Device(0xdf04,0x0004,0x03,0x01,0x02)

    13:18:06 USB: Found a new 12Mbps device “usbhid” on port 2

     

     

    #49496
    Axell
    Participant
    • Total Post: 9
    • Regular Joe
    • ★★

    Hello Twilley!

    Nice solution!

    But if we dont have Horizon Agent, is it possible to do the same with xendesktop 7.2+thin OS 8.0 (on dell wyse 5010)+VSphere VMs.

    I just have citrix studio and its options.

    #49497
    Axell
    Participant
    • Total Post: 9
    • Regular Joe
    • ★★

    Citrix studio has no option “Allow Auto Device Splitting”

Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.