- This topic is empty.
7. November 2012 at 21:47 #7578
Has anyone had any luck with using USB license dongles with Wyse thin clients? In particular the C10 and R10.
Our company uses some older software which uses the license key on a USB dongle. Even with USB redirection and mapping set in the wnos.ini files and also the MAC.ini files, the sessions do not see the licenses.
In the event viewer, the Wyse terminal picks up the USB device.
We have gotten many other USB devices to work, but these seem to be different. My guess is that it is because they use drivers, but those should be on the VM that the RDP session connects to?!
I opened a ticket with WYSE, but that usually takes quite a bit of time.
Any help is greatly appreciated.8. November 2012 at 9:15 #22974
– firmware version?
– backend you are connecting to?
CG13. November 2012 at 16:47 #22985
Thanks for the response.
Wnos.ini is below (we are still working some other issues out, which is why it may seem a little jumbled).
On a side note, I have been informed by Wyse that TCX is required for this to work. But if you have any other ideas…
RDP session connects to XP Pro SP3
Firmware on all clients is 7.1_130
AdminMode=yes Admin-Username=XXXXXXXXXXXXXX Admin-Password=XXXXXXXXXXXXXX
SysMode=classic toolbar_no_conmgr=yes DisableAddConnection=yes
SessionConfig=All MapDisks=yes UnmapUSB=no UnmapPrinters=no UnmapSerials=no
TimeZone=”GMT – 05:00″
TimeZoneName=”Eastern Standard Time”
DayLightName=”Eastern Daylight Time”
Include=$mac.ini15. November 2012 at 12:25 #22994
Wyse is correct. In a pure WinXp RDP environment you have to use TCX USB redirection.
CG19. November 2012 at 20:17 #23023
Just to let you know, we installed TCX server suite on the host, made a few configuration changes in the .ini files, and now the dongles are read from the client software. Thanks for the input.27. November 2012 at 8:04 #23038tarasovMember
- Total Post: 138
- Legend in Own LunchBox
1) Try ForceRedirect command in wnos.ini with VID,PID, etc of your USB dongle 2) Check VID, PID in Windows device manager – it could happen that they are different from the ones if device is plugged in locally. If VID, PID are different in redirected and ‘local’ connections you might have to change them in the INF files of dongle driver to match mapped values. p 1) helped me with Bloomberg keyboard finger print scanner , p 2) – with some other crazy scanner. Of course TCX rullezzz 🙂10. January 2013 at 0:29 #23276
I’m also attempting to get a Bloomberg keyboard with the finger scanner working with an RDP session.
So you are using the TCX suite, specifically USB redirector? Do you need to purchase licenses for the USB redirector?
Thanks!10. January 2013 at 8:43 #23277
Yes, TCX Suite has to be licensed.
CG7. February 2013 at 23:03 #23436
Thank you. We tested the eval and successfully tested it so purchased a license.
It’s partially working in that the RDP session is recognising the Bloomberg keyboard and all the key functions are working but the fingerprint scanner function is not being recognised.
I believe this is because there is a Bloomberg keyboard connected to the PC that the user is RDPing to and Bloomberg software is registering this fingerprint scanner.
When I RDP to a PC which does not have the bloomberg keyboard plugged into it the finger scanner works fine.
Is there a way to override or disable the PC local Bloomberg finger scanner or force the Wyse local Bloomberg finger scanner?
I don’t know if the ForceRedirect would achieve the desired result.
Thanks.8. February 2013 at 13:26 #23444
I do not understand you. When are you logging in from a PC? Same Server? Same session?
CG10. February 2013 at 23:37 #23456
So there is a PC running Bloomberg and the TCX suite. This PC has a Bloomberg finger scanner connected to it.
I have a Wyse C10LE with a Bloomberg finger scanner installed and is configured to RDP to the PC running Bloomberg.
When connecting to the PC via RDP using the Wyse, the Bloomberg finger scanner connected to the Wyse is not being picked up in the RDP session.
However, if I disconnect the Bloomberg finger scanner from the PC then the Bloomberg finger scanner works from the RDP session.
The user scenario is that they work in the office locally connected to the PC 3 days a week.
The other 2 days they work from another office and connect via RDP to the same PC.
I have tried to see if starting a new session via the Wyse works as oppossed to reconnecting to the session that was logged in locally but this made no difference.
Thanks.12. February 2013 at 14:32 #23466
A little bit to special for me. Sorry, no idea.
CG14. February 2013 at 0:13 #23479
No problems. I’ll post to Wyse support.
Thought maybe the ForceDirect or ForceLocal could exclude the finger scanner connected directly to server (PC) from being included in the RDP session.14. February 2013 at 16:01 #23483
There is no ForceLocal for RDP. Only ICA.
- You must be logged in to reply to this topic.