opsi Version 3.3.1 - opsi Download - uib

5. Netboot products: Automated OS installation and more
• The automated software distribution then installs all the software packages as
defined in the client's configuration.
5.1.2. Preconditions
First of all an opsi depot server has to be installed.
The client PC has to be equipped with a bootable network controller. Most recent
network controllers provide this functionality (PXE boot), also recent network controllers
which are integrated on the PC's main board. The PXE software, which is stored in the
'bootprom' of the network controller, controls the boot process via network according to
the BIOS boot device sequence. Usually the boot sequence has to be set in the BIOS,
'network-boot' has to be the first boot device.
On request also the support of 'bootp' bootproms is available.
The opsi installation package for the OS to be installed needs to be provided on the
depot server. In the following we assume Windows 2000 to be the OS to install.
5.1.3. PC-client boots via the network
The PXE firmware gets activated at startup of the PC. Part of the PXE implementation
is a DHCP client.
Depot-Server
from
/etc/hosts +
/etc/dhcp3/dhcpd.conf
Figure 20: Step 1 during PXE-Boot
dhcpdiscover
dhcpoffer
dhcprequest
dhcpack
76
PC/Client
PXE-Bootprom
becomes active
PC now knows:
- it's IP
- the server
- Gateway and netmask
- bootfilename