i hope somebody is been able to help me.
I try to use the "vWorkspaceConnector for linux" in combination with the vWorkspace Webportal.
We use the preinstalled connector on a igel thin-client.
I can open firefox and login to the web-portal. Whenever i try to start an application or desktop i can only download the *.pit file.
On Windows i still have to link the *.pit-files to the pntsc.exe. I try the same on the tc, but nothing happened. I also try to link the files with the "qrdesktop" and will get an error-message "Could not get session number".
Has somebody a solution for this "little" problem?
nice to meet you in here. I assume that like always you are using the current or even a beta image of the IGEL Linux OS for your testing device.
A few minutes ago i viewed the current feature support guide and i have to admit that i am not sure about the Web-IT support in detail. Do you mind to try to launch your published applications with the JAVA client instead of the factory installed vWorkspace Connector. I would be interested in if this go through without any issues. Even if the seamless mode isn't supported and you have to be satisfied with the published application within a window at the moment the JAVA client normally works just fine.
Further on we will try what happens with our UD5 with the current IGEL Linux OS image installed if we try the same within our testlab. I will follow up on you right after.
I am not sure if iGel is using the latest Linux Connector in their images but you should be able to make an association to /usr/local/bin/launcher for PIT files and it should work just fine.
IGEL is using the latest Linux Connector with their current image 4.04.100 of their IGEL Universal Desktop LX / IGEL Linux OS. The image was relased on August the 20th. And as far as i know Malko is using this image with his device.
my Igel is running at the latest FW 4.04.500.01 (released two weeks ago) with the Linux Connector 7.0.
But there is no path to /usr/local/bin/launcher. There is a dead end at /usr/local
I called the igel-support and asked about the path to the Linux Connector.
The path is: /services/vws/bin/ and there is a launcher file and much more (see attachment). But nothing happened when i linked the *.pit to the launcher-file.
Malko, i am not aware about if you already did, but we updated your support case at IGEL with this information. We have the same issue with our UD5 here.
I am investigating this and will have an update for you all as soon as I figure out what is going on with the iGel and our launcher binary.