Installation Notes

Update Instructions

To install this update please follow the following steps:

Procedure

1. It is highly recommended to backup of all server data with the Collax backup system before proceeding. Check that the backup was successful before proceeding with the update (this can be done within the backup information email).
2. In the administration interface go to System → System Operation → Software → System Update and press Get Package List. This will download the listed update packages. If successful the message Done! will be displayed on the screen.
3. Click Get Packages to download the update packages.
4. Click Install. This installs the update. The end of this process is indicated by the message Done!.
5. A new kernel will now be installed. The system will reboot automatically after installing the update. An appropriate note will be shown if the update process is completed.

New in this Version

Zarafa Groupware: New Version 7.1.4

With this Collax software update the new version 7.1.4 of Zarafa Groupware is going to be installed. This version includes mainly improvements, also for clients running on Windows 8 and Outlook 2010. Please find details here:

https://doc.zarafa.com

Zarafa Groupware: Single Sign On in Active Directory

With this update the feature Single Sign on for the Zarafa server is being enabled automatically as soon as the server is member within an Active Directory. Zarafa Outlook clients use the login credentials given for the domain login, the user only need to log in on the workstation.

Zarafa Groupware: Central Email Disclaimer

A diclaimer for all emails sent by Zarafa users can be defined from this update on. The content of the disclaimer can be defined as ASCII text or as HTML code. The disclaimer is then attached to all outgoing emails that are sent via Zarafa users.

Backup/Restore: Set Identifier for Backup System Manually

Usually the identifier for backups is generated automatically by the backup system and contains the host name of the system. To improve the disctinction of multiple backup systems the identifier can be set manually from this update on.

Issues Fixed in this Version

Zarafa Groupware: Zarafa Bricklevel Restore shows index without special characters

The index shown in Zarafa Restore problem is missing special characters. This is going to be fixed within this software update.

Zarafa Groupware: Maximum Size of Attachements within Zarafa WebApp

From this update on the maximum size of attachments being sent via the Zarafa WebApp is set to the value Maximum message size within the dialog Settings → Mail and Messaging → SMTP reception. If the default value has not been changed attachments with the size up to 100MB can be sent via Zarafa WebApp.

Zarafa Groupware: Booking Zarafa Resources

Sometimes it was not possible to book a Zarafa Resource correctly for a meeting. This is going to be fixed witin this software update.

Zarafa Groupware: Added Public Folder Not Visible

Public Folders for the Zarafa Groupware can also be defined within the graphical interface of the Collax server administration. Sometimes such Public Folders were not visibal to Zarafa users. This is going to be fixed with this update.

Authentication: New Local User gets Existing UID Number

If the user database was reset from remote to local new local users could get the same user ID like existing users. This ist going to be fixed with this software update.

Security: Scripting Language PHP5 and PHP Libraries

In the source code of PHP5 security holes have been discovered. These holes will be closed within this software update to PHP 5.3.23.

Backup/Restore: Missing Backup Log if Restoring Stream Data (LDAP)

Until now, the exit value of the restore was ignored when restoring stream data (e.g. LDAP), and failing restores were only detected if the error occured during the restore itself (i.e., write error) instead of during stream close. With this update restores can make the restore terminate in an error state by exiting with a non-zero value. This will be logged appropriate.

Backup/Restore: Status of Removed Media from Virtaul Tape Library

When the backup service checks for media currently present in changer magazines, it failed to mark all volumes as not present in changer if the list of currently available cartridges was empty (i.e., magazines not present, or all VTL media detached). With this update backup jobs are continued only if appropriate media is connected.