Bug 7061 - difficult to discover .tlclient file association feature and what it should be used for
Summary: difficult to discover .tlclient file association feature and what it should b...
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Documentation (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: MediumPrio
Assignee: Samuel Mannehed
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-04 13:12 CEST by Pierre Ossman
Modified: 2024-02-16 12:50 CET (History)
2 users (show)

See Also:
Acceptance Criteria:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Pierre Ossman cendio 2017-10-04 13:12:31 CEST 
We've had many interactions with customers where we've noticed that they have not discovered the feature where the native client can load a separate configuration file. We've also not properly documented what use cases this feature can be used for.

We'd like to make this clearer and document that the primary use for this is to easily load a set of settings in the client.
Comment 2 Pierre Ossman cendio 2017-10-04 14:04:07 CEST 
There was some confusion as to what we meant with the purpose, so some clarification:

The current behaviour of settings both being loaded and saved back to the file is the one we want to describe. I.e. that the file represents a certain set of settings that will follow any changes you do in the UI, a "profile".

Note that the issue mentioned above wanted to avoid this saving so isn't a reference.
Comment 4 Linn cendio 2024-02-16 12:50:55 CET 
There is now a guide on the community on how to use tlclient-files (called user profile files in the guide):
https://community.thinlinc.com/t/how-to-conveniently-switch-between-different-user-profiles/863
Note You need to log in before you can comment on or make changes to this bug.