> 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/configuration/booting-custom-entries-in-2pxe-menu.md).

# Booting custom entries in 2PXE menu

Custom 2PXE boot menu entries (CustomMenuItems) are not available in 2PXE Server 4.0.

{% hint style="warning" %}
The `CustomMenuItems` and `CustomItems` sections that 2PXE Server 3.x read from the **2Pint.2PXE.Service.exe.config** file are not available in 2PXE Server 4.0. 4.0 no longer uses the `.config` file, and the **Configure 2PXE** configuration editor has no equivalent setting.
{% endhint %}

If you need custom actions during the boot process, such as opening an iPXE shell, booting a custom WinPE image or calling the iPXE Anywhere Web Service, use one of the following instead:

* **iPXE Anywhere Web Service:** turn on **Integrate with iPXE Anywhere Web Service** in the configuration editor and return a custom iPXE script from the web service's PowerShell scripts.
* **PowerShell integration mode:** set **Integration mode** to **PowerShell** and control the boot process with the PowerShell extension scripts. See [PowerShell Request Handler](/2pxe-server/4.0/configuration/2pxe-config-file/powershell-request-handler.md).

For more information about the settings, see [Configuring 2PXE Server](/2pxe-server/4.0/configuration/2pxe-config-file.md). If you have custom scripting scenarios you would like to discuss, contact <support@2pintsoftware.com>.


---

# 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/configuration/booting-custom-entries-in-2pxe-menu.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.