When did it all begin?
The Univention Portal is the central hub via which users access a Univention system. It is where you can find links to installed applications like webmail. In addition, administrators also have the option of including their own links to external websites. Last, but by no means least, there is also a module here with which users can change their own password.
Univention supports personalization of the portal’s start page – in the best-case scenario, this not only ensures compliance with your corporate identity, but also allows users to identify better with Univention. For example, it is possible to place a number of different applications on the start page, permitting users direct access to them. Yet another option is even more evident immediately: In just a few steps, the portal can be customized with a large-scale background image and a portal logo. Domain administrators can perform this step quickly and with minimal effort.
With version 17.1, EGroupware has been extended from the classic groupware with an integrated CRM system to include a file server with Collabora Online Office. The complete package can be easily installed via the Univention App Center. In addition, the browser-based EGroupware does not require an Office suite to be installed on the client.
With UCS 4.2-3, the third point release for Univention Corporate Server (UCS) 4.2 is now available. It includes a number of improvements and security updates.
Among the highlights of 4.2-3 are several new functional tests that allow administrators to diagnose their IT infrastructure. Thanks to these, you can now check upon the health of the server and the entire domain.
We here at bitpack.io accompanied the project from start to finish and would like to present it to you today.
The Open Source/Linux Tech platform OSTechNix publishes another article on Univention Corporate Server (UCS). This time, they provide a detailed tutorial about the installation and configuration process of UCS.
The LDAP server in UCS, like the Active Directory on a Windows server, stores all the information on your domain about all your resources from hardware to employee as objects, namely in a structured and well-defined manner. Every object has some defined attributes of a particular type. Common attributes of a user object are, for example, the user’s surname, password and further valuable information on him. Part of the LDAP is the LDAP schema, which provides the administrator with a clear overview on all objects by describing which types of attributes exist within the LDAP and what attributes they have.
So, if you want to include additional attributes or create entirely new object types, extending the schema might be the way to go.