Introduction

1. Introduction#

Important

Most sections of this manual have been migrated to the Nubus for UCS 5.2 - Operation Manual [1]. For each moved section, you find a link to its new location in that document. If you don’t find the content you’re looking for here, check Nubus for UCS 5.2 - Operation Manual [1] directly.

The content of this section moved to Introduction in Nubus for UCS 5.2 - Operation Manual [1].

1.1. What is Univention Corporate Server?#

The content of this section moved to What is UCS? in Nubus for UCS 5.2 - Operation Manual [1].

1.2. What is Univention Nubus?#

The content of this section moved to Understanding Nubus and UCS in Nubus for UCS 5.2 - Operation Manual [1].

1.3. Overview of UCS#

The content of this section moved to Key concepts in Nubus for UCS 5.2 - Operation Manual [1].

1.3.1. Commissioning#

The content of this section moved to Key concepts in Nubus for UCS 5.2 - Operation Manual [1].

1.3.2. Domain concept#

The content of this section moved to Domain concept in Nubus for UCS 5.2 - Operation Manual [1].

1.3.3. Expandability with the Univention App Center#

The content of this section moved to Univention App Center in Nubus for UCS 5.2 - Operation Manual [1].

1.3.4. LDAP directory service#

The content of this section moved to LDAP directory service in Nubus for UCS 5.2 - Operation Manual [1].

1.3.5. Domain administration#

The content of this section moved to Management UI in Nubus for UCS 5.2 - Operation Manual [1].

1.3.6. Computer administration#

The content of this section moved to Key concepts in Nubus for UCS 5.2 - Operation Manual [1].

1.3.7. Policy concept#

The content of this section moved to Policy concept in Nubus for UCS 5.2 - Operation Manual [1].

1.3.8. Listener/notifier replication#

The content of this section moved to Listener/notifier replication in Nubus for UCS 5.2 - Operation Manual [1].

1.4. Further documentation#

This manual addresses just a small selection of the possibilities in UCS. Among other things, UCS and solutions based on UCS provide:

  • Comprehensive support for complex server environments and replication scenarios

  • Advanced capabilities for Windows environments

  • Central network management with DNS and DHCP

  • Monitoring systems and networks

  • Print server functionalities

  • Proxy server

Further documentation related to UCS and further issues is published under UCS documentation overview [2].

1.5. Symbols and conventions used in this manual#

The manual uses the following symbols:

Caution

Warnings are highlighted.

Note

Notes are also highlighted.

This table describes the functionality of a UMC module:

Table 1.1 Tab DHCP service#

Attribute

Description

Name

The unique name of a DHCP service.

Description

An arbitrary description of the service.

Menu entries, button labels, and similar details with actions are printed in this font face.

Names are highlighted.

Computer names, LDAP DNs, program names, file names, file paths, internet addresses and options are also optically accented.

Commands and other keyboard input is accented optically.

In addition, excerpts from configuration files, screen output, etc. are
printed as code block.

A backslash (\) at the end of a line signifies that the subsequent line feed is not to be understood as an end of line. This circumstance may occur, for example, where commands cannot be represented in one line in the manual, yet have to be entered in the command line in one piece without the backslash or with the backslash and a subsequent Enter.

The path to a function is represented in a similar way to a file path. Users ‣ Add means for example, you have to click Users in the main menu and Add in the submenu.

On this page