@jhumpf There is no resolution to this. UEFI captured images can only function on uefi based computers. The same is true for BIOS captured images they can only function on bios based systems. The hardware is interfaced differerntly between the two. Most will just create two images, one for BIOS and one for UEFI systems which is MUCH cleaner and a MS supported solution.
@robertd Checkout the below image, this is how you password-protect the entire fog menu. This will accomplish what you’re after. Technicians need only to enter the key-combination in order to be prompted for user/pass credentials. The accepted credentials are those in the FOG web interface users area.
I’ve been thinking on this for a bit, and have thought of some far more complex ways to do it. I think that George’s below post is the best out of all the things I’ve thought of.
Basically have the post-install scripts write a .bat file on the local hdd with the needed arguments. Then make a snapin that runs a .bat file - and that just execute the local .bat file.
Just wanted to thank everyone for their suggestions( @george1421@Wayne-Workman). We did install LAPS on a test OU and it works perfectly. We’ll likely be rolling it out in the next week or two. For those machines off the domain, oh well…
Hmmm I have been making a lot of changes. I created a “Production” field in MySQL so that it doesn’t list non production images. I guess I need to go look at the original files. Thanks Tom!
Thanks for all the replies! Good information to have. I guess what I should probably be more concerned about is the fog server serving up the tftp boot file to every client as they reboot. I imagine at the start of the school year a lot of machines will be booting up at the same time, but only time will tell.
