I did create the Boot Files after...
Assuming we just wanted to do it with the Boot Files ISO and not PXE...

I have done the below with another platform Will not mention here to not have others bail from this Great Product.

So I think I just have a syntax issue with TheOpenEm.
Assuming I copy the appropriate files to the correct folders..

kernel http://x.x.x.x/iso/pcunlocker/wimboot
initrd http://x.x.x.x/iso/pcunlocker/bootmgr.efi
initrd http://x.x.x.x/iso/pcunlocker/Boot/BCD bcd
initrd http://x.x.x.x/iso/pcunlocker/Boot/boot.sdi boot.sdi
initrd http://x.x.x.x/iso/pcunlocker/sources/boot.wim boot.wim
boot

NEW Entry with TheOpenEm
IF I create a folder called "pcunlocker" in this case...

kernel pcunlocker/wimboot
initrd pcunlocker/bootmgr.efi
initrd pcunlocker/Boot/BCD bcd
initrd pcunlocker/Boot/boot.sdi boot.sdi
initrd pcunlocker/sources/boot.wim boot.wim
boot

Hope that is clear as mud. I appreciate the feedback.

As a follow up, I noticed the system does create the Database Entry for the Custom Menu Entry, but sometimes does not update the files in the pxelinux.cfg folder. So possibly the system reads one but not the other. It may be my ignorance as to how the custom entry works. Basic goal is to boot an ISO using PXE. Possibly this is a bug who knows.

Hello - I wanted to create a pxe booted ISO from the Custom Boot Entry. Was hoping someone could point out the steps. I basically copied the Current Menu Option..
kernel http://ipofmyopenemserver/fileIwantToBoot

Getting "error: can't find command kernel.
Thank You!

I did create the Boot Files after...
Assuming we just wanted to do it with the Boot Files ISO and not PXE...

I have done the below with another platform Will not mention here to not have others bail from this Great Product.

So I think I just have a syntax issue with TheOpenEm.
Assuming I copy the appropriate files to the correct folders..

kernel http://x.x.x.x/iso/pcunlocker/wimboot
initrd http://x.x.x.x/iso/pcunlocker/bootmgr.efi
initrd http://x.x.x.x/iso/pcunlocker/Boot/BCD bcd
initrd http://x.x.x.x/iso/pcunlocker/Boot/boot.sdi boot.sdi
initrd http://x.x.x.x/iso/pcunlocker/sources/boot.wim boot.wim
boot

NEW Entry with TheOpenEm
IF I create a folder called "pcunlocker" in this case...

kernel pcunlocker/wimboot
initrd pcunlocker/bootmgr.efi
initrd pcunlocker/Boot/BCD bcd
initrd pcunlocker/Boot/boot.sdi boot.sdi
initrd pcunlocker/sources/boot.wim boot.wim
boot

Hope that is clear as mud. I appreciate the feedback.

Well hopefully the Dev will respond, I am seeing some PXE issues in general or ignorance to how it is setup. Likely there are a few bugs, and or issues with newer chipsets.

One option I have been successful with on newer hardware, is to set the Network Stack in Bios to "Legacy" vs "EFI" if its available. Then I can do the cloning successfully, and then after the clone it boots EFI etc since the Image is EFI of the machine in question.

Not sure if your Units have that option in Bios, but if they do it sometimes works because of the different Stack Software load, it can work with Older Kernels etc.

Hoping we can all get TheOpenEm to work, as it is very slick for the most part, I think its just early on.

You tried all the Boot Options - ipxe_efi64 and grub and winpe_efi64?
If I boot to a VM thru PXE or USB I could not get anything to work until I switched to GRUB for 64 bit efi...
I had some Intel NUC's that were very new with new chipsets so it was all ticked off, until I set the NUC to ipxe_efi64 etc. Anyhow could be totally not your issue, but hoping it might help you out.

As a follow up, I noticed the system does create the Database Entry for the Custom Menu Entry, but sometimes does not update the files in the pxelinux.cfg folder. So possibly the system reads one but not the other. It may be my ignorance as to how the custom entry works. Basic goal is to boot an ISO using PXE. Possibly this is a bug who knows.

May not be what you want but will change the wallpaper on boot.
https://www.techwalla.com/articles/how-to-change-desktop-wallpaper-for-all-users

Hello - I wanted to create a pxe booted ISO from the Custom Boot Entry. Was hoping someone could point out the steps. I basically copied the Current Menu Option..
kernel http://ipofmyopenemserver/fileIwantToBoot

Getting "error: can't find command kernel.
Thank You!

Just punting, but did you try Admin Settings->Kernels->5.11.10x64->Download
Then Update your PXE boot Menus to that Kernel? (Seems they all default to the 5.10 version so change each time and hit update.

Answering my own question here in case someone needs.
Admin Settings->Kernel Downloads
Click Download Kernel of latest version (5.11.10) in my case.
The AWESOME TheOpenEm will automagically Install the kernel.
Click Admin Settings->PXE Boot Menu
Ensure ipxe_efi is selected for both on EFI
Click Global Boot Menu
Set the New Kernel to each of the Bios, EFI64
Actions->Create Boot Files
System will take you to PXE Settings to update those.
Actions->Update
Should boot right in.

Hello - FANTASTIC PRODUCT! I setup the PXE Boot for 64 Bit EFI and works, but I have a 10th Gen Intel NUC that boots and downloads the NBP File and says "NBP File Downloaded Successfully" and then it just sits at that screen.

Tried older Kernel and winpxe etc and same result.
Anyone have a suggestion?