Table of Contents
With Univention Corporate Server 3.2-3, the third point release for Univention Corporate Server (UCS) is now available. It includes all errata updates issued for UCS 3.2-2.
The new module Active Directory Connection merges the domain administrated by UCS and an existing Active Directory. UCS is then available as a platform for the integrated operation of apps in an Active Directory domain.
The UCS setup wizard has been completely overhauled and now guides users particularly comfortably through the domain configuration of UCS and detects, for example, configuration settings automatically and suggests useful defaults.
PHP 5.4.4 has been back-ported to UCS 3.2. It can be installed from a separate repository and will receive security updates.
The OpenLDAP replication has been improved significantly by tracking changes in the directory service with unique IDs. The replication performance has been improved and replication errors have been reduced.
The Linux Kernel package has been updated to version 3.10.11. Besides many bug fixes, this improves the hardware support.
The Active Directory compatibility has been improved. UCS now supports the Microsoft Data Protection Application Program Interface (DPAPI).
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 console with the root user and then the update started there. Alternatively, the update can be initiated using the Univention Management Console.
Remote updating via SSH is not recommended as this may result in the update procedure being cancelled if the network connection is interrupted, for example, and this can affect the system.
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, for example, using the tools screen
and at
, which are installed on all system roles.
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 the user root.
Subsequently the UCS system should be restarted.
Pre-up and postup 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; 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 the 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 the 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 righthand corner of the Univention Management Console and selecting 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.
. If
Indendepent of the licence 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 the 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 currently.
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 currently support forest domains.
Samba 4 does not currently support trust relationships.
Further information can be found in Chapter 8 of the [ucs-handbuch].
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-2:
univention-add-app
no longer registers a link on the UCS startsite and
removes the component again if called with --master (just like the App
Center module)
(Bug 35022).
dojo.js
(Bug 34484).
/var/lib/samba/private
before new provision (relevant for
UCS@school Slave PDCs)
(Bug 32246).
/var/lib/samba/*
, only clear private subdir before re-join
(Bug 35000).
/usr/share/univention-s4-connector/remove_ucs_rejected.py
/usr/share/univention-s4-connector/remove_s4_rejected.py
smb.conf
share
sections. This will be used for the sysvol share to make rsync recognize
permission changes on directories
(Bug 34431).
univention-ad-takeover
has been removed since
the UMC module is more recent
(Bug 35514).
The following packages have been moved to the maintained repository
[ucs-handbuch] Univention GmbH. 2013. Univention Corporate Server - Manual for users and administrators. http://docs.univention.de/manual-3.2.html.