@george1421 thanks for the reply buddy. I understand, it’s Friday, so my Google-Fu ix non-existent

I think I understand what you mean, and I was actually generally curious about that as well.
I as able to get that same image captured using “undionly.pxe”. The image was a Win 11 Pro (UEFI/GPT) image, and I was curious if it would apply correctly in this manner, but I’m gathering that as long as the target PC’s firmware matches with the “captured” image’s is, it should work (correct me if I’m wrong).

To make matter more interesting, ALL of those computers I need to image don’t even have Ethernet ports or NICs. I don’t even really want to “fool” with wireless PXE stuff (would take an eternity with their image). Their “fix” was to get docking stations, but crazily enough, Lenovo apparently makes docking stations for laptops without Ethernet ports, which I had personally never seen before until now.

So yeah, I think I may end up just doing this the “traditional” way (not to mention, I didn’t see an option within the BIOS of the Lenovo laptops’ to boot into “BIOS/Legacy”).

I really appreciate you guys and all that you do. It’s been years, but on the bright side, I have a working FOG server that I can use to image for future projects. I sure have missed this tinkering/collaboration. As always, thank you!

I am attempting to capture a Win 11 Pro image using VirtualBox.
I had some issues with the bit always dirtying itself regardless of what I tried, but I got around that using the “chkdsk” tactic, for lack of a better term.

I now have a Golden Image, and I’m able to “capture” it to the FOG server when using “undiononly.kpxe”.

I have now built a UEFI image that I would like to capture, but I can’t get either ipxe.efi or snponly.efi to work. When I attempt to use ipxe.efi, I get an “Exec format error”. When I attempted to use “snponly.efi” (which is what I’ve seen recommended), I get the following:<br> </br>

Any help is appreciated.

@youzersef I was remote to the physical host, but it seemed more like a blue screen in comparison to just “hanging”.

Anyways, I reinstalled FOG and cloned “stable” instead of “master” and got around that issue.

I’m going to make another post for another issue I’m facing with UEFI (would have updated sooner, but forms have been down).

Hello,
I used FOG years ago and was able to get it working fairly easily.
I recently attempted to re-deploy a FOG server, as I recently have acquired the need to image a lot of PCs for a local hospital.

Long story short, I have FOG installed and working completely normally from what I can tell.
The issue I’m having occurs when I’m actually attempting to capture the image from the VirtualBox VM (just a simple, Win 11 Pro image).

I’m able to completely register the host, create the task, etc., with no errors.
When I attempt to network boot for a second time (after host registration), it begins to attempt to capture the image, but it always crashes. The weird part is, it’s not the VM crashing, it’s actually resetting the physical host that the VM is on.

I looked around and couldn’t find anything like this in the forums. Do you guys have any ideas on this? I can provide any necessary logs, better descriptions, etc.

Thanks in advance, FOG is an extremely amazing project!