> 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/deployr/1.1/setup/configuring-pxe-booting/using-2pxe.md).
# Using 2PXE
The simplest option for PXE booting the DeployR boot images is using the 2Pint Software 2PXE service. See the [2PXE documentation](https://documentation.2pintsoftware.com/2pxe-server) for information on installation and configuration.
To support DeployR, you can enable the **PowerShell Integrated Installation** option, either at install time or later by editing the 2Pint.2PXE.Service.exe.config file to set the "EnablePowerShellExtension" value to "1". Then, edit the "PowerShellBootExtensionBootImages.ps1" script to add an entry near the bottom of the script:
```
$bootimages.Add("DeployR_x64","x64")
```
Restart the 2PXE service after making configuration or script changes.
During the Windows PE boot image generation process, DeployR will automatically copy the needed files to a location where 2PXE can find them.
{% hint style="info" %}
Note: 2PXE does not yet support ARM64 booting. The PowerShell extension does not support Linux booting, although it is possible to use the Configuration Manager extension to add Linux or Windows custom menu options. See the [2PXE documentation](https://documentation.2pintsoftware.com/2pxe-server/configuration/booting-custom-entries-in-2pxe-menu) for more information.
{% endhint %}
---
# 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/deployr/1.1/setup/configuring-pxe-booting/using-2pxe.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.
