Ltsp-manager/Netboot clients

There are three basic methods to configure the clients to boot from the network, depending on if the network interface is onboard or if it's a separate PCI/PCI-e card.

Onboard card - BIOS
If your network interface is onboard, then press Del or F2 etc when the clients boot in order to enter the BIOS. There you need to search for and enable up to three settings - the wording may vary:
 * Enable LAN: enables the internal network card
 * Enable Boot ROM: enables the ROM of the network card)
 * Boot sequence - LAN: put LAN before C: or CDROM or Floppy in the boot sequence

Note that at this point, LTSP doesn't support UEFI, so if you have a new computer, you may have to additionally enable the CSM - BIOS Legacy mode.

PCI card - iPXE
If the network card is PCI or PCI-e, then the solution is to use http://www.ipxe.org. This is a small application that supports most network cards and is able to load the kernel from the network. You need to have some local media, e.g. hard disk or CD or floppy in order to use it.

iPXE: win32-loader
If your clients have a disk with Microsoft Windows, then you can put iPXE in the Windows boot loader. Just install this application as administrator: win32-loader.exe.

Note that win32-loader doesn't yet support UEFI installations of Windows.

iPXE: grub package
Many distributions offer an ipxe package that automatically puts a "Boot from network" option in the grub boot manager.
 * Debian: apt install ipxe
 * Ubuntu: apt install grub-ipxe

iPXE: CD and floppy images
You can find CD and floppy images of iPXE in http://boot.ipxe.org/.

Local kernel
In the rare case that you can't netboot the clients either from the BIOS or using iPXE, then it's possible to install the LTSP vmlinuz kernel and initrd.img image to the local client disk, configure grub to boot from those, and set KERNEL_DEVICE="/dev/sda1" in lts.conf so that they're automatically updated with newer versions. This method is outside the scope of this document.