UCS 4.3 Release Notes

Release notes for the installation and update of Univention Corporate Server (UCS) 4.3-5


Table of Contents

1. Release Highlights
2. Notes about the update
2.1. Recommended update order for environments with more than one UCS server
2.2. UCS installation DVD only available for 64 bit
3. Preparation of update
4. Postprocessing of the update
5. Notes on selected packages
5.1. Collection of usage statistics
5.2. Scope of security support for WebKit, Konqueror and QtWebKit
5.3. Recommended browsers for the access to Univention Management Console
6. Changelog
6.1. General
6.2. Basic system services
6.2.1. Boot Loader
6.3. Domain services
6.3.1. DNS server
6.4. Univention Management Console
6.4.1. Domain join module
6.5. System services
6.5.1. PAM / Local group cache
6.6. Virtualization
6.6.1. UCS Virtual Machine Manager (UVMM)
6.7. Services for Windows
6.7.1. Samba
6.7.2. Univention S4 Connector

§Chapter 1. Release Highlights

With Univention Corporate Server 4.3-5, the fifth point release of Univention Corporate Server (UCS) 4.3 is now available. It provides several feature improvements and extensions, new properties as well as various improvements and bugfixes. Here is an overview of the most important changes:

  • Samba was updated to version 4.10.

  • With 4.3-5 the update to Debian point release 9.11 is completed.

  • Various security updates have been integrated into UCS 4.3-5, e.g. Samba, the Linux kernel and Dovecot. A complete list of security and package updates is available in Chapter 6.

§Chapter 2. Notes about the update

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.

§2.1. Recommended update order for environments with more than one UCS server

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.

§2.2. UCS installation DVD only available for 64 bit

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.

§Chapter 3. Preparation of update

It must be checked whether sufficient disk space is available. A standard installation requires a minimum of 10 GB of disk space. The update requires approximately 4 GB additional disk space to download and install the packages, depending on the size of the existing installation.

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.

§Chapter 4. Postprocessing of the update

Following the update, new or updated join scripts need to be executed. This can be done in two ways: Either using the UMC module Domain join or by running the command univention-run-join-scripts as user root.

Subsequently the UCS system needs to be restarted.

§Chapter 5. Notes on selected packages

§5.1. Collection of usage statistics

Anonymous usage statistics on the use of Univention Management Console are collected when using the UCS Core Edition. The modules opened get logged to 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 License -> License information of the user menu in the upper right corner of Univention Management Console. If UCS Core Edition is listed under License type, 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.

§5.2. Scope of security support for WebKit, Konqueror and QtWebKit

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.

§5.3. Recommended browsers for the access to Univention Management Console

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 running older browsers may experience display or performance issues.

§Chapter 6. Changelog

Listed are the changes since UCS 4.3-4:

§6.1. General

§6.2. Basic system services

§6.2.1. Boot Loader

  • Re-add accidentally dropped patch to ignore files ending on .debian (Bug 49440).

§6.3. Domain services

§6.3.1. DNS server

  • Fix dependency header of legacy SysV init script to work in environments installed with UCS-4.2 or older and without Samba4 (Bug 49440).

§6.4. Univention Management Console

§6.4.1. Domain join module

  • Package rebuilt for new ldb library version 1.5.4 required by Samba 4.10 (Bug 49479).

§6.5. System services

§6.5.1. PAM / Local group cache

  • Disable PAM module systemd by default. It can be re-enabled by setting the Univention Configuration Registry variable pam/session/systemd to true (Bug 49910).

§6.6. Virtualization

§6.6.1. UCS Virtual Machine Manager (UVMM)

  • Re-connect VMs to bridges on network restart (Bug 49604).
  • Use interleaved memory policy on NUMA architectures by default (Bug 49548).

§6.7. Services for Windows

§6.7.1. Samba

  • Call samba_dnsupdate with --use-samba-tool instead of --local if Univention Configuration Registry variable samba4/join/dnsupdate is active (for UCS@school with Samba 4.10) (Bug 49482).
  • Run samba-tool dbcheck --reindex on update to Samba 4.10 (Bug 49479).
  • Re-add auth methods option removed from upstream Samba sources (Bug 47314).
  • Update to Samba 4.10.3. The dependent packages tevent, tdb, ldb were updated to new versions as well (Bug 49479).

§6.7.2. Univention S4 Connector

  • Use new LDAP control DSDB_CONTROL_REPLICATED_UPDATE_OID when changing objectSid's in UCS@school (Bug 49481).
  • The connector now properly handles the AD password change (Bug 49480).