NOTE: brainstorming; not final
Boot into a Windows PE operating system generated according to these instructions via TFTP.
No physical disks present. System configured to boot from NIC equipped with gPXE ROM.
TFTP server hosting WinPE files. DHCP server providing network configuration and path to WinPE's \Boot\pxeboot.n12 file.
Success is defined as reaching WinPE's X:\Windows\system32 command prompt.
Boot into a Windows Server 2003 operating system stored on an iSCSI target that requires forward CHAP authentication.
No physical disks present. System configured to boot from NIC equipped with gPXE ROM. NIC non-volatile storage configured with iSCSI username and password.
iSCSI target running IETD set up to require forward CHAP authentication. DHCP server providing network configuration and iSCSI root-path, but not providing iSCSI username and password (which are held in the DUT's non-volatile storage).
Success is defined as reaching the Windows graphical login screen.
Boot into a minimal Linux/busybox system created using mkbootfs via HTTP.
No physical disks present. System configured to boot from NIC equipped with gPXE ROM.
Apache HTTP server providing gPXE script, kernel, initrd, and modules as separate files. gPXE script set to instruct client to download kernel, initrd and relevant modules. DHCP server providing network configuration and path to gPXE script on HTTP server.
Success is defined as reaching the busybox shell prompt.