Table of Contents
With Univention Corporate Server 4.2-2, the second point release of Univention Corporate Server (UCS) 4.2 is now available. It provides several feature improvements and extensions, new properties as well as various improvements and bugfixes. An overview of the most important changes are:
The portal is now also easily usable in cloud setups. The services installed on UCS are directly accessible without further configuration steps. For this purpose, the portal converts existing links into relative links. For portal entries with multiple links, heuristic procedures are used to determine the best link.
The usability of the management system has been improved further. Users and groups can be copied, the error handling has been enhanced in various places and the performance has been increased.
Every app provider can now create simple app appliances through the App Provider Portal. App appliances bundle an app with UCS into a directly usable virtual machine. In addition, the integration depth of the apps can be significantly increased by so-called app settings. These can be created by the app provider simply via the provider portal without additional programming knowledge.
Various security updates have been integrated into UCS 4.2-2, e.g. OpenLDAP, the Linux kernel, Samba, MySQL and PostgreSQL.
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 1 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.2-1:
All security updates issued for UCS 4.2-1 are included:
runsv
service for the DHCP server is now always started, even when the initial check of the configuration file /etc/dhcp/dhcpd.conf
fails. This sometimes happens when BIND and OpenLDAP start too slowly during boot, in which case that is mis-detected as an error in that configuration file (Bug 45065).
/var/log/univention/ec2.log
have been fixed (Bug 44803).
[Errno24] Too many open files
errors (Bug 44965).
umc/module/timeout
was not evaluated anymore which caused that the connection to module processes was closed after 30 seconds bug (Bug 45307).
docker cp
to copy files into the container (Bug 44814).
:umlauts
modifier in the template mechanism of e.g. user templates now normalizes all characters (Bug 44370).
create
, modify
and remove
operation is allowed before executing the action (Bug 39253).
Span both columns
option for extended attributes is functioning again (Bug 40487).
udm --help
output has been cleaned up to improve readability (Bug 31768).
--position
argument has been added to the --help
output of the udm list
command (Bug 29501).
General
tab (Bug 33652).
udm remove --filter
is now displayed (Bug 37285).
ObjectFlag
syntax now allows the value synced
(Bug 37676).
--ignore_not_exists
(Bug 40737).
ComboBox
widgets (Bug 44847).
,
(Bug 42423).
users/self
and users/passwd
modules have been added for convenience (Bug 37623).
nagios
services has been improved (Bug 38362).
univention.uldap.access()
instances to UDM objects is handled more gracefully (Bug 41368).
container/dc
objects has been removed (Bug 24374).
settings/umc_operationset
(Bug 25187).
settings/umc_operationset
is now a required field (Bug 25189).
PostReadControl
(RFC 4527) (Bug 43628).
univention.admin.objects.get()
has been fixed which caused that the Univention Corporate Client UMC configuration was not possible anymore (Bug 45116).
sources.list
used for release updates is now removed if any of the pre-update scripts signals an abort condition (Bug 44821).
univention-saml
Apache site is now disabled upon package removal (Bug 41500).
univention-fix-ucr-dns
is installed in Docker containers too (Bug 45040).
security/packetfilter/docker/disabled
(Bug 44829).
sync_to_ucs
remember entryCSN of msGPO changes to be able to identify and skip them later in sync_from_ucs
(Bug 43628).
systemd-journald.service
for time limited log retention (Bug 44234).
bootsplash
to welcome screen is now flicker free.
Improved systemd integration for the welcome screen.
Crashes and graphic errors on VirtualBox and VMware have been fixed.
Always use framebuffer driver to ensure a working welcome screen (Bug 44061).
univention-fix-ucr-dns
when not default gateway is set (Bug 45120).