Same boat here(kernel 6.6.7), not looking forward to switching to the WIE since it's so much larger as far as the boot files etc.
from section 3.1 of this article it seems there is indeed an issue with arguments getting passed to the loader, but there was a commit to supposedly fix it, I'm just not familiar enough with the compilation processes to know what to do with this info.
Same here on new machines, we are looking at the WIE (tests work as expected) as well, but compared to the LIE it's huge as far as PXE booting. I figure this is a Linux kernal issue, but just a guess.
@jakevirginia I know this is quite old, but just in case someone else has an issue, I'm going to guess this is a windows 11 image, I had the same issue couldn't even set the BIOS to the boot file manually, I ended up changing the image profile partition method from standard to "Use Original MBR/GPT" and that seemed to work.
Best I can guess is something with the UEFI partitions being recreated in a "not so standard" way?
@theopenem_admin Well, maybe I jumped the gun here I just tried it on a different computer and it appears to be working as expected (cache maybe?). I apologize for the premature support request, but I do appreciate your quick response!
I have setup a restricted user that I want to only be able to deploy images, I configured the ACLs and it mostly looks good, but they cannot create new on Demand Multicast sessions, when the screen loads it is blank like the other areas they do not have permission too.
Honestly I really like this idea, I used to do this with TRK (Trinity Rescue Kit), make a master machine, then use TRK to make a temp PXE boot, make the fresh machine the master, then it cloned it's drive to the other in the mcast session. Worked pretty good until EFI cam around.
Is there any way to import our CloneDeploy images into TOEMS?
I am trying to do this too, I am using proxy, I have modified the default files in the 3 folders under C:\Program Files\Theopenem\tftpboot\proxy (bios, efi32, efi64) but the changes do make any difference, even if I try to rename a label. Then I seemed to remember I needed to regenerate boot files, and that made no difference other than resting the default files back to default setting of 50
so on the replication, does that truly mean it copies the image file to both servers or is it just updating that it is available? I would like to have the image files stored just once but available to both com servers for cloning on either subnet.
If it is making multiple copies, would maybe a third server for SMB storage prevent that and accomplish one file for both?