@george1421 No I want to be able to reimage a computer if we need to from any location but make it to where we can be the only ones that can connect to the fog server. We have Lenovo Thinkcentre Tiny PC’s for most of the computers.

@george1421 so I did some more research and I wonder if it’s not technically booting the fog server but only throwing an error because of secure boot being enabled. The issue I’m going to run into is disabling secure boot on 400 computers in our company because it can’t be done remotely. Would it be easier to set up fog to do secure boot instead?

@george1421 should I use a different boot file then? I’m currently using ipxe.efi for the dhcp option.

@george1421 I could maybe start with disabling the secure boot and see what happens after that.

@george1421 they run into a secure boot error which i’m needing to turn off on our machines if we are not currently using it. I did change the timeout for the main menu so that I could work on some testing for it. Do i need to change the main menu timeout back to 5 seconds so it will continue booting to the hard drive. This issue mostly happens when someone restarts their computer.

I’m able to get pxe boot working with our FOG server but have noticed that random computers are booting to it even though their hard drive is fine to boot from and the boot priority is set that the network boot is not the first in the list. I do have DHCP option 66 and 67 enabled on our DHCP server. I’m wanting to set it up in a way so that our IT department is the only ones that can have a computer boot to that server for imaging purposes. There maybe a setting i’m missing on our server or we need to reconfigure all of our computers in the bios.