Table of Contents
The sixth point release for Univention Corporate Server (UCS) is now available in the form of Univention Corporate Server 3.2-6. The online repository provided by Univention can be used to update existing UCS systems or, alternatively, updates can be installed from an update DVD. There are also UCS 3.2-6 ISO images available for new installations. UCS 3.2-6 includes all the errata updates published for UCS 3.2-5. An overview of the most important changes:
The release contains several security updates which have been released in the previous weeks and months as errata updates for UCS 3.2-5. Among others, it contains updated packages for the Linux kernel, OpenSSL, glibc, sudo.
Various tools using the PAM stack now support the configuration of multiple LDAP servers. Such a configuration can be used to improve the reliability of authentication services.
The login performance in large environments has been improved: Time consuming queries for quota settings have been separated from the login process.
Provided that UCS receives a network configuration via DHCP
, additional parameters like routing information are now also evaluated.
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.
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.
Pre-up and post-up scripts are scripts which are run before and after release updates (e.g., for post-processing the update, for example by uninstalling obsolete packages). As of UCS 3.2, these scripts are cryptographically signed to prevent unauthorized modification. During the update and when mirroring the repository these signatures are checked. If they're invalid or missing, the action is aborted.
If a repository server is operated with UCS 3.1-x, it should be updated to UCS 3.2 before additional systems can be updated to UCS 3.2-1 or newer.
If it is not possible to update the repository server, the signature files must be downloaded manually:
LOCAL_DIR="/var/lib/univention-repository/mirror" SERVER="http://updates.software-univention.de" for release in 3.2-0 3.2-1 3.2-2 3.2-3 3.2-4 3.2-5 3.2-6; do for script in preup postup; do file="3.2/maintained/$release/all/$script.sh.gpg" wget -O "$LOCAL_DIR/$file" "$SERVER/$file" done done
Alternatively, it is also possible to disable the signature checks, which can be a security risk.
For the repository server this can be done by setting the Univention Configuration Registry variable repository/mirror/verify
to false
.
For the update the Univention Configuration Registry variable repository/online/verify
must be set to false
on all systems.
Anonymous usage statistics on the use of Univention Management Console are collected when using the free for personal use version of UCS (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 free-for-personal-use license is used. The license status can be verified by clicking on the cog symbol in the top right corner of the Univention Management Console and selecting . If Free for personal use edition 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
.
In addition to the standard installation DVD there is also a medium with support for the Unified Extensible Firmware Interface standard (UEFI) available for the amd64 architecture.
It must be used instead of the standard DVD on systems which only support a UEFI boot.
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.
Some Active Directory functions are currently not available in Samba 4:
Microsoft Windows domain controllers must not be joined in a Samba 4 domain and vice versa.
Selective replication is not possible with Samba 4 as this is not supported by Active Directory in principle (in UCS@school selective replication is implemented through the listener/notifier replication mechanism).
Samba 4 does not support forest domains.
Samba 4 does not support trust relationships.
Further information can be found in Chapter 8 of the [ucs-manual].
During the installation of UCS in the virtualization solution VirtualBox, a VirtualBox bug may appear which has been corrected in version 4.2: if UCS has been successfully installed and the DVD is still in the disk drive, the installation DVD offers the option
. If you select this option, VirtualBox freezes.For Linux distributions which still use VirtualBox 4.0 or 4.1, either the installation DVD should be removed from the drive settings of the VirtualBox VM or F12 pressed when starting the virtual instance and the hard drive selected as a boot partition as a workaround before starting the UCS VM. UCS will then start successfully.
When UCS is installed in the virtualization solution Citrix XenServer 6.0 - 6.2, the GRUB menu of the Univention installer is not shown with the Cirrus graphics card emulated as standard. The Univention Installer can be started directly by pressing the ENTER key; alternatively, the installation starts automatically after sixty seconds. The Univention Installer which then starts is displayed as normal.
To display GRUB correctly, the graphics card emulated by XenServer can be reconfigured.
This is done by logging on to the XenServer system as the root
user.
Firstly, the xe vm-list
command is used to determine the UUID of the virtual machine.
The following command is then used to reconfigure the emulated graphics card to VGA:
xe vm-param-set uuid=UUIDVM platform:vga=std
There are two basic procedures for migrating Samba 3 to Samba 4:
Setup of a parallel Samba 4 domain. Both domains use different NetBIOS names and SIDs. The clients then join the Samba 4 step by step.
Migration of all systems within one maintenance window.
Both procedures are documented in detail in the Univention Wiki: http://wiki.univention.de/index.php?title=Migration_from_Samba_3_to_Samba_4.
If the Xen hypervisor is used and the memory limit for the dom0
has been configured using the Univention Configuration Registry-Variable grub/xenhopt
, the value should be updated to include the ,max: part as well.
See the http://wiki.univention.de/index.php?title=UVMM_Quickstart-3.1/en#Configuring_the_Dom0 for details.
Listed are the changes since UCS 3.2-5:
All security updates issued for UCS 3.2-5 are included:
univention-user-quota
(Bug 38078).
univention-group-quota
(Bug 38079).
msgpo.schema
adjusted in UCS 3.2-5 erratum 276 would get replaced by a not-adjusted version during an update to UCS 4.0.
This erratum avoids this by implementing a dpkg
diversion for that file, which will get removed again in an erratum for UCS 4.0-2 (Bug 38488).
Additional arguments for smtpd
processes may now be added via Univention Configuration Registry variables.
The given arguments are automatically added to the configuration file /etc/postfix/master.cf
.
The following UCR variable prefixes are currently supported:
mail/postfix/mastercf/options/smtp/...
mail/postfix/mastercf/options/smtps/...
main.cf
framework have been done for defining a custom restriction rule set via Univention Configuration Registry variables for Postfix' smtps
port (465).
There is currently no change in Postfix behaviour (Bug 31738).
[ucs-manual] Univention GmbH. 2014. Univention Corporate Server - Manual for users and administrators. http://docs.univention.de/manual-3.2.html.