Change Log
Changes from 2.5.0.0 to 2.7.0.0
All communication is now HTTPS between the iPXE boot loader and the 2PXE server, regardless of HTTP state of the DP.
HTTPS DP’s and NTLM DP’s are now supported, no need for anonymous access configured on the DP.
Change from using DHCP option 252 to 175
Pure PowerShell setup got revamped to work again with HTTPS communication
iPXE -> 2PXE TFTP communication methods are no longer supported, use HTTPS instead
Change to work with subordinate CA servers in Configuration Manager integration
The use of Windows boot loaders is discontinued
Minor bug fixes
Changes from 2.2.0.0 to 2.5.0.0
Improvement to performance
Filter abilities to Configuration Manager TS deployments
Updated boot screen
WIM File injection - No need to modify the boot image
TFTP Server
Supports option to bind to single IP for multi NIC machines
Allows to link to single port for TFTP transfers
Registry Detection – No need to restart service when Configuration Manager changes configuration
iPXE WinPE Client – Now included and shipped as part of 2PXE installer
Custom Variable injection – Task Sequence runs as part of variable creation
Improved Web Service integration
WimBoot WinPE loader:
Ability to inject files into RAM held WinPE image
Bug fixes
iPXE Network Boot Program Changes:
Included Syslog Client
TLS Updates to support IIS
Added Certificate commands for iPXE
Updated to latest build at time of compiling
Bug fixes for Realtek NIC’s
Added and updated logging options for troubleshooting.
Added infrastructure support for UEFI 2.5 and above based systems
Last updated