|
|
|---|
| 7 |
</para> |
7 |
</para> |
| 8 |
|
8 |
|
| 9 |
<para> |
9 |
<para> |
| 10 |
When the image is installed, the image installation tool then checks whether there is already a |
10 |
When the image is installed, the image installation tool checks whether there is already a |
| 11 |
computer account available for the client and uses it. If the computer name is not stored in |
11 |
computer account available for the client and uses it. If the computer name is not stored in |
| 12 |
advance, the name can be specified interactively during the installation. |
12 |
advance, the name can be specified interactively during the installation. |
| 13 |
</para> |
13 |
</para> |
|
|
|---|
| 17 |
<para> |
17 |
<para> |
| 18 |
The image with which a UCC client is operated is configured in the |
18 |
The image with which a UCC client is operated is configured in the |
| 19 |
&ucsUMC; in the <guimenu>Images</guimenu> tab on UCC computer |
19 |
&ucsUMC; in the <guimenu>Images</guimenu> tab on UCC computer |
| 20 |
objects. All the UCC images registered in the UCS management |
20 |
objects. All UCC images registered in the UCS management |
| 21 |
system are available for selection. The registration is effected |
21 |
system are available for selection. The registration is effected |
| 22 |
with join scripts during the installation of the image, see <xref |
22 |
with join scripts during the installation of the image, see <xref |
| 23 |
linkend="installation:imagemanagement:download"/>. |
23 |
linkend="installation:imagemanagement:download"/>. |
|
|
|---|
| 33 |
</figure> |
33 |
</figure> |
| 34 |
|
34 |
|
| 35 |
<para> |
35 |
<para> |
| 36 |
UCC clients can be operated in three different installation modes, |
36 |
UCC clients can be operated in five different modes, |
| 37 |
which can be assigned via the <guimenu>Boot variant</guimenu> field: |
37 |
which can be assigned via the <guimenu>Boot variant</guimenu> field. |
|
|
38 |
The client must be configured for PXE boot in the BIOS. |
| 38 |
<itemizedlist> |
39 |
<itemizedlist> |
| 39 |
<listitem> |
40 |
<listitem> |
| 40 |
<simpara><guimenu>Live boot</guimenu> Here the image is |
41 |
<simpara><guimenu>Live boot</guimenu> Here the image is |
| 41 |
started via PXE and mounted via NFS. The client must be configured |
42 |
started via PXE and mounted via NFS. Technically, all UCC systems are always |
| 42 |
for PXE boot in the BIOS. Technically, all UCC systems are always |
|
|
| 43 |
treated as having read/write storage media: If an image is mounted from a |
43 |
treated as having read/write storage media: If an image is mounted from a |
| 44 |
source which itself only allows readonly access (from a live DVD or as |
44 |
source which itself only allows readonly access (from a live DVD or as |
| 45 |
in this case from a NFS share), an OverlayFS file system is employed: |
45 |
in this case from an NFS share), an OverlayFS file system is employed: |
| 46 |
All the write changes are cached in the system memory and are lost when the computer is |
46 |
All the write changes are cached in the system memory and are lost when the computer is |
| 47 |
switched off. Thin clients are also always run with an overlayfs |
47 |
switched off. Thin clients are also always run with an overlayfs |
| 48 |
for a local installation, further information can be found under |
48 |
for a local installation, further information can be found under |
|
|
|---|
| 53 |
<para> |
53 |
<para> |
| 54 |
<guimenu>Installation with repartitioning and image rollout</guimenu>: This mode is used for |
54 |
<guimenu>Installation with repartitioning and image rollout</guimenu>: This mode is used for |
| 55 |
the initial installation of a UCC client. It is also required whenever a UCC client should |
55 |
the initial installation of a UCC client. It is also required whenever a UCC client should |
| 56 |
be installed completely or switched to a different partition scheme. The partitions of the |
56 |
be reinstalled completely or switched to a different partition scheme. The partitions of the |
| 57 |
system are setup as configured in the image configuration. A prompt must be |
57 |
system are setup as configured in the image configuration. A prompt must be |
| 58 |
confirmed before the partitioning begins (it can be disabled using the boot option |
58 |
confirmed before the partitioning begins (it can be disabled using the boot option |
| 59 |
<emphasis>force_partition</emphasis>, see below). After the installation of the image, the |
59 |
<emphasis>force_partition</emphasis>, see below). After the installation of the image, the |
|
|
|---|
| 71 |
<para> |
71 |
<para> |
| 72 |
<guimenu>Image boot with update check</guimenu> is used to update an existing UCC |
72 |
<guimenu>Image boot with update check</guimenu> is used to update an existing UCC |
| 73 |
installation to a new version. It is detected whether the installed image differs |
73 |
installation to a new version. It is detected whether the installed image differs |
| 74 |
from the image to be installed. If that is the case, the UCC system partition is |
74 |
from the image to be installed. If that is the case, the UCC image on the system is replaced. |
| 75 |
overwritten. In contrast to the partition option above, no new partitioning occurs. |
75 |
In contrast to the partition option above, no new partitioning occurs. |
| 76 |
</para> |
76 |
</para> |
| 77 |
</listitem> |
77 |
</listitem> |
| 78 |
|
78 |
|
| 79 |
<listitem> |
79 |
<listitem> |
| 80 |
<para> |
80 |
<para> |
| 81 |
<guimenu>Image boot without update check</guimenu>: In this boot mode, the locally installed |
81 |
<guimenu>Image boot without update check</guimenu>: In this boot mode, the locally installed |
| 82 |
image is started and no check for a newly available image performed. Following an |
82 |
image is started and no check for a newly available image performed. Following a successful |
| 83 |
installation performed with <guimenu>Image boot with update check</guimenu> or |
83 |
installation performed with <guimenu>Image boot with update check</guimenu> or |
| 84 |
<guimenu>Installation with repartitioning and image rollout</guimenu>, the system returns to |
84 |
<guimenu>Installation with repartitioning and image rollout</guimenu>, the system returns to |
| 85 |
this boot mode automatically. |
85 |
this boot mode automatically. |