Personal tools
You are here: Home Support and Documentation Administrator's Guide 3.5.  Upgrading an Old Installation
Document Actions

3.5.  Upgrading an Old Installation

3.5.  Upgrading an Old Installation

Upgrading an old installation of ThinLinc is very much like installing it from scratch. The only difference is that you will have to adapt the old settings in /opt/thinlinc/etc/conf.d/ to the new configuration files afterwards.

3.5.1.  Acquire New Licenses

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 1.4.0 will still work for ThinLinc 1.4.1, but not for ThinLinc 1.5.0 or ThinLinc 2.0.

Contact your reseller for new licenses. If you bought ThinLinc with a maintenance agreement, new licenses will be provided without cost.

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.

3.5.2.  Run the Installation Program

The same installation program that you used to install ThinLinc is also used to upgrade it. It is located in the directory that is appropriate for your server architecture, i.e. serverkit-linux or serverkit-solaris on the server-CD. Start the installation program as follows:

$ sh ./install-server

and answer the questions. If you prefer, you can also upgrade the ThinLinc packages by hand.

3.5.3.  Update Configuration Files

When upgrading RPM-based Linux systems or systems running Solaris, the package installation process handles configuration files that have been changed by taking backups of existing configuration . The installation program will detect that the configuration files need attention and prompt the user to adjust them before running tl-setup. See below for instructions on how to handle the configuration files on different types of systems.

3.5.3.1.  RPM-based Linux systems

Look for files with filenames ending in .rpmsave, .rpmorig in /opt/thinlinc/etc and below. These are copies of the files as they were before the upgrade. Review the differences between the old and the new files, and add relevant statements from the old files to the new files, then remove or move away the .rpmsave and/or .rpmorig files.

3.5.3.2.  DPKG-based Linux systems

Upgrade of the configuration files are handled via interactive prompts during package installations. Follow the instructions given on the screen.

3.5.3.3.  Solaris

All configuration files that were present in the old version you're upgrading from will be saved as <filename>.pkgsave. Transfer relevant statements from these files to the new configuration files installed by pkgadd.

3.5.4.  Run tl-setup

After installation of the packages and modification of the configuration files as described above, run /opt/thinlinc/sbin/tl-setup to verify that the system is correctly configured. If no configuration files were changed by the installation program, tl-setup will be started automatically.