> 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).

# Use existing PXE infrastructure

PXE is not officially supported as a Foundry OSD media output. Foundry OSD does not configure or manage PXE, DHCP, TFTP, or third-party PXE server infrastructure.

{% hint style="warning" %}
Use this workaround only with an existing, working PXE environment. PXE configuration, operation, and support remain the responsibility of the PXE infrastructure owner.
{% endhint %}

## Before you begin

Confirm that you have:

* An existing PXE environment that supports importing and starting WIM boot images.
* Permission to import, configure, and advertise boot images on the PXE server.
* A client architecture and firmware mode compatible with the Foundry OSD ISO and PXE environment.
* Any WinPE network drivers required by the target hardware included when the ISO is created.
* Network access from Windows PE to the services required by [Foundry Connect](/foundry-connect.md) and [Foundry Deploy](/foundry-deploy.md).

## Prepare the boot image

1. [Create an ISO](/foundry-osd/media/create-iso.md) and validate that it boots on representative hardware or a virtual machine.
2. Mount the validated ISO.
3. Locate `sources\boot.wim` on the mounted ISO.
4. Copy `sources\boot.wim` to a location accessible to the PXE administrator.
5. Import the copied WIM as a boot image into the existing PXE server.
6. Configure and advertise the boot image according to the PXE vendor documentation.

## Validate the deployment

1. Boot a representative client from the imported image.
2. Confirm that Windows PE obtains the required network access.
3. Confirm that [Foundry Connect](/foundry-connect.md) starts and reports network readiness.
4. Continue and confirm that [Foundry Deploy](/foundry-deploy.md) starts.
5. Complete one representative end-to-end deployment.
6. Confirm that Foundry Deploy reports successful completion.
7. Complete the relevant [post-boot checks](/foundry-deploy/verify-deployment.md).

Resolve driver, architecture, firmware, or network compatibility issues in the ISO and PXE environment before wider deployment.

## Maintain the boot image

Re-import `sources\boot.wim` whenever the Foundry OSD ISO is regenerated. Keep the previous boot image available until the replacement has passed PXE boot and runtime validation on representative clients.

## Custom image payloads

[Custom Windows images](/foundry-osd/customization/custom-windows-images.md) are external to `sources\boot.wim`. Copying that boot image alone does not transfer custom images or their manifest. This feature does not provide a supported PXE delivery path for custom WIMs; use the complete generated ISO or USB media.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.foundryosd.com/foundry-osd/media/pxe-deployment.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.