iPXE Anywhere is a network booting solution using the Open Source iPXE network boot firmware. We add the “Anywhere” components which is a set of server components and support infrastructure components to make iPXE sing and dance even more, by communicating with the iPXE client software, and enabling seamless integration with WDS, SCCM etc.
We are investing in the iPXE development program too, and have funded the implementation of Microsoft BranchCache into the iPXE software itself. But that is still part of the Open Source iPXE available to everybody for free. See it as our sacrifice to the PXE gods..
If iPXE is free, why should we pay for iPXE Anywhere?
The answer is, you don’t have to. If you want to build the solution yourself we will support that endeavor as well, we just won’t be able to support your code. The way that we see things is, that the more people use iPXE the merrier. We love the community feel to iPXE, it’s like the old days of IT before the corporate conglomerates took over everything. It also means that you can have a real say in the future of the technology, with a large support network of like-minded souls!
If however you don't have the time (it took us a year to put this thing together!), or the inclination to build your own solution, we made iPXE Anywhere for you. It's built by us, supported by us, and it won't cost you an arm and a leg. More like your pinky finger or a toe or something..
The iPXE Anywhere Concept
The iPXE Anywhere solution is designed to be flexible yet powerful and work with most operating systems and boot servers. So if you need to support Macs, Linux etc you're in the right place!
The default iPA (iPXE Anywhere)setup uses Windows Deployment Services as the PXE engine, providing the Proxy DHCP and TFTP capabilities.
Overview
A machine requesting PXE boot will be picked up by the network boot server (WDS for example). The server will parse the request and send the corresponding boot file (BIOS or EFI) to the client. This file is very small and handles low bandwidth situations really well. Once the iPXE Boot Program is downloaded, it will contact the 2Pint iPXE Anywhere Web Service to lookup the right action to execute. Once an action is detected the server will send back the corresponding boot script to the client. Following so far? The client will then execute this script, which typically involves loading a high level OS (WinPE) over HTTP. Once in WinPE, the system will contact the network boot server to get the right action to execute again. In the Windows world, this typically means launching a Task Sequence from ConfigMgr or MDT.
iPXE Components - in more detail
iPXE Anywhere consist of several components, some server and some client focused. All the server components can be installed on a single server for small environments, or several for larger environments.
Network Boot Server
This is the server that responds to the initial PXE request unless DHCP options are used to control the PXE booting process. This server also acts as the TFTP server, offering the intial iPXE NBP files to the clients.
Booting Flow
- Client requests PXE boot through keyboard input or Hardware settings
- DHCP Request of info of where to boot
- Boot server replies with TFTP path of the iPXE Network Boot Program and possibly DHCP info if not using DHCP options.
- iPXE Network Boot Program is downloaded using TFTP
- iPXE Network Boot Program initializes the hardware accordingly and contacts the iPXE Anywhere Web Service over HTTP(S) for boot actions.
- iPXE Web Service writes configuration data to file or database
- iPXE Web Service reads the supplied configdata from the NBP and gets the .bcd file from the network boot server
- iPXE Web Service modifies the .bcd file and send it back to the Network Boot Server.
- iPXE Web Service sends reply to NBP of .bcd location and other boot critical data
- iPXE Network Boot Program executes boot actions set by the server side
iPXE Network Boot Program (NBP)
This is the core essence of iPXE Anywhere. A customized version of the open source iPXE solution tailored to work with the 2Pint iPA server environment. BranchCache aware, it can grab content such as WinPE from other BranchCache enabled peer computers, which reduces WAN traffic considerably.
IIS Server for file access
An IIS (or BranchCache capable web service) is required for iPXE Anywhere to download content over HTTP leverageing BranchCache
iPXE Anywhere Web-Service
This is a Windows .Net service that hosts the iPXE Web Service that the iPXE Network Boot Program talks to. This service talks HTTP with the client and SQL to the SQL DB (if present). It also downloads and creates .bcd files on the WDS server. Each .bcd file is about 16kb and makes a return trip, equaling to about 50k of network traffic per network boot operation. The process has to wait for this to finish before allowing the network boot, so transfer latency applies to the overall network boot speed.
iPXE Anywhere SQL Database(s)
This database stores info about PXE booted computers and their capabilities. This database can be hosted on SQL Express if necessary as traffic to this database is very small. Optional
iPXE Anywhere SQL Reportings Services
An instance of SQL reporting services used to pull reports from the SQL database.Optional
Next - Part iii - The Data Transfer Flow
Doris The Bot..