|
|
|---|
| 322 |
<section id="rollout:uefi"> |
322 |
<section id="rollout:uefi"> |
| 323 |
<title>Rollout of UEFI systems</title> |
323 |
<title>Rollout of UEFI systems</title> |
| 324 |
<para> |
324 |
<para> |
| 325 |
In the default setting, Univention Corporate Client uses a BIOS-based boot. Alternatively, for |
325 |
Univention Corporate Client uses a BIOS-based boot by default. Alternatively, for |
| 326 |
systems which no longer support a BIOS boot, there is the possibility of generating UCC images |
326 |
systems which no longer support a BIOS boot, it is possible to generate UCC images |
| 327 |
with which the rollout and operation can be performed via the <emphasis>Unified Extensible |
327 |
with which the rollout and operation can be performed via the <emphasis>Unified Extensible |
| 328 |
Firmware Interface</emphasis> standard. |
328 |
Firmware Interface</emphasis> standard. |
| 329 |
</para> |
329 |
</para> |
| 330 |
|
330 |
|
| 331 |
<para> |
331 |
<para> |
| 332 |
Not all UEFI-compatible systems also support UEFI booting via PXE. This should be checked in |
332 |
Not all UEFI-compatible systems also support UEFI booting via PXE. This should be checked in |
| 333 |
advance and consideration given to updating the UEFI firmware. |
333 |
advance and consideration given to update the UEFI firmware. |
| 334 |
</para> |
334 |
</para> |
| 335 |
|
335 |
|
| 336 |
<para> |
336 |
<para> |
|
|
|---|
| 340 |
</para> |
340 |
</para> |
| 341 |
|
341 |
|
| 342 |
<para> |
342 |
<para> |
| 343 |
As standard, the <filename>pxelinux.0</filename> boot loader is used for the rollout of BIOS-based |
343 |
By default, the <filename>pxelinux.0</filename> boot loader is used for the rollout of BIOS-based |
| 344 |
systems and assigned in the &ucsUMC; via a <guimenu>DHCP Boot</guimenu> policy. A |
344 |
systems and assigned in the &ucsUMC; via a <guimenu>DHCP Boot</guimenu> policy. An |
| 345 |
UEFI-compatible boot loader must be assigned via this type of policy for the UEFI |
345 |
UEFI-compatible boot loader must be assigned via this type of policy for the UEFI |
| 346 |
rollout. <filename>syslinux.efi32</filename> must be assigned as the <guimenu>Boot |
346 |
rollout. <filename>syslinux.efi32</filename> must be assigned as the <guimenu>Boot |
| 347 |
filename</guimenu> for i386 systems and <filename>syslinux.efi64</filename> for amd64 systems. |
347 |
filename</guimenu> for i386 systems and <filename>syslinux.efi64</filename> for amd64 systems. |
| 348 |
</para> |
348 |
</para> |
| 349 |
|
349 |
|
| 350 |
<para> |
350 |
<para> |
| 351 |
If a UEFI-compatible image has been generated and the DHCP boot policy defined, the rollout of |
351 |
If an UEFI-compatible image has been generated and the DHCP boot policy defined, the rollout of |
| 352 |
a UEFI system is then no different from the standard rollout via the BIOS. |
352 |
an UEFI system is no different from the standard rollout via the BIOS. |
| 353 |
</para> |
353 |
</para> |
| 354 |
</section> |
354 |
</section> |
| 355 |
|
355 |
|