From Univention Wiki
This documentation describes how to create an appliance based on UCS 3. It is recommended to use the latest UCS 3 version. The appliance mode can only configured on a Domaincontroller Master. Later in the configuration wizard it is possible to change the server role.
While selecting the system role in UCS 3 Domaincontroller Master installation, F3 must be pressed. This will disable the join scripts. After the installation the system should be upgraded to the latest version, for example by running the following command as user root:
In UCS 3.0-2 are several fixes. Until this release is available it is possible to install the required packages from the scope system-setup3.0-1. To activate this scope the following steps are required:
ucr set repository/online/component/system-setup3.0-1=yes \ repository/online/component/system-setup3.0-1/parts=unmaintained univention-upgrade
After that the package univention-system-setup-boot should be installed. There are three ways to configure the UCS system: local, remote or automatic.
The local configuration will start at the next boot a firefox session. For this setup the access to the graphical console of the system is essential. In this session all requirements for the configuration will be asked and the system will be configured. To activate this mode univention-system-setup-boot can be installed by the following command:
The remote configuration is necessary whether the access to the local console is not given. The configuration takes place in a remote web browser session. Therefor the network address of the booting system must be known. Usually the X window system will be installed when univention-system-setup-boot is installed, this can be prevented by adding --no-install-recommends to the command. Additional the start of firefox should be prevented by disabling the UCR variable system/setup/boot/start:
univention-install univention-system-setup-boot --no-install-recommends ucr set system/setup/boot/start="false"
An automatic configuration is possible by creating a profile file (/var/cache/univention-system-setup/profile). Here is an easy example for creating such a file and running setup-join.sh:
cat > /var/cache/univention-system-setup/profile <<__HERE__ hostname="ucs" domainname="testdom.local" windows/domain="TESTDOM" ldap/base="dc=testdom,dc=local" root_password="univention" components="univention-s4-connector:univention-samba4 univention-nagios-server" packages_install="univention-s4-connector univention-samba4 univention-nagios-server" packages_remove="" # interfaces/eth0/type="dynamic" interfaces/eth0/type="" interfaces/eth0/address="10.201.101.2" interfaces/eth0/netmask="255.0.0.0" interfaces/eth0/network="10.0.0.0" interfaces/eth0/broadcast="10.255.255.255" dns/forwarder1="10.201.74.2" gateway="10.201.0.1" __HERE__ /usr/lib/univention-system-setup/scripts/setup-join.sh >>/var/log/univention/setup.log 2>&1
Preparing Amazon EC2 Images
The easiest way is to install UCS into KVM with the raw image format for the harddisks, one for root and one for swap. As architecture is amd64 recommended. Amazon EC2 images must be configured with the remote or automatic mode, because the access to the local console is not given.
Amazon EC2 uses Xen, therefore the following changes are required after the installation, upgrade and configuration:
# change from sda to xvda ucr set grub/root=/dev/xvda1 sed -i 's|/dev/sda1|/dev/xvda1|' /etc/fstab append="$(ucr get grub/append)" ucr set grub/append="$(echo "$append" | sed -e 's|/dev/sda|/dev/xvda|g;s|splash|nosplash|')" ucr set grub/groot="(hd0)" # generate all UMC languages ucr set locale/default="en_US.UTF-8:UTF-8" locale="en_US.UTF-8:UTF-8 de_DE.UTF-8:UTF-8"; locale-gen #SSH with authentication key will be used in EC2, so remove the root password sed -i 's|root:[^:]*|root:|' /etc/shadow # Activate EC2 mode ucr set server/amazon=true