Thin Client vendor Igel Technology have added the Quest vWorkspace 6.2 linux client to their latest firmware release, the exact build is 4.01.500. The firmware will run on any hardware that supports the Universal Desktop image. Igel Technology also manufacture a range of terminals that ship with Microsoft Windows Embedded Standard, the vWorkspace Windows client is compatible with this platform.
For further information on the Quest Linux client please refer to the ‘Quest vWorkspace Linux Client Guide’ that is located in the downloads section of www.vworkspace.com. For further information on Igel Technology’s product range please refer to their website.
You can leave a response, or trackback from your own site.
October 2nd, 2009 at 4:16 pm
We already had SBC projects with thin clients from the German vendor IGEL Technology in conjunction with the Quest vWorkspace enterprise suite. So far we were using the clients with a customized Microsoft Windows Embedded Standard OS
The cool thing about the IGELs is that you can manage them centralized with the IGEL Universal Management Suite (UMS) for free. With this powerful management tool you can also push out the needed configuration for new thin client devices on the network incl. a customized MSI file that e.g. install the current vWorkspace windows client to the devices…
Up to now we had the series UD1 to UD5 and would recommend the use of UD3- or UD5 series because
1. UD1 series devices can’t be managed by the IGEL UMS.
2. UD2 series acts much slower within the RDP session than UD3 series devices as soon as it comes to Microsoft Windows Server 2008 with terminal services enabled.
Thanks to Quest and IGEL for shaking hands.
Holger Bui
Terminal-Services.NET
http://www.sbcpro.de
November 7th, 2009 at 8:28 am
The IGEL UD5 (Linux) flys with Vworkspace 6.2 and has many nice features in the management suite, on the downside, Igels support is polite and willing and but just not good enough. I was raving about the performance etc of the UD5, until I realized that the none the keys on the mid section (Cursor keys and Home, delete etc) of the extended keyboard, work at all with the QR client. IGEL and Quest informed and currently clueless)
The Thinspace TST600 is much smaller than the UD5, but just as fast, but USB does not work. The management software is not as good as IGEL. (Thinspace and Quest informed and currently clueless)
IGEL and Thinspace are the best thin clients that I have seen to date (HP, Wyse, Chip PC etc) but the lack of support and urgency from everyone including Quest is holding back a fantastic solution.
Chris Petrie
IT Director Stephenson Harwood
(End user of many excellent Quest products)
November 23rd, 2009 at 8:55 am
The issue mentioned above related to the way the keymap file had been converted and subsequently corrupted, therefore the extended keyboard wasn’t working correctly. The forthcoming Linux 6.2 client addresses the issue however it should also be possible to address the issue from a command line using the dos2unix command.
The command below should resolve the issue:
dos2unix /usr/local/share/qrdesktop/keymaps/* (of course I am making the assumption the Thin Client OS will allow you access to the command prompt as root)
December 29th, 2009 at 3:35 pm
Neither IGEL or Thinspace have fixed the issues mentioned in my earlier post.
In fact the IGEL keyboard issue has survived a firmware update.
We are now trying another manufacturer, who has both USB and Keyboard issues in the one Thin Client
Happy Days
Quest have contributed nothing at all of any value to this debate, it pains me greatly to say
January 22nd, 2010 at 10:33 am
I have been doing some testing in house and working with Igel. Their lead Linux developer has told that the next release of firmware will incorporate a fix that will allow different clients in the firmware to utilize different keymap files, however in the interim it is possible to configure the existing keymap so the kesy are enabled correct in a vWorkspace session. You will need to do the following:
1. Launch Igel Setup.
2. Click Sessions –> RDP -> RDP Global.
3. Click on Keybord and uncheck PC Keyboard Scan Codes.
4. Once this is saved the keyboard should work correctly in the session.
I have tested this in my lab using firmware 4.02.100.01 and had success.