Table of Contents
The first point release for Univention Corporate Server (UCS) 3.3 is now available in the form of Univention Corporate Server 3.3-1. The online repository provided by Univention can be used to update existing UCS systems or, alternatively, updates can be installed from an update DVD. UCS 3.3-1 includes all the errata updates published for UCS 3.3-0. The maintenance cycle for the UCS 3 major version ends on 31 December 2016. Further information can be found in the Univention Forum.
In environments with more than one UCS system, the update order of the UCS systems must be borne in mind:
The authoritative version of the LDAP directory service is maintained on the master domain controller and replicated on all the remaining LDAP servers of the UCS domain. As changes to the LDAP schemes can occur during release updates, the master domain controller must always be the first system to be updated during a release update.
It is generally advisable to update all UCS systems in one maintenance window whenever possible.
It must be checked whether sufficient disk space is available. A standard installation requires a minimum of 6 GB of disk space. Depending on the scope of the existing installation, the update will require at least another 1 GB of disk space for the downloading and installation of the packages.
For the update, a login should be performed on the system's local console as user root
, and the update should be initiated there.
Alternatively, the update can be conducted using Univention Management Console.
Remote updating via SSH is not recommended as this may result in the update procedure being cancelled, e.g., if the network connection is interrupted.
In consequence, this can affect the system severely.
If updating should occur over a network connection nevertheless, it must be verified that the update continues despite disconnection from the network.
This can be done, e.g., using the tools screen
and at
. These tools are installed on all system roles by default.
PostgreSQL 9.1 is delivered with UCS 3.3. Security Updates for PostgreSQL 8.4 won't be provided with UCS 3.3. The migration from PostgreSQL 8.4 to PostgreSQL 9.1 should be done after the migration to UCS 3.3. See SDB 1292 for more details.
Following the update, new or updated join scripts need to be executed.
This can be done in two ways:
Either using the UMC module univention-run-join-scripts
as user root
.
Subsequently the UCS system needs to be restarted.
Anonymous usage statistics on the use of Univention Management Console are collected when using the UCS Core Edition (which is generally used for evaluating UCS). The modules opened are logged in an instance of the web traffic analysis tool Piwik. This makes it possible for Univention to tailor the development of Univention Management Console better to customer needs and carry out usability improvements.
This logging is only performed when the UCS Core Edition license is used. The license status can be verified via the menu entry of the user menu in the upper right corner of Univention Management Console. If is listed under , this version is in use. When a regular UCS license is used, no usage statistics are collected.
Independent of the license used, the statistics generation can be deactivated by setting the Univention Configuration Registry variable umc/web/piwik
to false.
WebKit, Konqueror and QtWebKit are shipped in the maintained branch of the UCS repository, but not covered with security support. WebKit is primarily used for displaying HTML help pages etc. Firefox should be used as web browser.
Univention Management Console uses numerous JavaScript and CSS functions to display the web interface. Cookies need to be permitted in the browser. The following browsers are recommended:
Chrome as of version 14
Firefox as of version 10
Internet Explorer as of version 9
Safari (on the iPad 2)
Users with older browsers may experience display or performance problems.
Listed are the changes since UCS 3.3-0:
All security updates issued for UCS 3.3-0 are included:
/etc/fstab
and rebooting the system (Bug 42984).
/boot/grub
and the
GRUB directly on the disk. This makes the system unbootable.
This update checks all devices in grub-pc/install_devices, removing invalid devices. A guess is
made for the correct boot device which will be added to grub-pc/install_devices if
grub-pc/install_devices is currently empty or there were invalid devices. If any changes were made,
grub-install is run on all devices in grub-pc/install_devices. See also SDB 1356
(Bug 41497).