Difference between revisions of "Operation and Configuration of the UCS system in VMware or VirtualBox"

From Univention Wiki

Jump to: navigation, search
(VMware Player Version hochgesetzt.)
 
(39 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Version|UCS=3.0-1}}
+
{{Version|UCS=4.0}}
{{Language|de=Inbetriebnahme und Konfiguration des VMware Demosystems}}
+
{{Language|de=Inbetriebnahme und Konfiguration des Demosystems in VMware oder VirtualBox}}
  
The article describes operation and first steps in the demo system of Univention Corporate Server (UCS) in VMware. A sufficient latest VMware Player (>= 4.0.2) is recommended.
+
The article describes operation and first steps of the Univention Corporate Server (UCS) virtualization image. The image is provided in the zip format for VMware and in the OVA format for VirtualBox.
  
The VMware image ([http://www.univention.de/download/vorinstallierte-vmware-images/ Download]) includes a complete installed and pre-configured UCS system in the system role domain controller master. The system offers more possibilities than the [http://www.univention.de/en/download/online-demo/ online demo system]. It is a complete UCS system with access restrictions to test functionality and application.
+
A sufficiently recent VMware Player (>= 5) or VirtualBox (>= 4.1.12) is recommended.
 +
 
 +
To start the image, a BIOS option for hardware virtualization has to be activated. Depending on the CPU Vendor, the option is called VT-x or AMD-V.
 +
 
 +
The image ([https://www.univention.com/downloads/ucs-download/preinstalled-vm-images/ Download]) includes a completely installed and pre-configured UCS system, which can be configured for different system roles. The system offers more possibilities than the [http://www.univention.com/downloads/ucs-online-demo/ online demo system]. It is a complete UCS system without 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.
 
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.
  
 
= Operation =
 
= Operation =
 +
 +
== Starting the VirtualBox image ==
 +
 +
The UCS VirtualBox image can be downloaded in the OVA format from our [https://www.univention.com/downloads/ucs-download/preinstalled-vm-images/ download area].
 +
 +
The image can now be imported. Start VirtualBox and select the downloaded image after clicking on ''File'' → ''Import Appliance''. When the import is finished the appliance can be started by clicking on the ''Start'' button.
  
 
== Starting the VMware image ==
 
== Starting the VMware image ==
  
The UCS VMware image can be downloaded as zip archive from the [http://www.univention.de/en/download/preinstalled-vmware-images/ download area]. After extracting zip archive, the VMware image can be used in VMware Player (free download at http://www.vmware.com/download/player/).
+
The UCS VMware image can be downloaded as zip archive from the [https://www.univention.com/downloads/ucs-download/preinstalled-vm-images/ 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:
 
After the installation of VMware Player, the UCS VMware image can be started on Linux with the following command:
Line 18: Line 28:
 
<code>$ vmplayer path to download/VMware­Image­Name.vmx</code>
 
<code>$ vmplayer path to download/VMware­Image­Name.vmx</code>
  
[[Datei:vmware-demo-bootloader.png|500px]]
+
== System boot ==
  
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 using [[UCS Appliance|UCS Appliance mode]].
+
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.
  
[[Datei:vmware-demo-ucs-initial-configuration.png|500px]]
+
[[File:vmware-demo-ucs-initial-configuration.png|500px]]
  
 
== Settings ==
 
== 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.
+
The network access in the image is set to "''Bridged mode''" in order to enable a network configuration for access to the test system from the local network. The UCS appliance wizard guides the user through the following steps of the initial configuration.
  
 
{| cellpadding="8" border="1" style="border: 1px solid rgb(0, 0, 0); border-collapse: collapse; background-color: #ffffff;" class="wikitable"
 
{| cellpadding="8" border="1" style="border: 1px solid rgb(0, 0, 0); border-collapse: collapse; background-color: #ffffff;" class="wikitable"
 
|-
 
|-
| style="vertical-align: middle" | '''System role''' for configuration of the UCS system role for the system. The first thing to define is the system role of the newly created UCS system. A domain controller master is the first system to be defined for a new environment. More information about the system roles can be found in the {{Manual UCS 3.0|UCS Manual}} in section 3.3 ''System roles''.  
+
| style="vertical-align: middle" | '''Domain and network configuration''' defines the network configuration for the system. You can leave the setting at "obtain IP address automatically (DHCP)".
| [[File:vmware-demo-system-role.png|thumb|400px|Systemrolle]]
+
 
 +
 
 +
Click on '''Next'''.
 +
 
 +
| [[File:vmware-demo-networksettings.png|thumb|400px|Domänen und Netzwerkkonfiguration]]
 +
|-
 +
| style="vertical-align: middle" | '''Domain setup''' for configuration of the UCS system role in the environment. If the system is the first UCS system in the environment, the setting has to be left at ''Create a new UCS domain''.
 +
 
 +
More information about the domain setup can be found in the [http://docs.univention.de/manual-4.0.html#systemrollen UCS manual].
 +
 
 +
Click on '''Next'''.
 +
| [[File:vmware-demo-system-role.png|thumb|400px|Domain setup]]
 
|-
 
|-
| style="vertical-align: middle" | '''Language settings''' for configuration of the available languages on the system. English and German are already chosen in UTF-8 encoding.
+
| style="vertical-align: middle" | '''Administator account information''' for configuration of the ''Administrator'' account on the system. The password for the administrator account has to be provided here.
|[[Datei:vmware-demo-language-settings_en.png|thumb|400px|Language settings]]
+
 
 +
 
 +
Click on '''Next'''.
 +
|[[File:Administator-account-information-en.png|thumb|400px|Administrator account information]]
 
|--
 
|--
| style="vertical-align: middle" | '''Basic settings''' for configuration of fully qualified domain name (FQDN), LDAP base, Windows domain and Root password.LDAP base and Windows domain are automatically suggested according to the FQDN and can be customized. The Root password has to be filled in.  
+
| style="vertical-align: middle" | '''Host settings''' for configuration of fully qualified domain name (FQDN) and LDAP base. The fully qualified domain name is automatically suggested from the administrator account setting and can be customized.
| [[Datei:vmware-demo-basic-settings.png|thumb|400px|Basic settings]]
+
 
 +
 
 +
Click on '''Next'''.
 +
| [[File:Domain-and-host-configuration-en.png|thumb|400px|Basic settings]]
 
|--
 
|--
| style="vertical-align: middle" | '''Network settings''' for configuration of IPv4 and if necessary IPv6 addresses and the gateway. The system is configured to get it's IP address via DHCP. If no DHCP server provides an IP address, the system will use a link local address. The first entry in the list for the nameservers should be the local IP address of the UCS demo system, because UCS comes with an own name services. The network settings can be changed later in the modul ''Base settings'' in the UCS management system.
+
| style="vertical-align: middle" | '''Software configuration''' for installation of additional software components. The settings can be left as is.  
| [[Datei:vmware-demo-network-settings.png|thumb|400px|Network settings]]
+
 
 +
 
 +
Depending on the test purpose additional software components may be chosen that will be installed after finishing the configuration. For example, the component ''Mail server''.
 +
 
 +
 
 +
Click on '''Next'''.
 +
| [[File:vmware-demo-software-settings.png|thumb|400px|Software configuration]]
 
|--
 
|--
| style="vertical-align: middle" | '''Certificate settings''' for configuration of the SSL certificate. The settings may be left as is.
+
| style="vertical-align: middle" | All necessary settings are made after the software settings and can be applied to the test system by clicking on '''Configure system'''.
| [[Datei:vmware-demo-certificate-settings.png|thumb|400px|Certificate settings]]
+
| [[File:vmware-demo-confirmation.png|thumb|400px|Configure system]]
|--
 
| style="vertical-align: middle" | '''Software settings''' for installation of additional software components. 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.
 
| [[Datei:vmware-demo-software-settings.png|thumb|400px|Software settings]]
 
|--
 
| style="vertical-align: middle" | All necessary settings are made after the software settings and can be applied to the test system by clicking on ''Apply changes''.
 
| [[Datei:vmware-demo-confirmation.png|thumb|400px|Apply changes]]
 
 
|--
 
|--
 
| style="vertical-align: middle" | 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.
 
| style="vertical-align: middle" | 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.
| [[Datei:vmware-demo-init.png|thumb|400px|Configuration progress]]
+
| [[File:vmware-demo-init.png|thumb|400px|Configuration progress]]
 
|--
 
|--
| style="vertical-align: middle" | After all the system will be continue the boot process.
+
| style="vertical-align: middle" | Afterwards the system setup is finished and the system is ready for operation.
| [[Datei:vmware-demo-restart.png|thumb|400px|Continue Boot process]]
+
| [[File:vmware-demo-restart.png|thumb|400px|Setup has been successful]]
 
|}
 
|}
  
= First steps in the UCS demo system =  
+
= 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.
 
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.
Line 64: Line 91:
 
== SSH Login ==
 
== SSH Login ==
  
A SSH server is installed on the UCS demo system. The user "''root''" can login via SSH, if the network settings have been customized accordingly. With the SSH login the user has direct access to the system (e.g. <tt>univention-config-registry</tt> or view log files in <tt>/var/log/…</tt>).
+
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. <tt>univention-config-registry</tt> or view log files in <tt>/var/log/…</tt>).
  
 
== UCS management system ==
 
== 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 ''<nowiki>https://<IP address></nowiki>''. For example, if the suggested IP address 192.168.0.140 has been set, the URL would be ''https://192.168.0.140''.
+
The UCS management system can be accessed with a web browser through the configured IP address during the initial configuration. The URL is ''<nowiki>https://<IP address></nowiki>''. For example, if the IP address 192.168.0.140 has been set, the URL would be ''https://192.168.0.140''.
  
 
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.
 
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.
Line 74: Line 101:
 
== Graphical login ==
 
== Graphical login ==
  
KDE is installed as desktop on the UCS demo system. It allows users to have a graphical login to the system. The user "''root''" is not allow to login to the desktop by default. To test the graphical environment without adding a new user, the user "''Administrator''" may be used.
+
KDE is installed as desktop on the UCS system. It allows users to have a graphical login to the system. The user "''root''" is should not login to the desktop. To test the graphical environment without adding a new user, the user "''Administrator''" may be used.
  
 
= Add further systems to the UCS environment =
 
= Add further systems to the UCS environment =
Line 80: Line 107:
 
== Windows client computers ==
 
== Windows client computers ==
  
Univention Corporate Server provides functionality known from Microsoft Windows server systeme to Windows client computers. The demo 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 demo 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.
+
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.
  
The following settings are required:
+
This is documented in the [http://docs.univention.de/manual-4.0.html#windows-domaenenbeitritt UCS manual].
* domain name: The domain name has been set in the Basic settings during initial configuration.
 
* User that is allowed to join systems to the domain: <tt>Administrator</tt>
 
* Password: The password has been set in the basic settings for ''Root password'' during initial configuration.
 
 
 
After the Microsoft Windows client computer has joined the domain, an entry for the joined computer is created in the computer management of the domain management.
 
  
 
== UCS systems ==
 
== UCS systems ==
  
If additional UCS systems (servers or desktops) should be operated in the environment, they have to be installed seperately. It is not possible to operate the UCS demo system repeatedly in different system roles. Detailed information about the installation can be found in the [[UCS Quickstart-3.0/en| UCS Quickstart Guide]] and in the {{Manual UCS 3.0|UCS manual}}.
+
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 [http://docs.univention.de/quickstart-en-4.0.html UCS Quickstart Guide] and in the [http://docs.univention.de/manual-4.0.html UCS manual].
  
 
= Documentation =
 
= Documentation =
  
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. {{Manual UCS 3.0|Univention Corporate Server - Manual for users and administrators}} is the available documentation for UCS.
+
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 available in other distributions. The [http://docs.univention.de/manual.html UCS manual] describes many of these features.
  
 
Announcements and discussion about Univention Corporate Server can be found in the Univention Forum. Feedback is welcome in the Forum.  
 
Announcements and discussion about Univention Corporate Server can be found in the Univention Forum. Feedback is welcome in the Forum.  
Line 101: Line 123:
 
Further information to start with Univention Corporate Server can found at the following entry points:
 
Further information to start with Univention Corporate Server can found at the following entry points:
  
* [[UCS Quickstart-3.0/en | UCS Quickstart Guide]]
+
* [http://docs.univention.de/quickstart-en-4.0.html UCS quickstart guide]
* {{Manual UCS 3.0|UCS Manual}}
+
* [http://docs.univention.de/manual.html UCS manual]
 +
 
 +
{{Navigationbar Quickstarts UCS 3}}
 +
[[Category:Quickstart]]

Latest revision as of 07:45, 7 September 2015

Produktlogo UCS Version 4.0
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 zip format for VMware and in the OVA format for VirtualBox.

A sufficiently recent VMware Player (>= 5) or VirtualBox (>= 4.1.12) is recommended.

To start the image, a BIOS option for hardware virtualization has to be activated. Depending on the CPU Vendor, the option is called VT-x or AMD-V.

The image (Download) includes a completely installed and pre-configured UCS system, which can be configured for different system roles. The system offers more possibilities than the online demo system. It is a complete UCS system without 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.

Operation

Starting the VirtualBox image

The UCS VirtualBox image can be downloaded in the OVA format from our download area.

The image can now be imported. Start VirtualBox and select the downloaded image after clicking on FileImport Appliance. When the import is finished the appliance can be started by clicking on the Start button.

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

System boot

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.

Vmware-demo-ucs-initial-configuration.png

Settings

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

Domain and network configuration defines the network configuration for the system. You can leave the setting at "obtain IP address automatically (DHCP)".


Click on Next.

Domänen und Netzwerkkonfiguration
Domain setup for configuration of the UCS system role in the environment. If the system is the first UCS system in the environment, the setting has to be left at Create a new UCS domain.

More information about the domain setup can be found in the UCS manual.

Click on Next.

Domain setup
Administator account information for configuration of the Administrator account on the system. The password for the administrator account has to be provided here.


Click on Next.

Administrator account information
Host settings for configuration of fully qualified domain name (FQDN) and LDAP base. The fully qualified domain name is automatically suggested from the administrator account setting and can be customized.


Click on Next.

Basic settings
Software configuration 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. For example, the component Mail server.


Click on Next.

Software configuration
All necessary settings are made after the software settings and can be applied to the test system by clicking on Configure system.
Configure system
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
Afterwards the system setup is finished and the system is ready for operation.
Setup has been successful

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 IP address 192.168.0.140 has been set, the URL would be https://192.168.0.140.

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 should not login to the desktop. 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 UCS manual.

Documentation

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 available in other distributions. The UCS manual describes many of these features.

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