iPXE Anywhere 2PXE Server
3.6
3.6
  • Start Here - 2PXE Server 3.6
  • Introduction
    • 2PXE Overview
    • Technical Overview
    • Release Notes
  • Proof of Concept
    • Objectives & Prerequisites
    • Install and Configure 2PXE
    • Testing and Validation
    • 2PXE POC Quick Checklist
  • Planning
    • Planning Your Implementation
    • Permissions
    • Firewall Considerations
    • Antivirus Exclusions
  • Installation
    • 2Pint PXE Server Manual Installation
    • Unattended Installation
    • 2PXE Post Installation Checks
  • Configuration
    • 2PXE Server Configuration File
      • Configuring the 2PXE Request Handlers
    • DHCP Configuration
      • Using DHCP Scope Options
        • Overview - DHCP Scope Options
        • Creating DHCP Scope Options
          • Manually Creating DHCP Scope Options
      • Using IP Helpers
    • Booting custom entries in 2PXE menu
    • iPXE 802.1x Integration
  • Troubleshooting
    • Overview
    • Multi NIC and trunks implementations
    • Custom entries in WinPEShl.ini
    • DP Package Share IIS Permissions
  • Reference
    • iPXE Console Commands
Powered by GitBook
On this page
  • Introduction
  • New Features & Functionality
  • Improvements/Bug Fixes
  1. Introduction

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

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

December 8, 2023

Release Build Versions

2PXE Server: 3.6.1122.954

New Features & Functionality

  • New 2PXE & Web Service integration

Improvements/Bug Fixes

  • 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

PreviousTechnical OverviewNextObjectives & Prerequisites

Last updated 1 year ago