--- rollout.xml.orig 2014-06-02 14:26:45.078713401 +0200 +++ rollout.xml 2014-06-02 14:36:23.862704019 +0200 @@ -322,15 +322,15 @@
Rollout of UEFI systems - In the default setting, Univention Corporate Client uses a BIOS-based boot. Alternatively, for - systems which no longer support a BIOS boot, there is the possibility of generating UCC images + Univention Corporate Client uses a BIOS-based boot by default. Alternatively, for + systems which no longer support a BIOS boot, it is possible to generate UCC images with which the rollout and operation can be performed via the Unified Extensible Firmware Interface standard. Not all UEFI-compatible systems also support UEFI booting via PXE. This should be checked in - advance and consideration given to updating the UEFI firmware. + advance and consideration given to update the UEFI firmware. @@ -340,16 +340,16 @@ - As standard, the pxelinux.0 boot loader is used for the rollout of BIOS-based - systems and assigned in the &ucsUMC; via a DHCP Boot policy. A + By default, the pxelinux.0 boot loader is used for the rollout of BIOS-based + systems and assigned in the &ucsUMC; via a DHCP Boot policy. An UEFI-compatible boot loader must be assigned via this type of policy for the UEFI rollout. syslinux.efi32 must be assigned as the Boot filename for i386 systems and syslinux.efi64 for amd64 systems. - If a UEFI-compatible image has been generated and the DHCP boot policy defined, the rollout of - a UEFI system is then no different from the standard rollout via the BIOS. + If an UEFI-compatible image has been generated and the DHCP boot policy defined, the rollout of + an UEFI system is no different from the standard rollout via the BIOS.