UCC 1.0 Quickstart

From Univention Wiki

Jump to: navigation, search
Sprachen: Flag de.gif DeutschFlag usa.gif English
Produktlogo UCC Version 1.0

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.

UCC is the successor to the UCS products UCS Thin Client Services and Univention Corporate Desktop.

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:

  • Access to Windows terminal services via RDP using a thin client
  • The management of Linux-desktop systems (here taking a notebook with a KDE desktop environment as an example). If you only wish to test one of these scenarios, one of the two steps can also be skipped.

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 GiBs for the home directory).

Detailed descriptions of UCC can be found on the website website and in the UCC manual.

Installing the UCS system

UCC requires Univention Corporate Server (UCS) 3.1 or 3.2. The installation of Univention Corporate Server is described in the Quickstart Guide for UCS.

UCC can be installed on all UCS server roles. In this example, the installation is performed on a single-server system. Therefore, Domaincontroller master should be selected as system role. Only the DHCP server needs to be selected in the software selection.

All available errata updates should be installed on the UCS system.

Available in AppCenter Button 200.png

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

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 Univention App Center needs to be opened.

UCS overview page
Login to UMC
UMC module App Center

In the Univention App Center, select the Univention Corporate Client application and click on Install. The UCC thin client image is downloaded automatically during the installation. The image size is approx. 300 MB, so the download may take some time. Following that, a new login to UMC needs to be done.

Selecting UCC in the App Center
Description of UCC
Installation of UCC

Creating users and computers in the UMC

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

One-time preparations

Define a network for the clients
In the UMC, a network object should be set up under Add in the Networks wizard in the UMC. A network object allows the simple administration and assignment of the IP addresses and network settings for systems. It would also be possible to perform manual assignment for the two clients created in this quickstart guide but for demonstration purposes it is done here via the network object.

For example, if the UCC clients use the IP addresses from 192.168.100.1 to 192.168.100.240, the following values must be entered:

  • Name: UCC Clients
  • Networks: 192.168.100.0
  • Netmask: 255.255.255.0
  • First Address: 192.168.100.1
  • Last Address: 192.168.100.240
The zones generated as standard during the installation and the DHCP service must be selected under DNS forward lookup zone, DNS reverse lookup zone and DHCP service. Here there is only one entry to choose from each time. By default the reverse lookup zone is created during the installatin of the master domain controller based on the IP address of the master domain controller. If the UCC clients are to be operated in a different IP range an additional reverse lookup zone needs to be created in the UMC and used as the reverse lookup zone.
Definition of the default gateway
Then the default gateway for the DHCP zone should be specified. This is done by clicking on the Service entry in the list in the DHCP module of the UMC and then selecting the subnet. Then click on DHCP routing in the [Policies] tab. Then click on Create new policy. You can enter any name as the Name, e.g., Routing default, and the default gateway for the network under Routers. Finally confirm with Create policy and exit the DHCP object by clicking Save changes. Additional information on creating policies can be found in the UCS manual.

Creating computer objects

Two Univention Corporate Client systems are now created in the UMC computer wizard:

  • Hostname: thinclient01 (or desktop01)
  • MAC address: The MAC addresses of the systems
  • Network: UCC Clients

It is important that the MAC address is entered first before the network is selected. This ensures that a DHCP entry for the computer is created automatically. If the network is selected first, the MAC address needs to be selected under DHCP in the dialogue below.

Configuring the thin client for the access to Windows terminal servers

Firstly a policy is created in which the Windows terminal server to be used for all the users of the UCS domain is configured. This is done by opening the UMC module LDAP directory, right clicking on users in the navigation tree on the left and then selecting Edit.

You can then select UCC user session on the Policies tab and click Create new policy. The following parameters must be configured here:

  • Name: UCC standard user settings
  • Windows domain: The domain name with which logins are performed on the Windows terminal server
  • Windows terminal server: The hostname of the Window terminal server

The computer thinclient01 must now be opened in the computer management of the UMC. The following parameters must then be configured on the Images tab:

  • Boot variant: Image boot with update check / initial installation
  • Image: ucc-1.0-thinclient-image.img
  • Repartitioning for installed systems Enable

The thin client is now started. A PXE start must be selected in the system's BIOS. The image is started via PXE and the thin client storage device 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 (see the UCS manual).

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.

Configuring the Linux desktop system

Whereas the thin client image is downloaded automatically in the scope of the UCC installation in the App Center, the desktop image must be installed separately. This is done by installing the ucc-desktop-image, which downloads the latest desktop image automatically.

The package can be installed using the tab Extended software management in the Univention App Center or on the commandline as the root user:

univention-install ucc-desktop-image

The image size is approx. 3 GiB, so the download may take some time. After the desktop image has been downloaded it must be extracted. There should be at least 20 GiB of free disk space available on the UCS system.

The computer desktop01 must now be opened in the computer management module of the UMC. The following must then be configured on the Images tab:

  • Boot variant: Image boot with update check / initial installation
  • Image: ucc-1.0-desktop-image.img
  • Repartitioning for installed systems: Enable

The client is now started. A PXE start must be selected in the system's BIOS. The image is started via PXE and the harddrive 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 (see the UCC manual).

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

Further information

General informations can be found in the UCC manual.

Help on Univention Corporate Client is offered in the Univention Forum.

Errors in the documentation or programs can be filed directly in the Univention Bugzilla.

Personal tools