> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/2pxe-server/4.0/reference/boot-media-tools.md). # Boot Media Tools 2PXE Server 4.0 installs two tools in the **Tools** folder of the 2PXE installation folder (by default `C:\Program Files\2Pint Software\2PXE\Tools`). ## iPXE Anywhere Boot Media Generator (BootGen.exe) **BootGen.exe** generates USB drives and ISO files that boot iPXE and connect to 2PXE. Use boot media for devices that cannot PXE boot, for example devices without a supported network adapter for PXE, or on networks where DHCP options and IP helpers cannot be configured. In the tool, select the target USB drive (or create a boot disk), choose the 2PXE server the media should connect to, and then write the files to the drive. The tool can also keep existing media up to date with the latest boot files. {% hint style="info" %} BootGen runs as an administrator (it prompts for elevation), because it partitions and formats USB drives. {% endhint %} ### The autoexec.ipxe script iPXE can run an `autoexec.ipxe` script when it starts. 2PXE serves this script for each architecture over TFTP and from its web service at `/2PXE/Boot//autoexec.ipxe` (for example `http://:8049/2PXE/Boot/x64/autoexec.ipxe`): * If an `autoexec.ipxe` file exists in the `Boot\` folder under the RemoteInstall folder, 2PXE serves that file. Otherwise, it generates a script that sets `bootroot` to the 2PXE server's URL. * In either case, 2PXE adds commands at the start of the script that set the device's clock to the 2PXE server's time. If the device's iPXE cannot set its clock that way, and the clock is far off, the script uses the NTP server specified by the **NtpServer** setting instead. A correct clock is needed for HTTPS certificate checks. ## iPXE binary identifier (iPXEIdentifier.exe) **iPXEIdentifier.exe** is a command-line tool that shows details about an iPXE binary, such as its version and build information. Use it to check which iPXE build a boot file or boot media contains, for example when working with 2Pint Software support. ``` iPXEIdentifier.exe ``` BIOS (`pcbios`) binaries such as `undionly.kpxe` are not supported. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://documentation.2pintsoftware.com/2pxe-server/4.0/reference/boot-media-tools.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.