This blog post details how to set up a network bootable Windows 11 installation using iSCSI for storage and iPXE for booting. The author outlines the process of preparing a Windows 11 image for iSCSI, configuring an iSCSI target (using TrueNAS in this example), and setting up an iPXE boot environment. The guide covers partitioning the iSCSI disk, injecting necessary drivers, and configuring the boot process to load the Windows 11 installer from the network. This allows for a centralized installation and management of Windows 11 deployments, eliminating the need for physical installation media for each machine.
This blog post details the process of setting up a network boot environment for Windows 11 using iSCSI for storage and iPXE for booting. The author's goal is to create a system where the operating system resides entirely on a network share, allowing for centralized management and deployment of Windows 11 installations.
The process begins with configuring an iSCSI target, which will act as the hard drive for the networked Windows 11 installation. The author uses TrueNAS SCALE as the iSCSI server, highlighting its user-friendly interface for creating and managing iSCSI targets. The specific steps involved in configuring the target are outlined, including setting the target name, creating an extent (which represents the virtual disk space), and finally creating the target itself.
Next, the blog post addresses the preparation of the Windows 11 installation files. This involves downloading the Windows 11 ISO image and using a tool like oscdimg to create a bootable ISO. This ISO is then mounted, and its contents are copied to a directory on the iSCSI target that has been mounted on the server. This effectively places the Windows 11 installation files on the network share.
With the storage prepared, the focus shifts to configuring the network boot environment using iPXE. The author leverages the flexibility of iPXE scripting to automate the boot process. The provided iPXE script first retrieves the Windows 11 boot files (bootmgfw.efi) from the iSCSI target via HTTP. This crucial step enables the system to initiate the Windows 11 installation process from the network. The script then proceeds to load the Windows 11 installer environment using the retrieved boot file. This sets the stage for the actual Windows 11 installation.
The blog post then walks through the Windows 11 installation process within this network boot environment. It emphasizes the importance of selecting the correct storage driver during the installation process. Because the "hard drive" is the iSCSI target, a specific driver needs to be loaded to allow the installer to recognize and interact with it. The author recommends using the StarWind iSCSI Initiator driver for this purpose. The remaining steps of the Windows 11 installation are standard, including partitioning the iSCSI target, selecting the installation location, and completing the setup process.
Finally, after the installation completes, the post briefly discusses the process of configuring the network boot environment for ongoing use. This entails ensuring the iPXE script is readily available for client machines to access during boot, allowing them to load the installed Windows 11 instance from the iSCSI target each time they start up. The author suggests serving the iPXE script via a DHCP server or TFTP server for easy network access. This creates a truly diskless Windows 11 environment, booting and operating entirely from the network.
Summary of Comments ( 23 )
https://news.ycombinator.com/item?id=43204604
Hacker News users discuss the practicality and potential benefits of netbooting Windows 11 using iSCSI and iPXE. Some question the real-world use cases, highlighting the complexity and potential performance bottlenecks compared to traditional installations or virtual machines. Others express interest in specific applications, such as creating standardized, easily deployable workstations, or troubleshooting systems with corrupted local storage. Concerns about licensing and Microsoft's stance on this approach are also raised. Several users share alternative solutions and experiences with similar setups involving PXE booting and other network boot methods. The discussion also touches upon the performance implications of iSCSI and the potential advantages of NVMe over iSCSI for netbooting.
The Hacker News post titled "Netboot Windows 11 with iSCSI and iPXE" has generated several comments discussing various aspects of network booting Windows and the author's approach.
Several commenters focused on the complexities and challenges associated with network booting Windows, particularly regarding licensing and driver management. One commenter highlighted the difficulty in getting all the necessary drivers loaded correctly during the boot process, often requiring specific drivers for the network card and storage controller to be injected early on. This commenter also pointed out that dealing with different hardware configurations can further complicate matters. The licensing aspect was also brought up, with concerns about whether Microsoft permits this kind of setup and how to activate Windows in such an environment.
The discussion also touched on the practicality and use cases of netbooting Windows. Some questioned the real-world benefits compared to other deployment methods like traditional imaging or virtual machines, particularly for home use. They pointed out that maintaining the iSCSI target and the network infrastructure adds complexity that might outweigh the advantages for individual users. However, others suggested potential scenarios where netbooting could be beneficial, such as in enterprise environments for standardized deployments, testing, or disaster recovery situations.
A few commenters shared alternative approaches and technologies for netbooting or achieving similar results. One commenter mentioned using WDS (Windows Deployment Services) as a more integrated solution within the Windows ecosystem. Another commenter discussed the advantages of using a hypervisor for greater flexibility and control over the environment.
There's also a thread discussing the performance implications of iSCSI, particularly for booting an operating system. One commenter questioned the speed and responsiveness of booting from an iSCSI target, while another suggested that modern networks and hardware can mitigate potential performance bottlenecks. Someone with experience using iSCSI for booting other operating systems like Linux chimed in, noting that performance can be acceptable but depends heavily on the network infrastructure.
Finally, some comments offered additional tips and resources related to iPXE, network booting, and Windows deployment in general. One user suggested a resource for building custom iPXE boot images. Another highlighted the potential security considerations of network booting, emphasizing the importance of securing the boot process and protecting against unauthorized access.