Upgrading LAM or migrate from LAM to LAM Pro
Prev | Chapter 2. Installation | Next

## Upgrading LAM or migrate from LAM to LAM Pro

Upgrading from LAM to LAM Pro is like installing a new LAM version. Simply install the LAM Pro packages/tar.bz2 instead of the LAM ones.

### Upgrade LAM

Backup configuration files

Configuration files need only to be backed up for .tar.bz2 installations. DEB/RPM installations do not require this step.

LAM stores all configuration files in the "config" folder. Please backup the following files and copy them after the new version is installed.

config/*.conf
config/config.cfg
config/pdf/*.xml
config/profiles/*

LAM Pro only:

config/selfService/*.*

Uninstall current LAM (Pro) version

If you used the RPM installation packages then remove the ldap-account-manager and ldap-account-manager-lamdaemon packages by calling "rpm -e ldap-account-manager ldap-account-manager-lamdaemon".

Debian/Ubuntu needs no removal of old packages.

For tar.bz2 please remove the folder where you installed LAM via configure or by copying the files.

Install new LAM (Pro) version

Please install the new LAM (Pro) release. Skip the part about setting up LAM configuration files.

Restore configuration files

RPM:

Please check if there are any files ending with ".rpmsave" in /var/lib/ldap-account-manager/config. In this case you need to manually remove the .rpmsave extension by overwriting the package file. E.g. rename default.user.rpmsave to default.user.

DEB:

Nothing needs to be restored.

tar.bz2:

Please restore your configuration files from the backup. Copy all files from the backup folder to the config folder in your LAM Pro installation. Do not simply replace the folder because the new LAM (Pro) release might include additional files in this folder. Overwrite any existing files with your backup files.

Final steps

Now open your webbrowser and point it to the LAM login page. All your settings should be migrated.

Please check also the version specific instructions. They might include additional actions.

### Version specific upgrade instructions

You need to follow all steps from your current version to the new version. Unless explicitly noticed there is no need to install an intermediate release.

#### 9.4 -> 9.5

Users who have an active session in LAM need to relogin to LAM.

#### 9.3 -> 9.4

New configuration format for main configuration and server profiles is enforced. Please save your main configuration and all server profiles with LAM 9.0 - 9.3 before upgrading. You can also export your configuration and import all server profiles and main configuration. This format change does not apply if you use MySQL for configuration storage.

#### 9.2 -> 9.3

No actions required.

#### 9.1 -> 9.2

LAM Pro:

- Custom scripts: The settings in server profile were split by account type. If you use custom scripts then you need to perform these steps for each server profile that uses them (no scripts will be executed till migration was done):

  - Open server profile and switch to tab "Module settings"

  - Review the automated migration of the custom scripts settings (complex configurations will need manual adaptions)

  - Save the server profile

#### 9.0 -> 9.1

No actions required.

#### 8.9 -> 9.0

Main configuration and server profiles: Both use a new file format (JSON). The configuration will be converted to the new JSON format if you save your settings. The old format is still supported when the configuration will be read. As the old format will be supported for a limited time, it is recommended to open LAM and save the main configuration and all server profiles after the upgrade. If you have any external processes to modify/generate these configurations please adapt them.

LAM Pro:

- Cron jobs of server profiles no longer use the job token parameter

- cron.sh and cronGlobal.sh are deprecated and will be removed in the next release. Use the new command "runCronJobs.sh". E.g. "runCronJobs.sh all" will run all global jobs and all server profile jobs. Execute "runCronJobs.sh" to get a list of possible options.

#### 8.8 -> 8.9

No actions required.

#### 8.7 -> 8.8

LAM Pro:

- Request access: please run the new global cron job to remove requests that are too old. The time limit can be configured in LAM's main configuration.

#### 8.6 -> 8.7

LAM Pro:

- Self-service profiles that were not saved with a LAM Pro version of the past 3 years must be saved with LAM Pro 8.6 before upgrading to LAM Pro 8.7.

- Self-service profiles that have enabled "HTTP authentication" need to be reconfigured. Open the self-service profile, select "HTTP authentication" as "Authentication method" (first tab, server settings) and save the self-service profile.

#### 8.1 -> 8.6

No actions required.

#### 8.0 -> 8.1

Configuration settings in server profiles must be redone for group of unique names and group of members.

#### 7.6 -> 8.0

No actions required.

#### 7.5 -> 7.6

The tree view was rewritten from scratch. It moved to the tools menu. You need to reconfigure the tree suffix in your LAM server profile (tools section on first tab).

#### 7.2 -> 7.5

No actions required.

#### 7.1 -> 7.2

LAM Pro: All emails need a specified FROM address. This affects password email, self registration, password self reset and cron emails.

#### 6.7 -> 7.1

No actions required.

#### 6.6 -> 6.7

Self-service: please verify the self-service base URL in your self-service profiles in case you have password self reset / user self registration enabled.

#### 6.5 -> 6.6

No actions required.

#### 6.4 -> 6.5

No actions required.

#### 6.3 -> 6.4

No actions needed.

#### 6.2 -> 6.3

Unix: Options in server profile for Unix users and groups need to be reconfigured. Several settings (e.g. id generation) are now specific to subaccount type.

Self-service: If you use a captcha for user self registration this needs to be reconfigured. On tab General settings please activate Google reCAPTCHA (the checkbox to secure login is optional). On tab Module settings please tick the captcha checkbox at self registration settings.

#### 6.1 -> 6.2

No actions required.

#### 6.0 -> 6.1

DEB+RPM configuration for nginx uses PHP 7 by default. Please see /etc/ldap-account-manager/nginx.conf if you use PHP 5.

#### 5.7 -> 6.0

No actions needed.

#### 5.6 -> 5.7

Windows: The department attribute was changed from "departmentNumber" to "department" to match Windows user manager. The attribute "departmentNumber" is no more supported by the Windows module. You will need to reactivate the department option in your server profile on module settings tab.

#### 5.5 -> 5.6

Mail routing: No longer added by default. Use profile editor to activate by default for new users/groups.

Personal/Unix/Windows: no more replacement of e.g. $user/$group on user upload

#### 5.4 -> 5.5

LAM Pro requires a license key. You can find it in your customer profile.

#### 5.1 -> 5.4

No special actions needed.

#### 5.0 -> 5.1

Self-service: There were large changes to provide a responsive design that works for desktop and mobile. If you use custom CSS to style Self-service then this must be updated.

#### 4.9 -> 5.0

Samba 3: If you used logon hours then you need to set the correct time zone on tab "General settings" in server profile.

#### 4.5 -> 4.9

No special actions needed.

#### 4.4 -> 4.5

LAM will no longer follow referrals by default. This is ok for most installations. If you use LDAP referrals please activate referral following for your server profile (tab General settings -> Server settings -> Advanced options).

The self-service pages now have an own option for allowed IPs. If your LAM installation uses IP restrictions please update the LAM main configuration.

Password self reset (LAM Pro) allows to set a backup email address. You need to update the LDAP schema if you want to use this feature.

#### 4.3 -> 4.4

Apache configuration: LAM supports Apache 2.2 and 2.4. This requires that your Apache server has enabled the "version" module. For Debian/Ubuntu and Fedora this is the default setup. The Suse RPM will try to enable the version module during installation.

Kolab: User accounts get the object class "mailrecipient" by default. You can change this behaviour in the module settings section of your LAM server profile.

Windows: sAMAccountName is no longer set by default. Enable it in server profile if needed. The possible domains for the user name can also be set in server profile.

#### 4.2.1 -> 4.3

LAM is no more shipped as tar.gz package but as tar.bz2 which allows smaller file sizes.

#### 4.1 -> 4.2/4.2.1

Zarafa users: The default attribute for mail aliases is now "dn". If you use "uid" and did not change the server profile for a long time please check your LAM server profile for this setting and save it.

#### 4.0 -> 4.1

Unix: The list of valid login shells is no longer configured in "config/shells" but in the server/self-service profiles (Unix settings). LAM will use the following shells by default: /bin/bash, /bin/csh, /bin/dash, /bin/false, /bin/ksh, /bin/sh.

Please update your server/self-service profile if you would like to change the list of valid login shells.

#### 3.9 -> 4.0

The account profiles and PDF structures are now separated by server profile. This means that if you edit e.g. an account profile in server profile A then this change will not affect the account profiles in server profile B.

LAM will automatically migrate your existing files as soon as the login page is loaded.

Special install instructions:

- Debian: none, config files will be migrated when opening LAM's login page

- Suse/Fedora RPM:

  - Run "rpm -e ldap-account-manager ldap-account-manager-lamdaemon"

  - You may get warnings like "warning: /var/lib/ldap-account-manager/config/profiles/default.user saved as /var/lib/ldap-account-manager/config/profiles/default.user.rpmsave"

  - Please rename all files "*.rpmsave" and remove the file extension ".rpmsave". E.g. "default.user.rpmsave" needs to be renamed to "default.user".

  - Install the LAM packages with "rpm -i". E.g. "rpm -i ldap-account-manager-4.0-0.suse.1.noarch.rpm".

  - Open LAM's login page in your browser to complete the migration

- tar.gz: standard upgrade steps, config files will be migrated when opening LAM's login page

#### 3.7 -> 3.9

No changes.

#### 3.6 -> 3.7

Asterisk extensions: The extension entries are now grouped by extension name and account context. LAM will automatically assign priorities and set same owners for all entries.

#### 3.5.0 -> 3.6

Debian users: LAM 3.6 requires to install FPDF 1.7. You can download the package here. If you use Debian Stable (Squeeze) please use the package from Testing (Wheezy).

#### 3.4.0 -> 3.5.0

LAM Pro: The global config/passwordMailTemplate.txt is no longer supported. You can setup the mail settings now for each LAM server profile which provides more flexibility.

Suse/Fedora RPM installations: LAM is now installed to /usr/share/ldap-account-manager and /var/lib/ldap-account-manager.

Please note that configuration files are not migrated automatically. Please move the files from /srv/www/htdocs/lam/config (Suse) or /var/www/html/lam/config (Fedora) to /var/lib/ldap-account-manager/config.

#### 3.3.0 -> 3.4.0

No changes.

#### 3.2.0 -> 3.3.0

If you use custom images for the PDF export then these images need to be 5 times bigger than before (e.g. 250x250px instead of 50x50px). This allows to use images with higher resolution.

#### 3.1.0 -> 3.2.0

No changes.

#### 3.0.0 -> 3.1.0

LAM supported to set a list of valid workstations on the "Personal" page. This required to change the LDAP schema. Since 3.1.0 this is replaced by the new "Hosts" module for users.

Lamdaemon: The sudo entry needs to be changed to ".../lamdaemon.pl *".

#### 2.3.0 -> 3.0.0

No changes.

#### 2.2.0 -> 2.3.0

LAM Pro: There is now a separate account type for group of (unique) names. Please edit your server profiles to activate the new account type.

#### 1.1.0 -> 2.2.0

No changes.

Prev | Up | Next
Chapter 2. Installation | Home | Uninstallation of LAM (Pro)