networkbooted

Networkbooted (also written network-booted) describes a computer or device that loads its firmware, bootloader, or operating system over a network rather than from local nonvolatile storage. The process typically begins with a network firmware request that uses DHCP or BOOTP to obtain network configuration and the location of a boot image, followed by transfer of boot files via protocols such as TFTP, HTTP(S), or iSCSI.

Common implementations include the Preboot Execution Environment (PXE) and its open-source derivatives like iPXE, which add features such as HTTP boot, scripting, and authentication. Network boot can deliver full diskless systems, root filesystems over NFS, or installers and live images for provisioning and recovery. It is widely used for thin clients, cluster nodes, automated operating system deployment, stateless server farms, and system rescue.

Advantages of networkbooted environments include centralized image management, simplified updates, faster mass deployment, and reduced local storage requirements. Drawbacks include dependence on network availability and bandwidth, increased initial complexity, potential single points of failure, and specific security concerns related to boot file integrity and network-based attacks.

Mitigations and best practices often involve using secure boot and signed images, TLS-protected transport where possible, network segmentation, DHCP and PXE access controls, and redundant provisioning services. Network booting remains a practical tool in many enterprise, cloud, and lab environments for scalable, automated system management.