Cool Solution - Run UCC Thinclients from USB-Stick
From Univention Wiki
This article describes briefly how to deploy UCC on an USB-Stick to run UCC Thin Clients apart from your own device.
UCC uses a partitioning defined in the image-configuration. This can not easily be changed once the image is generated, as it is part of the PXE boot process (initrd). There are two possible ways to install the UCC on a USB-Stick: modify the partitioning definition and generate a new image or deploy UCC on a device without local storage.
1. Variant: define an individual image
For the first solution it is necessary to build your own UCC local image according to the UCC-manual. Here you can set the parameter "device" with "hda", "sda", "auto" etc. The "auto" is default and determines the first available device, which usually is a local storage.
To deploy UCC on devices with local storage (usually "sda"), the "device" parameter must be set to the second device (usually "sdb"). If unsure which device name to use, boot the client over the network, connect to it using ssh and examine "/proc/partition" or "/var/log/kern.log". Once the device name is defined the image can be build and deployed as documented in the UCC-manual.
2. Variant: devices without storage
If your device has no local storage, or the storage can be deactivated (in BIOS) or dismounted, you can use the default UCC images.
Attach a USB-Stick on the thinclient and rollout the UCC image via PXE. The USB-Stick should be automatically detected. Choose "Image boot with update check / Initial installation" and "Repartitioning for installed systems" in the Univention-Management-Console.
Use USB-sticks for unknown clients
During rollout, it is necessary to join the client into the domain. Afterwards it is possible to use the USB-Stick on any other device.
If more than one unknown client should be deployed and therefore more than one USB stick is needed, those USB sticks should not be deployed using the default workflow of UCC: UCC generates a new password for the host account on each rollout, which makes older USB sticks "unmanageable". You should use an individual hostname for each deployment or clone an USB stick using tools like "dd".