Difference between revisions of "Cool Solution - Run UCC Thinclients from USB-Stick"

From Univention Wiki

Jump to: navigation, search
Line 2: Line 2:
 
{{Cool Solutions Disclaimer}}
 
{{Cool Solutions Disclaimer}}
  
This article describes briefly how you can set up a UCC Thinclient on a USB-Stick to run it apart from your own device.<br>
+
This article describes briefly how to depoly UCC on an USB-Stick to run UCC Thin Clients apart from your own device.<br>
Prerequisites:
 
* UCS DC Master with installed modul UCC
 
  
There are two possible ways to install the UCC on a USB-Stick.
+
= Overview/Background =
For the first solution it is necessary to build your own UCC local image according to the [http://docs.univention.de/ucc-manual-1.0.html#imagegen:toolkit UCC-manual]. Here you can set the parameter "device" with "hda", "sda", "auto" etc. The "auto" determine the first available device and therefore the second solution will be described.
+
 
 +
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 [http://docs.univention.de/ucc-manual-1.0.html#imagegen:toolkit 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.
 
   
 
   
= Demount Flash from Thinclient =
+
= 2. Variant: devices without storage =
The UCC Boot-Menu does not provide a particular Boot-Parameter to select a Boot-Device and therefore it is necessary to demount the flash from the thinclient.  
+
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  [http://docs.univention.de/ucc-manual-1.0.html#rollout:imagerollout 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.
  
= PXE-BOOT with Thinclient =
+
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".
Attach a USB-Stick on the thinclient and rollout the UCC image  [http://docs.univention.de/ucc-manual-1.0.html#rollout:imagerollout 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. It is necessary to join the client one time but afterwards it is possible to use the USB-Stick on any other device.
 

Revision as of 13:10, 2 April 2014

Produktlogo UCC Version 1.0

Note: Cool Solutions are articles documenting additional functionality based on Univention products. Not all of the shown steps in the article are covered by Univention Support. For questions about your support coverage contact your contact person at Univention before you want to implement one of the shown steps.

Also regard the legal notes at Terms of Service.


This article describes briefly how to depoly UCC on an USB-Stick to run UCC Thin Clients apart from your own device.

Overview/Background

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".

Personal tools