Table of Contents
With Univention Corporate Server 4.1-2, the second point release of Univention Corporate Server (UCS) 4.1 is now available. It provides various improvements and bugfixes. An overview of the most important changes:
Several important security updates have been integrated in UCS 4.1-2, among others for Samba, Apache, OpenSSL and the GNU C Library (glibc).
The update to Samba 4.3.7 includes various security updates. In addition, several issues have been fixed, for example, failed login attempts are now counted correctly.
The Active Directory Connector now uses Active Directory standard interfaces for synchronizing the password hashes. Thus, the Windows password synchronization service is no longer needed.
The presentation of the apps in the Univention App Center has been improved, among others the App license terms are now displayed.
During the update some services in the domain may not be available temporarily, that is why the update should occur in a maintenance window. It is recommended to test the update in a separate test environment prior to the actual update. The test environment should be identical to the production environment. Depending on the system performance, network connection and the installed software the update will take between 20 minutes and several hours.
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 to all the remaining LDAP servers of the UCS domain. As changes to the LDAP schema can occur during release updates, the master domain controller must always be the first system to be updated during a release update.
Starting with UCS 4.0, installation DVD are only provided for the x86 64 bit architecture (amd64). Existing 32 bit UCS 3 systems can still be updated to UCS 4.0 through the online repository or by using update DVD. The 32 bit architecture will be supported over the entire UCS 4 maintenance period.
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 about another 2 GB of disk space for download and installation all 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 canceled, 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 in case of disconnection from the network.
This can be achieved, e.g., using the tools screen
and at
. These tools are installed on all UCS 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.
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 by 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 37
Firefox as of version 38
Internet Explorer as of version 11
Safari and Safari Mobile as of version 9
Users with older browsers may experience display or performance issues.
Listed are the changes since UCS 4.1-1:
All security updates issued for UCS 4.1-1 are included:
mount -o remount,no_mbcache "$fs"
or by adding the option
no_mbcache in /etc/fstab
and rebooting the system (Bug 41054).
/etc/univention/service.info/services
are now only considered if they carry the filename suffix .cfg
.
The behavior is now similar to the treatment of UCR info files.
(Bug 40383).
grub/default
, as it doesn't work on systems using a different language (Bug 41046).
grub-mkdevicemap
as it is not needed (Bug 40586).
grub/terminal
and grub/serialcommand
. Thanks to Lutz Willek for the patch (Bug 40596).
umc/logout/location
(Bug 40613).
univention-register-apps
now uses the new App Center API and has been deprecated (Bug 40754).
univention-app
shell now correctly exits with the exit code of the called command (Bug 40550).
univention-app
installed unsigned packages. This issue has been fixed (Bug 40861).
univention-run-join-scripts
instead of being called directly
(Bug 40984).
umc/module/udm/users/self/disabled
to false
(Bug 39016).
preup.sh
and postup.sh
scripts have been updated to match UCS-4.1-2 (Bug 41157).
dists/**/Packages*
files created for local repositories did contain multiple entries for the
same package. This breaks the Debian installer and other tools like debootstrap
, which use a simpler implementation than
APT. A filter has been added to filter out old versions and duplicate entries (Bug 40932).
kerberos/autostart
did not clearly explain
that this variable needs to remain set to no on Samba4/AD DCs (Bug 40383).
nssldap/timelimit
and defaults to 30 seconds. This prevents hanging UMC server processes when changing
network and IP settings in certain circumstances (Bug 40968).
samba-tool domain
passwordsettings
, the badPwdCount increased in steps of two for each failed login attempt
at a Windows client (Bug 40328).
/
. This issue
has been fixed (Bug 40847).
smb.conf
option ldap server require strong auth to
allow_sasl_over_tls. Additionally it configures tls verify peer to
ca_and_name. The raised security requirements of Samba server components may require configuration
adjustments for older clients. Univention Corporate Client (UCC) 1.0 running a Linux kernel version prior to 3.8 for
example require an adjustment of the mount.cifs options. In that case the value for mount option
sec needs to be adjusted to ntlmsspi, e.g. by setting ucr set
ucc/mount/cifshome/options="serverino,sec=ntlmsspi"
. UCC 2.x clients (i.e. Linux kernel above 3.8) don't
require this adjustment (Bug 40988).
smb.conf
options configurable via Univention Configuration Registry:
samba/ntlm/auth
, samba/server/signing
samba/tls/verify/peer
samba/tls/priority
samba/tls/dh/params/file
and
samba/ldap/server/require/strong/auth
(Bug 41034).
connector/ad/mapping/user/alternativemail
and
connector/ad/mapping/group/alternativemail
(Bug 40357).