Upgrading an old installation of ThinLinc is very much like installing it from scratch. The only difference is that you will have to decide how to migrate the configuration. The package manager decides how to deal with configuration files during upgrade in most cases, but when configuration files have changed between the previous and the new ThinLinc release, and have also been changed on the system, you need to decide how to proceed by selecting one of the options presented by tl-setup:
Use the new Hiveconf files, but copy over the parameters and values from the old files. Use old non-Hiveconf configuration files.
With this option, all configuration changes done in the earlier version are preserved. The Hiveconf configuration will be based on the new files. Comments will not be migrated. The file structure and file names may also be different. All parameters and values from the listed Hiveconf files are copied over. This means that unchanged parameters in these files will use the default values from the earlier release.
Note that a certain parameter will be defined if it is defined either in the new or old Hiveconf files. This means that if you have removed some parameters, for example one of the example profiles, those parameters will again exist after the migration. For profiles, however, this will not affect the user session, since profiles are only visible if they are also listed in the "order" parameter.
Parameters will be removed from the new Hiveconf files if they are defined elsewhere. For example, if /vsmagent/agent_hostname has been moved from vsmagent.hconf to local.hconf, this change will be preserved.
Use all old configuration files.
With this option, all the old files are used. Custom comments and the file structure are preserved, but no new parameters or comments from the new release are introduced. Please note that configuration files which are identical in the old and new release are not listed or processed. This means that new default values in such files are introduced even with this option.
Ignore old configuration and use the new files.
With this option, the listed configuration files are ignored and the new files are used instead. Please note that configuration files which are identical in the old and new release are not listed or processed. This means that configuration changes to such files are preserved even with this option.
Before performing an upgrade, find out if you need new license files to run the new version. ThinLinc license files delivered with version x.y.z will still work for versions with the same x and y but higher z, but not for increased x or y. For example, license files for ThinLinc 3.1.0 will still work for ThinLinc 3.1.1, but not for ThinLinc 3.2.0 or ThinLinc 4.0.0.
As the new licenses will work with the old (current) version, it's a good idea to install them as the first step in the upgrade process.
The same installation program that you used to install ThinLinc is also used to upgrade it. It is located in the root directory of the Server Bundle. Extract the bundle and start the installation program as follows:
and answer the questions. If you prefer, you can also upgrade the ThinLinc packages by hand. These packages are located in subdirectory packages on the Server Bundle.
After upgrading the software packages, ThinLinc must be configured. This is done by the program /opt/thinlinc/sbin/tl-setup. If you are running install-server, it will ask you if you want to start tl-setup at the end of the package upgrade.