Bugzilla – Full Text Bug Listing
|Summary:||Browse .exe's from WTS when adding manually defined applications in TLDC|
|Product:||ThinLinc||Reporter:||Erik Forsberg <email@example.com>|
|Component:||TLDC (Desktop Customizer)||Assignee:||Karl Mikaelsson <firstname.lastname@example.org>|
|Status:||CLOSED WONTFIX||QA Contact:||Bugzilla mail exporter <email@example.com>|
It would be nice if it were possible to browse the available exe files on a windows terminal server from the TLDC GUI. For ideas on how to implement this, see bug 1360.
Continuing comment from 1360: >One problem is that the .exe files are not actually available on the ThinLinc >servers. (If they were, it would also be possible to *browse* to the correct >file, instead of having to type it in by hand. A big improvement.) So, how to >reach the .exe from ThinLinc? There are two usable protocols: > >1) CIFS. TLDC could call "smbclient". Or, we could create a link to >"konqueror", which supports CIFS. One problem: Which user should we >authenticate as? The simple solution is just to popup a username/password >dialog, and let the admin decide. CIFS *might* be disabled altogether, though. > Another problem: It's not very easy to get the local, absolute path from a >CIFS path. If the servers shares \\server\programs, and we find >\\server\programs\app\app.exe, how do we >know if this file is c:\program\app\app.exe or c:\program files\app\app.exe? Actually, it *is* possible to retrieve the local path from a CIFS path: You can translate a CIFS share name to a local path with a comment like this: rpcclient -c "netshareenum 2" The output is like: >netname: C$ > remark: Standardresurs > path: C:\ > password: rpcclient is from Samba 3. I think this would be ideal for us. We could create a web GUI for smblient which allows us to both browse .EXEs and download/browse icons.
Instead of just browsing for .EXEs, we might want to make it possible to browse for Shortcuts (.LNK files) as well. These usually works better, since some applications requires a certain current directory or certain strange command line arguments and/or switches.
I like this bug. We already have experience with calling tools from the Samba suite, and all functionality that we require is in Samba 3:s "smbclient" and "rpcclient". Writing a web frontend to smbclient should be very hard. From a commercial perspective, this bug is important if we want to enhance our support for integrating WTS applications on a Linux desktop.