Univention Corporate Client

Quickstart Guide for Univention Corporate Client


Table of Contents

1. Introduction
2. Requirements
3. Installing the UCS system
4. Configuring thin client access to Windows terminal servers
4.1. Introduction
4.2. Adding a thin client
5. Configuring Linux desktop systems
5.1. Introduction
5.2. Adding a desktop
Bibliography

§Chapter 1. Introduction

Univention Corporate Client (UCC) is a flexible and very economic alternative for the operation and administration of PCs, notebooks and thin clients in companies and institutions. The software contains a Linux-based desktop environment optimised for business use. In addition, UCC serves as a platform for access to remote desktop solutions and virtualized desktops as well as browser or terminal server-based applications.

The administration is performed using the standard tools of the UCS management system from Univention Corporate Server and integrates seamlessly in the administration of existing domain resources.

This quickstart guide offers an introduction to Univention Corporate Client. Two application scenarios for UCC are presented:

  • The management of Linux desktop systems (here taking a notebook with a KDE desktop environment as an example).
  • Access to Windows Remote Desktop Services via the RDP protocol using a thin client

If you only wish to test one of these scenarios, one of the two steps can also be skipped.

UCC also offers the possibility of providing a KDE Linux desktop terminal server remotely via the RDP protocol. It is then possible to access it from thin clients, for example. This is documented in the UCC manual [ucc-manual].

Help on Univention Corporate Client is offered in the Univention Forum: http://forum.univention.de/.

§Chapter 2.  Requirements

The following systems are required for the quickstart guide:

  • A UCS system in which UCC is managed (a UCC environment can also be distributed on several systems, this example uses a single-server installation). The UCC images will be stored on the UCS system, so there should be sufficient disk space available. At least 2 GiB of free space are needed for the thin client image and at least 20 GiB for the desktop image.

To test the access to a Windows terminal server from a thin client:

  • A Windows terminal server for the thin client to access.
  • A thin client. The thin client must have 2 GiB CompactFlash memory.

To test the operation of a Linux desktop:

  • A system on which the Linux desktop is installed. The system should be equipped with at least 20 GiB of disk space (the operating system installation requires 15 GiB plus additional GiB for the home directory).

Detailed descriptions of UCC can be found on the website [1] and in the UCC manual [ucc-manual].

§Chapter 3. Installing the UCS system

UCC requires Univention Corporate Server (UCS) 4.0. The installation of Univention Corporate Server is described in the quickstart guide for UCS [ucs-quickstart].

UCC can be installed on all UCS server roles. In this example, the installation is performed on a single-server system. Therefore, Domaincontroller master has to be selected as system role. No additional component needs to be selected in the software selection. All available errata updates should be installed on the UCS system.

Following successful installation, a login is performed on the Univention Management Console (reachable under https://server_ip/) as user Administrator.

§

Figure 3.1. Login at the UMC

Login at the UMC

During the first login at the Univention Management Console a dialogue is displayed which allows the activation of the UCS license for the Univention App Center. For this an e-mail address needs to be provided to which the activated license key is sent.

The license key can be imported in the UMC by clicking on the gear-wheel symbol in the upper menu bar. The menu entry Import new license needs to be selected.

Now the UMC module App Center needs to be opened.

In the Univention App Center, select the Univention Corporate Client 2.0 application and click on Install. Following that, a new login to UMC needs to be done.

Now a user must be created in the user management of the UMC. It is sufficient to perform the minimum required settings.

§Chapter 4. Configuring thin client access to Windows terminal servers

§4.1. Introduction

The UCC setup UMC module must be run. In the first menu item you can select whether desktops and/or thin clients are to be set up. Select Thin client configuration and click Next.

The UCC systems are installed via images, i.e., the complete operating system is replaced during installations and updates (user data are stored separately). This makes it possible to run an installation in just a few minutes. Univention provides preconfigured images which are continuously maintained.

The thin client image must now be downloaded from the Univention server. As it is approximately 300 MB in size, the download may take some time. To do so, enable the Download the UCC thin client image option and click on Next. Once the download is complete, the image is unpacked.

UCS uses so-called network objects to manage IP addresses and DNS/DHCP settings for client systems. Network objects define IP address ranges and provide the next free IP address when a new computer is created.

The following dialogue can be used either to define a new network or to use the network object installed during the installation of the master domain controller.

In the following step, the wizard checks whether a standard gateway is configured in the DHCP. If this is not the case, a dialogue appears in which this can be defined.

The next prompt asks which remote desktop services should be accessed. Select RDP services (Windows Remote Desktop Services, XRDP) and click Next.

In addition to the RDP access described here, access to Citrix Terminal Services or a website can also be configured. This is documented in the UCC manual: [ucc-manual-citrix], [ucc-manual-firefox].

The server to be connected to is entered under Host name of RDP server. If this is a Windows server, the Domain name must also be configured.

After clicking on Next, the configured settings are then shown once again. Clicking Apply configuration applies them. The UCC image is then downloaded and unpacked and different Univention Configuration Registry policies are preconfigured.

§4.2. Adding a thin client

Now open the computer module in the UMC and click Add. Select computers/ucc-thinclients as the Container (this container is linked to policies which are configured in the UCC wizard) and Host: Univention Corporate Client as the Type. Then click on Next.

You can select any Host name. The network configured in the UCC setup wizard is used as the Network and an IP address suggested based on this (however, it is also possible to use a different one). In addition, the MAC address also needs to be configured. Then click on Next.

Select Installation with repartitioning and image rollout as the Boot variant and the downloaded thin client image (ucc-2.0-thinclient-image.img) as the Image. Then click Create computer.

The client has to be started now. A PXE start must be selected in the system's BIOS. The image is started via PXE and the hard-drive partitioned and installed following confirmation. The domain join to the UCS domain is performed in the scope of the installation. The join is performed with the Administrator account.

The domain join can also be performed completely automated [ucc-manual-automaticrollout].

The session RDP must now be selected in the LightDM login manager. A login can now be performed with the user created in the UMC. A connection to the Windows terminal server is created automatically and it is possible to work on the terminal server.

§Chapter 5. Configuring Linux desktop systems

§5.1. Introduction

The UCC setup UMC module must be opened. In the first menu item you can select whether desktops and/or thin clients are to be set up. Select Linux desktop systems configuration / XRDP terminal server setup and click Next.

The UCC systems are installed via images, i.e., the complete operating system is replaced during installations and updates (user data are saved separately). This makes it possible to perform an installation in just a few minutes. Univention provides preconfigured images which are continuously maintained.

The desktop image must now be downloaded from the Univention server. As it is approximately 1 GB in size, the download may take some time. To do so, enable the Download the UCC desktop image option and click on Next. Once the download is complete, the desktop image is unpacked. The UCS system should have at least 20 GiB of free disk space.

UCS uses so-called network objects to manage IP addresses and DNS/DHCP settings for client systems. Network objects define IP address ranges and provide the next free IP address when a new computer is added.

The following dialogue can be used either to define a new network or to use the network object installed during the installation of the master domain controller.

In the following step, the wizard checks whether a standard gateway is configured in the DHCP. If this is not the case, a dialogue appears in which this can be defined.

The configured settings are then shown once again. Clicking Apply configuration applies them. The UCC image is then downloaded and unpacked and different Univention Configuration Registry policies are preconfigured.

§5.2. Adding a desktop

Now open the computers module of the UMC and click Add. Select computers/ucc-desktops as the Container (this container is linked to policies which are configured in the UCC wizard) and Host: Univention Corporate Client as the Type. Then click on Next.

You can select any Host name. The network configured in the UCC setup wizard is used as the Network and an IP address suggested based on this (however, it is also possible to use a different one). In addition, the MAC address also needs to be configured. Then click on Next.

Select Installation with repartitioning and image rollout as the Boot variant and the downloaded desktop image (ucc-2.0-desktop-image.img) as the Image. Then click Create computer.

The client has to be started now. A PXE start must be selected in the system's BIOS. The image is started via PXE and the hard-drive partitioned and installed following confirmation. The domain join to the UCS domain is performed in the scope of the installation. The join is performed with the Administrator account.

In a productive UCC installation, the domain join can be performed completely automated [ucc-manual-automaticrollout].

The session UCC must now be selected in the LightDM login manager. The login can now be performed with the user created in the UMC. The user can then work with a KDE Plasma desktop.

§Bibliography

§

[ucc-manual] Univention GmbH. 2014. Univention Corporate Client - Manual for administrators. http://docs.univention.de/ucc-manual-2.0.html.

§

[ucs-quickstart] Univention GmbH. 2014. Quickstart Guide for Univention Corporate Server. http://docs.univention.de/quickstart-en-4.0.

§

[ucc-manual-citrix] Univention GmbH. 2014. UCC manual - Citrix XenApp terminal services. http://docs.univention.de/ucc-manual.html#terminalservices:citrix.

§

[ucc-manual-firefox] Univention GmbH. 2014. UCC manual - Firefox session script. http://docs.univention.de/ucc-manual-2.0.html#logins:firefox.

§

[ucc-manual-automaticrollout] Univention GmbH. 2014. UCC manual - Configuration of a fully automated rollout. http://docs.univention.de/ucc-manual-2.0.html#rollout:automatic.