We currently use %TMP%. As per the TAG: > Observe that some directories in the Windows %TMP% path may be flagged as hidden by the Windows system. This means that you need to change directory options to display hidden files and directories to navigate to the log file. We should consider changing where we put the client log file on Windows. Perhaps a better option might be %LOCALAPPDATA%. We might even consider creating a shortcut to it, in the same way we do for tlwebadm on the sever. This would help with support.
The objective here (al
The main objective here (along with related bug #8329) is to simplify the process of requesting client debug output from users, usually in the context of providing support. Meaningful client log output should be straightforward to generate and retrieve, including by non-technical end users who may not be familiar with concepts like system directories, environment variables, or command-line flags. A secondary consideration for this bug is whether the Windows temporary directory is the most appropriate location for storing log files. Logs files should be persistent, at least insofar as persistence is defined by the software writing them (in ThinLinc's case, the two most recent invocations of the client). There is no guarantee that files placed in %TMP% will remain there for any period of time.
We have not experienced any customers having difficulties finding these. It is expected that ThinLinc support will have to provide a small step-by-step guide for this. Let's reopen if we see more interest.
