Operation and Configuration of the UCS system in VMware or VirtualBox

From Univention Wiki

Jump to: navigation, search
Produktlogo UCS Version 3.0
Produktlogo UCS Version 3.1
Languages: Flag USA EnglishFlag Germany Deutsch

The article describes operation and first steps of the Univention Corporate Server (UCS) virtualization image. The image is provided in the OVF format, an open standard for virtual machines.

A sufficiently recent VMware Player (>= 5) is recommended. The image can also be used with virtualisation solutions like VirtualBox.

The VMware image (Download) includes a complete installed and pre-configured UCS system in the system role domain controller master. The system offers more possibilities than the online demo system. It is a complete UCS system with access restrictions to test functionality and application.

Virtualization with UCS Virtual Machine Manager (UVMM) can not be tested with a virtualized UCS system. The installation of UCS on hardware is required for virtualization.


Starting the VMware image

The UCS VMware image can be downloaded as zip archive from the download area. After extracting zip archive, the VMware image can be used in VMware Player (free download at http://www.vmware.com/download/player/).

After the installation of VMware Player, the UCS VMware image can be started on Linux with the following command:

$ vmplayer path to download/VMware­Image­Name.vmx

Upon start the boot menu appears. The default chosen entry Univention Corporate Server … will be started either with the return key or automatically after 5 seconds. After the first boot, UCS opens the wizard for the base settings.



The network access in the VMware image is set to "Bridged mode" in order to enable a network configuration for access to the test system from inside the local network. The wizard guides the user through the following steps of the initial configuration UCS as VMware image.

System role for configuration of the UCS system role for the system. If the system is the first UCS system in the environment, the setting can be left at Domain controller master.

More information about the system roles can be found in the UCS manual.

Click on Next.

Language settings for configuration of the available languages on the system. English and German are already selected in UTF-8 encoding. The settings can ususally be left as is.

Click on Next.

Language settings
Basic settings for configuration of fully qualified domain name (FQDN), LDAP base, Windows domain and Root password. Fully qualified domain name and root passwort have to be set here. LDAP base and Windows domain are automatically suggested according to the FQDN and can be customized.

Click on Next.

Basic settings
Network settings for configuration of IPv4 and if necessary IPv6 addresses and the gateway. The system is configured to get its IP address via DHCP. This setting can usually be left as is. The first entry in the list for the nameservers should be the local IP address of the UCS system, because UCS comes with an own name services.

If no DHCP server provides an IP address, the system will use a link local address. The network settings can be changed later in the module Base settings in the UCS management system.

Click on Next.

Network settings
Certificate settings for configuration of the SSL certificate. The settings may be left as is.

Click on Next.

Software settings for installation of additional software components. The settings can be left as is.

Depending on the test purpose additional software components may be chosen that will be installed after finishing the configuration. The component Mail server has been chosen as additional component in this example.

Click on Next.

Software settings
All necessary settings are made after the software settings and can be applied to the test system by clicking on Apply changes.
Apply changes
Finishing the configuration takes a moment. Hostname, LDAP base, Domain and network settings are configured, if necessary additional software will be installed and the system will join the domain.
Configuration progress
After all the system will be continue the boot process.
Continue Boot process

First steps in the UCS system

The system can be accessed with the already present accounts "root" and "Administrator" after the reboot. Both user accounts use the Root password that has been set during the base settings.

SSH Login

A SSH server is installed on the UCS system. The user "root" can login via SSH. With the SSH login the user has direct access to the system (e.g. univention-config-registry or view log files in /var/log/…).

UCS management system

The UCS management system can be accessed with a web browser through the configured IP address during the initial configuration. The URL is https://<IP address>. For example, if the suggested IP address has been set, the URL would be

All settings in the scope of the domain can be configured in the domain management of the UCS management, e.g. management of users, groups, computers, configuration of services etc. The user account "Administrator" can be used for administration tasks. In principle, all users in the group "Domain Admins" are allowed to make changes in the domain management.

Graphical login

KDE is installed as desktop on the UCS system. It allows users to have a graphical login to the system. The user "root" is not allowed to login to the desktop by default. To test the graphical environment without adding a new user, the user "Administrator" may be used.

Add further systems to the UCS environment

Windows client computers

Univention Corporate Server provides functionality known from Microsoft Windows server systeme to Windows client computers. The UCS systems includes an Active Directory compatible domain controller that allows the management of users, printers and shares that can be accessed from Microsoft Windows client computers. This requires the Microsoft Windows clients to be member of the domain. If the UCS system can be reached over the network from a Microsoft Windows client computer, the Windows client may join the domain just as if it joins a Windows domain.

This is documented in the UCS manual.

UCS systems

If additional UCS systems (servers or desktops) should be operated in the environment, they have to be instantiated seperately. It is possible to operate the UCS system repeatedly in different system roles. Detailed information about the installation can be found in the UCS Quickstart Guide and in the [docs.univention.de/manual-3.1.html UCS manual].


Univention Corporate Server differs from other Linux distributions among other things by its sophisticated management system. The UCS management system is well-rooted into several areas of the system. That is the reason why UCS includes concepts and mechanisms like domain management or Univention Configuration Registry for the administration of several UCS systems that are not know from other distributions. Univention Corporate Server - Manual for users and administrators is the available documentation for UCS.

Announcements and discussion about Univention Corporate Server can be found in the Univention Forum. Feedback is welcome in the Forum.

Further information to start with Univention Corporate Server can found at the following entry points:

Personal tools