Bug 445 - Client should remember several servers / profile manager
Summary: Client should remember several servers / profile manager
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Client (show other bugs)
Version: trunk
Hardware: PC Linux
: P2 Enhancement
Target Milestone: LowPrio
Assignee: Peter Åstrand
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-29 09:30 CET by Erik Forsberg
Modified: 2024-09-02 08:15 CEST (History)
3 users (show)

See Also:
Acceptance Criteria:


Attachments

Description Erik Forsberg cendio 2004-01-29 09:30:16 CET
For some cases, it would be convenient if the ThinLinc client remembered the
last n servers it has connected to. The servers could be presented in a dropdown
box similar to the one in Mozilla (for the URI field).

This would be convenient for example for support personel using ThinLinc to
connect to servers located at several different customers. This applies to both
Borås Sjukhus (which has requested the feature), and to ourselves.
Comment 1 Peter Åstrand cendio 2004-01-29 12:39:58 CET
We should consider generalizing this bug: Provide a profile manager that can
handle different settings for different servers as well. 

It could be implemented as a separate application, calling tlclient. 
Comment 3 Peter Åstrand cendio 2004-09-22 14:49:22 CEST
VMware has an interesting feature: The configuration files for the virtual
machines are executable, and begins with:

#!/usr/bin/vmware

This could perhaps be useful with tlclient as well: You could have several
different config files, and by executing these, you'll bring up the client with
the defined settings. 
Comment 4 Peter Åstrand cendio 2004-09-23 10:32:58 CEST
The solution with #!/usr/bin/vmware doesn't work, because /usr/bin/vmware is a
shell script. We will have the same problem with tlclient. 
Comment 5 Peter Åstrand cendio 2004-09-23 11:00:53 CEST
"#!/usr/bin/env vmware" works. 
Comment 6 Peter Åstrand cendio 2008-01-11 10:15:31 CET
Since we have implemented bug 2618, this functionality is basically available. We might want to consider some GUI manager tools, though. 
Comment 14 Samuel Mannehed cendio 2020-02-21 10:37:06 CET
See bug 5503 for simply having a list of recently used servers, without a connection to any other settings.
Comment 21 Pierre Ossman cendio 2024-09-02 08:15:34 CEST
Microsoft solved this by having a separate application for handling different connections:

https://learn.microsoft.com/en-us/sysinternals/downloads/rdcman

That could be an option that keeps things modular, and keeps the complexity away from standard users.

They tell people to avoid this and just use one of their standard clients, though:

https://learn.microsoft.com/en-us/troubleshoot/windows-client/remote/use-mstsc-universal-remote-desktop-client-instead-rdman

This might be wishful thinking, as I've not seen any connection manager in the standard mstsc. Their new "universal" client has an interface focused on multiple machines, though. At the cost of making the simple case more confusing.

Note You need to log in before you can comment on or make changes to this bug.