I remember having some issues with 3000s on Windows PE at my last job. If I recall I had to drop to the command line and assign the IP address manually. I'm not sure if that helps you at all or how you would do that on the Linux bootloader.
I do know the Linux bootloader sometimes works with secure boot but on some machines you need to turn it off while imaging. You could try turning off RAID as well and use AHCI.
Nevermind. It was an issue with the WIM not mounting when it was running the script on my laptop. A restart seemed to have fixed it. Sorry for wasting your time.
@theopenem_admin
Any reason it would just drop when starting wpeinit? I'm only using the 64bit ISO. It should work with the Windows 11 ADK right? This is all I'm getting after it loads:
I rebuilt the WIE(with the updated 2.0.2 tool) and updated my PXE boot settings. The WIM boots but it tries to start wpeinit then it just drops out to the command line. It does this if I PXE or boot off USB. The file size is also much smaller than the old one and it didn't take very long to create. I'm wondering if something is off with the new version? I'm using the latest Windows 11 ADK.
I'm also using the extra drivers in the optional folder if that makes any difference. Any assistance would be appreciated since now I can't image machines at all. 
@theopenem_admin Thanks for considering my ideas! My thought on the remote access link on the computer page is so if there is something you need to do manually in mass(IE: a computer lab) you could just remote in and out of them easily. I get your point of view though, it opens a can of worms as to what everyone wants on that page.
Coming from SCCM originally, OpenEM is a great solution for imaging and management. Its an amazing solution for a free product and I'd like to say hats off the the developer(s). More and more I find myself using it to push programs and scripts to solve problems.
I have a few suggestions though! I don't know if they are possible but here they are:
An option to use the remote access option and wake on LAN from the computer list page without needing to click on them individually.
The ability to search for computers using the serial number
A force toec checkin option for all active machines
An option to re-push out a oncepercomputer policy without needing to make changes to it.
A way to run policies on demand instead of just modules.
An option to select a computer or multiple computers and run CMD or powershell commands for testing or one time installs without needing to make a policy/module.
Keep up the great work with this product! Thanks for reading my thoughts!
@theopenem_admin Ah that is handy info! I might be able to just push a registry fix rather than reimaging the 120 desktops I have than. Your a lifesaver!
@theopenem_admin
That worked great thank you so much! I worked around it but there seems there is another issue you may want to be aware of.
The C:\drivers registry option in the Toec sysprep utility on Win 11 works great for all the system drivers but it bungles up something with printers. It makes the installation of the Xerox Global print driver impossible, and it errors out with this error.
Unable to find a core driver package that is required by the printer driver
I'm not sure everything that option does but I changed the Devicepath key in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion back to just "%SystemRoot%\inf" and it still doesn't work.
@theopenem_admin The Linux environment works fine yes. The problem it doesn't work as smoothly for deployment because of the need to change boot settings for secure boot.