Comparison of Iventoy and IPXE Manager.

[crasadure]

https://www.tnctr.com/topic/1262906-ipxe...http-boot/
https://github.com/abdullah-erturk/iPXE-Manager

Download Link : https://github.com/abdullah-erturk/iPXE-...s/main.zip

[mephistooo2]

A demo has been added.

Try accessing the control panel through your browser instead of downloading it to your computer — password: admin · No actual files are uploaded — it's a simulation.

erturk-dev.netlify.app/ipxe_demo.html

[jpzsj]

测试了一下，完全没有iventoy方便，iventoy可以装在nas里面，而iPXE-Manager需要一台windows电脑作为服务器

[mephistooo2]

测试了一下，完全没有iventoy方便，iventoy可以装在nas里面，而iPXE-Manager需要一台windows电脑作为服务器

Comparing iPXE Manager to iVentoy is a bit like comparing apples to oranges — they target different goals.

iVentoy boots ISOs as-is. It's easy to use, but for Windows, it only gets you to the WinPE environment. It cannot perform a real network installation.

iPXE Manager runs Windows Setup over WebDAV as a genuine network installation — completed entirely over the network, without USB or DVD. iVentoy cannot do this.

On the Linux side, both tools offer similar distro support. On the Windows side, nothing else in the free/open category does what iPXE Manager does.

Being "Windows only" is not a limitation — the target audience is system administrators working in Windows environments. If you need a PXE server running on Linux, you would naturally look at different tools for that.

v2 was also released.

[longpanda]

测试了一下，完全没有iventoy方便，iventoy可以装在nas里面，而iPXE-Manager需要一台windows电脑作为服务器

Comparing iPXE Manager to iVentoy is a bit like comparing apples to oranges — they target different goals.

iVentoy boots ISOs as-is. It's easy to use, but for Windows, it only gets you to the WinPE environment. It cannot perform a real network installation.

iPXE Manager runs Windows Setup over WebDAV as a genuine network installation — completed entirely over the network, without USB or DVD. iVentoy cannot do this.

On the Linux side, both tools offer similar distro support. On the Windows side, nothing else in the free/open category does what iPXE Manager does.

Being "Windows only" is not a limitation — the target audience is system administrators working in Windows environments. If you need a PXE server running on Linux, you would naturally look at different tools for that.

v2 was also released.

Just a correction:
For Windows, iVentoy will mount the remote ISO file as a local Y: driver through httpdisk, and take user's  unattend XML script (if provided) to do a fully auto unattened network installation.

[mephistooo2]

测试了一下，完全没有iventoy方便，iventoy可以装在nas里面，而iPXE-Manager需要一台windows电脑作为服务器

Comparing iPXE Manager to iVentoy is a bit like comparing apples to oranges — they target different goals.

iVentoy boots ISOs as-is. It's easy to use, but for Windows, it only gets you to the WinPE environment. It cannot perform a real network installation.

iPXE Manager runs Windows Setup over WebDAV as a genuine network installation — completed entirely over the network, without USB or DVD. iVentoy cannot do this.

On the Linux side, both tools offer similar distro support. On the Windows side, nothing else in the free/open category does what iPXE Manager does.

Being "Windows only" is not a limitation — the target audience is system administrators working in Windows environments. If you need a PXE server running on Linux, you would naturally look at different tools for that.

v2 was also released.

Just a correction:
For Windows, iVentoy will mount the remote ISO file as a local Y: driver through httpdisk, and take user's  unattend XML script (if provided) to do a fully auto unattened network installation.

A friendly suggestion.

You can use the same method in iVentoy that IPXE Manager uses to mount Windows ISOs and modified WinPE ISOs to virtual drives.

I think this method is very robust.

[crasadure]

iPXE Manager v2.1

v2.1 Changelog
This update was primarily introduced to resolve mounting issues encountered with modified WinPE ISOs (such as Sergei Strelec). Since these ISOs use a non-standard volume layout, the previous Get-DiskImage-based approach was not always reliable.
• If the existing

Code:

mnt_temp

folder is present before mounting, it is deleted and recreated to prevent issues caused by stale or corrupted mount points.
• The ISO mounting method has been completely migrated from the Get-DiskImage / Add-PartitionAccessPath approach to a DiskPart-based method. Before and after mounting, volume lists obtained via

Code:

diskpart list volume

are compared to identify the newly mounted UDF/DVD-ROM volume without a drive letter, which is then attached to the folder using the

Code:

diskpart assign mount=

command.
• The mount wait time has been increased from 1000 ms to 2000 ms, providing additional time for the mounting process to complete on slower systems.
• The additional PowerShell sweep code in the

Code:

_unmount_all_isos()

function has been removed. Since

Code:

_unmount_iso()

already unmounts each ISO individually and correctly, the extra cleanup step had become unnecessary.

[crasadure]

v2.2 Changes:

• Added support for direct PXE boot (HTTP Boot) over a network to Linux-based system recovery, disk cloning, and maintenance tools (ISO) such as Rescuezilla, Redo Rescue, SystemRescue, and Parted Magic.