> For the complete documentation index, see [llms.txt](https://docs.foundryosd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foundryosd.com/foundry-osd/media/pxe-deployment.md).

# Deploy with PXE

Create the files a PXE server needs to start devices from the network with Foundry. Foundry OSD writes them to a folder; it does not configure the PXE server, DHCP or TFTP, which stay the responsibility of their administrator.

<figure><img src="https://64695594-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdn0pr5zia6oG2DU1R1Pn%2Fuploads%2Fgit-blob-9b8b5128558bd0d9fbfe9c93d0ccf5ac3429c1f5%2Ffoundry-osd-media-pxe-01-destination.png?alt=media" alt="Create PXE files dialog over the Start page, with a destination folder typed and the Create and Cancel buttons"><figcaption><p>The <strong>Create PXE files</strong> dialog. When your configuration has imported content, the dialog also lists it under <strong>Not delivered with a PXE start</strong>.</p></figcaption></figure>

## Before you start

* No row of [Start](https://docs.foundryosd.com/foundry-osd/media.md) is marked **Needs attention**.
* 20 GB are free on the drives listed in [Start](https://docs.foundryosd.com/foundry-osd/media.md#before-you-start). The destination folder only needs room for the four files, about the size of `boot.wim`.
* The architecture, the language and the drivers of Windows PE are set in [General](https://docs.foundryosd.com/foundry-osd/general.md). The network drivers the devices need in Windows PE must be there.
* A PXE server that can start a UEFI device from a WIM boot image, and the right to add a boot image to it.
* Internet access from Windows PE to the hosts in [Network endpoints](https://docs.foundryosd.com/reference/network-endpoints.md).

## Create the PXE files

1. Open **Start** and select **Create PXE files**.
2. In **Destination folder**, type the folder or select **Browse**. A network share written as `\\server\share\folder` works. The folder you used last time is filled in.
3. Read the warnings of the dialog, then select **Create**:
   * "This folder already contains a boot image." The four files below are replaced. Other files of the folder are kept.
   * **Not delivered with a PXE start** lists the [imported content](#what-a-pxe-start-delivers) of your configuration that devices started from the network will not have. It does not appear while the [network cache](https://docs.foundryosd.com/foundry-osd/network-cache.md) is on with at least one share.
4. If a dialog titled **Update Foundry OSD before creating boot media** opens, apply the update first, or select **Create anyway**.
5. Wait until the dialog is titled **PXE files created** and reads "The PXE boot files were saved to:", followed by the folder and the total size. Select **Open folder** to open it, or **Close**.

| File          | Use                                                                                                                                                                                       |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `boot.wim`    | The boot image: Windows PE, its drivers, Foundry Connect and your options, built like the boot image of an ISO. Import this file in Windows Deployment Services or Configuration Manager. |
| `boot.sdi`    | The RAM disk image that Windows PE starts from.                                                                                                                                           |
| `BCD`         | The UEFI boot configuration that loads `boot.wim`.                                                                                                                                        |
| `bootmgr.efi` | The UEFI boot manager, signed for the **Secure Boot** choice of [General](https://docs.foundryosd.com/foundry-osd/general.md).                                                            |

PXE servers that start Windows PE with wimboot, such as iPXE or FOG, can load the four files together; check in the documentation of your server under which name it expects the UEFI boot manager. The files start UEFI devices only.

Foundry OSD replaces the files only once all four are written: a failed or canceled creation keeps the previous ones.

## What a PXE start delivers

| Delivered                                                                                                                                                      | Not delivered                                                                                                                                                                                                                                                |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Windows PE with its drivers, and Foundry Connect. As with an ISO, Foundry Deploy is downloaded when the device starts.                                         | [Custom Windows images](https://docs.foundryosd.com/foundry-osd/customization/custom-windows-images.md) and [custom driver sets](https://docs.foundryosd.com/foundry-osd/customization/custom-drivers.md)                                                    |
| Every option of your configuration: network, Windows Autopilot, Domain Join, computer name, OOBE, answer file, optional features, AppX removals, AI components | [Post-installation](https://docs.foundryosd.com/foundry-osd/customization/post-installation.md) actions that use imported files: every **PowerShell script (.ps1)** and **Software (.exe/.msi)** action, and a **Command line** action with imported content |
| Post-installation actions that need no imported file: **Command line** without content and **Restart Windows**                                                 | A cache: each deployment downloads Windows and the driver pack again                                                                                                                                                                                         |

With the [network cache](https://docs.foundryosd.com/foundry-osd/network-cache.md) on, the device gets what this table lists as not delivered from its share: Foundry OSD publishes the imported content to every share when it creates the PXE files, and Foundry Deploy takes the Windows image and the driver pack from the share when another device already published them. The device must be in an IP scope and reach one of its shares.

Without the network cache, a deployment that needs a post-installation action with imported files stops before the disk is erased. With the network cache on, a device that reaches none of its shares stops when Foundry Deploy opens: see [If a device stops at start](https://docs.foundryosd.com/foundry-osd/network-cache.md#if-a-device-stops-at-start). Start those deployments from an [ISO](https://docs.foundryosd.com/foundry-osd/media/create-iso.md) or a [USB drive](https://docs.foundryosd.com/foundry-osd/media/create-usb.md), turn on the network cache, or disable the actions in Foundry OSD and create the PXE files again. See [PXE start](https://docs.foundryosd.com/troubleshooting/media-creation/usb-drive-and-device-start.md#pxe).

## Check the result

1. Import the files in your PXE server, following the documentation of that server.
2. Start a test device from the network.
3. Check that Foundry Connect opens and reports the network as ready, then that Foundry Deploy opens.
4. Run one complete deployment and the [post-deployment checks](https://docs.foundryosd.com/foundry-deploy/verify-deployment.md).

## Keep the boot image up to date

Each time you change the configuration, create the PXE files again and import them again. Keep the previous boot image on the PXE server until the new one has started a test device.

## Related

* [Start: create deployment media](https://docs.foundryosd.com/foundry-osd/media.md)
* [Create an ISO](https://docs.foundryosd.com/foundry-osd/media/create-iso.md)
* [Network cache](https://docs.foundryosd.com/foundry-osd/network-cache.md)
* [Windows PE startup](https://docs.foundryosd.com/foundry-connect/windows-pe-startup.md)
* [USB drive and device start troubleshooting](https://docs.foundryosd.com/troubleshooting/media-creation/usb-drive-and-device-start.md)


---

# 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://docs.foundryosd.com/foundry-osd/media/pxe-deployment.md?ask=<question>&goal=<user_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.
