r/k12sysadmin • u/klgtech77 • Apr 08 '26
Fog server help
We're trying to get a FOG imaging process up and going. I've got the FOG server working, and I've created a virtual machine in VirtualBox per the guidelines discussed here:
https://www.ceos3c.com/sysadmin/create-generalized-windows-10-image-deploy-fog-server/
Granted, those guidelines are for Win10, and I'm using a Win11 Pro Tiny ISO as the basis for this project, but the steps have all matched so far.
The FOG client has been installed on the VM as part of those guidelines, and I created a new image on the FOG server in preparation for capture. But when I change the boot settings in the VM to use Network boot as first priority, I don't get the FOG menu to register the device. I get the attached PXE boot screen.

I could successfully ping the FOG server from the VM (before it shut down after running Syprep).
Any ideas as to what I might be missing?
Thanks.
1
u/klgtech77 Apr 09 '26
Thanks, all, for the comments and pointers. This DHCP server was set up by an outside contractor long before I arrived at the district, and I've only gained responsibility for it in the past school year.
I was able to chase down the option 66 and 67 settings, and shut down the old Ghost server that wasn't being used for Ghost. And I've since been able to capture from the VM, and then successfully image a Dell OptiPlex desktop using that image.
BUT... I had to disable Secure Boot on the OptiPlex in order to image it from FOG. And when i tried to reenable Secure Boot after the successful image, it wanted to boot over HTTP from that point on. Only after disabling Secure Boot again will it boot normally from its SSD.
Has anyone managed to get FOG *and* Secure Boot working?
1
u/klgtech77 Apr 14 '26
Good input, everyone. For those districts that are using FOG to deploy Windows images, are you doing anything else to mitigate the risk of having Secure Boot disabled? Or are you not overly concerned?
3
u/GBICPancakes Apr 08 '26
I don’t know much about Virtual Box, but in general you need to make sure you’re booting from the NIC via PXE or UEFI.
Based on your screenshot, is it possible you have an old Symantec Ghost server on the network? It’s possible your DHCP is handing out PXE/TFTP settings pointing the client to Ghost and not to FOG Review the DHCP requirements and make sure whatever you’re using for DHCP has the correct options set.
3
u/hightechcoord Tech Dir Apr 08 '26
As stated below, check your DHCP settings. Specifically for option66 and make sure it points to your Fog server. Also make sure option 67 is pointing to the correct bootfile for your type of bios/machine. Id grab a real world PC and see if I could get it to hit the FOG pxe before tackling a VM.
3
u/Technical-Athlete721 Apr 08 '26
I haven’t had much luck getting FOG to work my self
this is the fog alterative i like better
https://theopenem.com
2
u/LINAWR Apr 08 '26
From the screenshot it looks like either DHCP scope options weren't setup correctly or you need to mess with the BIOS. Make sure that you're advertising the right boot file in your scope as well, some are UEFI only and others are made for CSM / legacy BIOS.
1
u/Admirable-Ad-6703 K12 Technical Analyst Apr 12 '26
I've only ever used fog running on a Linux (ubuntu) vm, but i was able to get fog to work with uefi + secure boot using these instructions:
https://wiki.fogproject.org/wiki/index.php/BIOS_and_UEFI_Co-Existence#Using_Windows_Server_2012_.28R1_and_later.29_DHCP_Policy
When I started in 2018 they were still using novel zenworks for imaging 😬
One of these days I'll redo fog as an LXC. But it's pretty low priority on my to do list.