> 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/3.6/introduction/release-notes.md).

# Release Notes

This is the 2PXE Server 3.6 release documentation. For other versions, please select the Drop Down list at the Top Left and select the correct version.

### Introduction <a href="#introduction" id="introduction"></a>

iPXE Anywhere 2PXE Server 3.6 is the newest release of 2Pint Software's iPXE solution which replaces version 2.7 as the current release.

#### Release Date <a href="#release-date" id="release-date"></a>

December 8, 2023

#### Release Build Versions <a href="#release-build-versions" id="release-build-versions"></a>

2PXE Server: 3.6.1122.954

### New Features & Functionality <a href="#new-features-and-functionality" id="new-features-and-functionality"></a>

* New 2PXE & Web Service integration

### Improvements/Bug Fixes <a href="#improvements-bug-fixes" id="improvements-bug-fixes"></a>

* Added driver support for new hardware models
* Improved retry logic when downloading from Configuration Manager
* Improved USB BootGen tool with bug fixes
* Improved handling of 802.1x authentication
* Resolved an issue in which a cached security token would not expire until after server reboot
* Resolved an issue in which an authentication method would fail to verify / create token IDs, thus failing the connection


---

# 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/3.6/introduction/release-notes.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.