Bloomberg keyboard stop working after thinos lock

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • March 11, 2020 at 5:36 pm #51953
    bakhat
    Participant
    • Total Post: 1
    • Newbie
    • ★

    Dear all, I am facing a issue related to bloomberg key board. During the vdi session when we lock the thinclient (thisos), Bloomberg keyboard stop working. But when we logoff from the citrix session keyboard start working.

    March 30, 2020 at 10:44 pm #52009
    smokingmango
    Participant
    • Total Post: 55
    • Back Stage Pass
    • ★★★★

    So the Bloomberg KB comes in 2 flavors. Duel USB or single usb, which one are you using? We are using the Duel usb, we have a policy on the Citrix side to allot USB passthough for those KBs using the vid and pid. Then on the INI we have the VID and PID listed in the INI and allow USB passthough on those keyboards as well. We have zero issues with them .

    April 2, 2020 at 10:09 pm #52031
    brian1020
    Participant
    • Total Post: 259
    • Jacked into The Matrix
    • ★★★★★★

    Are you USB force redirecting the PID VID? The below change will also allow for the finger print reader to work in Citrix through the thin client.

    On your Windows machine make this change

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\ICA Client\GenericUSB

    EnableBloombergHID changed from 0 to 1

    DeviceRules key added the following:
    ALLOW:vid=1188 pid=9525 # Bloomberg
    ALLOW:vid=1188 pid=9535 # Bloomberg
    ALLOW:vid=1188 pid=9545 # Bloomberg
    ALLOW:vid=1188 pid=03e9 # Bloomberg
    ALLOW:vid=1188 pid=03ef # Bloomberg

    On your thin client policy make this advanced line config change or make it an INI file:

    #Bloomberg keyboard force redirect
    Device=vusb ForceRedirect=0x1188,0x9525,0x03,0x01,0x01
    Device=vusb ForceRedirect=0x1188,0x9535,0x03,0x00,0x01
    Device=vusb ForceRedirect=0x1188,0x9545,0x03,0x00,0x01
    Device=vusb ForceRedirect=0x1188,0x03e9,0x03,0x00,0x01
    Device=vusb ForceRedirect=0x1188,0x03ef,0x03,0x00,0x01

    June 22, 2020 at 2:32 pm #52410
    Tellmers
    Participant
    • Total Post: 3
    • Newbie
    • ★

    Hi Brian

    we work on ThinOS, if i create this policies, keyboard stops working.

    Both USB cables are connected. any other sugguestions

    should this work only with one USB –> the PC

    June 29, 2020 at 6:11 pm #52454
    brian1020
    Participant
    • Total Post: 259
    • Jacked into The Matrix
    • ★★★★★★

    Did you have a working policy previously or you are trying to get one working?

    Did you check the VID/PID of your keyboard and make sure its listed, not sure if newer keyboard have come out or if a different regional/language layout would have a different VID/PID value as mine are English US and English UK.

    Do you have everything configured on the Citrix side to allow USB pass-through?

    June 29, 2020 at 6:21 pm #52455
    Tellmers
    Participant
    • Total Post: 3
    • Newbie
    • ★

    hey Brian

    thx for your replay in this cause!

    after contacting support and some other it friends, we have the solution. and it looks good.

    – both usb cabels needed to be connected
    – this needs to be setup in WMS Device=vusb ForceRedirect=0x1188,0x9535,0x03,0x00,0x01
    –> but needed to set “interface redirect” specify if interface redirect should be on or off

    – inside CTX policy allow VID=1188 and PID=9535

    no installation of additional keyboard driver and so on.
    and works with TS-Server 2019

     

    thx to all

    June 29, 2020 at 6:24 pm #52456
    brian1020
    Participant
    • Total Post: 259
    • Jacked into The Matrix
    • ★★★★★★

    Good news.

    Where is “but needed to set “interface redirect” specify if interface redirect should be on or off” found? Was that thin client side or Citrix policy side? I’m not familiar with it.

    would be great to have additional information.

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