@brakcounty Well done!!

Where I also see value in this is if someone wanted to hard drive boot into iPXE then from iPXE into the hard drive or FOG without using PXE booting. Instead of a usb drive, everything could happen off the efi partition on the local hard drive. It would not solve the secure boot part of it, but its an option.

Also lets say someone wanted to setup a preboot menu (such as for dual booting) using refind. Your idea could be tweaked slightly to boot into refind menu manager and then pick to boot windows, linux or something else from the refind menu. There are a number of options this method opens up. Again, well done!

Hi,

i have FOG 1.5.0 running on an ESX Host and a Storage Node on a bare metal machine.
Works like a charm since years.

Best Regards X23

@danboid said in Restore BIOS W10 image onto UEFI machine:

First, why is there so little content on the FOG wiki FAQ page?

Would you be keen to help work on the documentation?

@george1421 I just tested it out on a PC outside of our IT vlan with success. I hard coded it already, but I have a habit of not disclosing our IP addresses even if they’re private. I get the Press ESC to show the menu option for one second, then it boots to the hard drive. Now I took the modified bootx64.efi from my usb drive and copied it to the Windows EFI partition, replacing the existing one (renamed the old to bootx64.efi.bak), made sure that the UEFI is pointing to the file, and now the PC boots the fog process without USB.

@george1421 well, I am excited to say that it is working. I literally just readded what was already added, and re-tested. Could have been gremlins or lack of sleep, whatever the case, I am about to capture my image, and do a test deploy. I will ping you back shortly and you can close this as solved I do believe.

Thank you so much for the assistance. Ping me anytime you need a tester.

@danboid said in Linux mdraid RAID-10 with FOG?:

software RAID built into the Linux kernel

These are the words I was looking for to give a direction. mdraid can be used for more than just the intel fake raid as you referenced previously.

Yes FOS linux (the engine that interacts with the target computer to capture and deploy images) can interact with a software raid.

the same rules for FOG imaging as with clonezilla. If the software raid doesn’t exist you must create it before you can image it. You could test to see if it exists in a FOG post init script, If your deployment mode is download then you could create a bash script to create the array. Post init scripts are executed just after the FOS OS inits and before any imaging begins. The tutorial you referenced before lays out all of the bits you need, just in this case you are not setting up the intel fake raid configuration.

@sebastian-roth it’s working thank you !!

@pep Any news on this?

@sebastian-roth 1.5.9. What is also strange about how FOG behaves across subnets is the USB boot method. I’ve explained in another post about how booting from USB on the same subnet and/or same switch stack on my floor will not prompt me to enter the tftp server but booting from a completely different vlan or subnet physically outside of our own network will prompt for it. See this line in the ipxescript:

:setserv echo -n Please enter tftp server: && read next-server && goto netboot || goto setserv

I tried changing it to and this time it configures net0 then does nothing and the PC returned to it’s own (Dell) boot menu:

:setserv set next-server 10.x.x.x && goto netboot || goto serserv

I know this is off OP but it seems related to different subnet behavior in FOG.

@jmeyer Having a FOG server with a dual nic is a standard and supported configuration for installing FOG.

There are a few things you need to know/do before installing FOG.

Know the linux kernel names of your network interfaces. You can see this by using the following command ip a s Identify the name of your business network interface and your imaging network interface. Document these names. Make sure your imaging network interface is configured for a static IP address. FOG does not like having the imaging network interface IP address changing once FOG is installed. Make sure your business network interface has a default route defined so that it can get to the internet. Confirm that your fog server has internet access. Make sure your imaging network interface does not have a default route defined.

Now use the git method to download the installer files onto your FOG server.

Install FOG. During the installation process you will be prompted for the linux name of your imaging network interface. Key that in when requested. You will also be prompted to if you want to install a dhcp server. Answer yes to this. The fog installer will only bind the dhcp server to the imaging network interface leaving your business network interface alone during the installation of FOG. There will be no conflicts on the business side since fog will only focus on the interface you said that is your imaging network.

@brakcounty said in Can a FOG Server setup as a Storage Node serve tftp files?:

I could always do a mysqldump export and import from the primary fog server to the secondary right?

Sure thing!

@yeet See if the bios has a setting called mac passthru or something similar. That will passthru the built in mac address of the mobile device to make the network adapter generic and the computer unique.

Doesn’t secure boot use unique keys? Have you been able to boot with secure boot enabled on machines that you deployed the image to?

@george1421 The USB ipxe boot method works perfectly, from a USB drive. The idea is to somehow make that ipxe process boot BEFORE Windows on the hard drive itself instead of the usb drive, and have a countdown to boot from first hardrive. This way I can set a deploy or capture task remotely and it would work. As for specifying the IP address, I already did. Ipxe sees the FOG server on the same vlan, but on a different vlan ipxe asks for the FOG server address.

@sebastian-roth I need to get back into those docs. Things have been just so crazy lately. When you have something working let me know and we’ll get it documented.

@sebastian-roth I already try snappin on Windows and it’s working. The client is install with the last version and my fog version is 1.5.9.
I tried to use Fog’s snappin on debian host but and it’s going well but I think that my command are not good. i tried with dpkg -i and /bin/bash. The client is downloading and rebooting the PC but I can’t find the program

463e11a5-6457-4538-a9ab-7b062651629a-image.png

@turtle331 I would like to get a solution for the installer error 😕

@brakcounty I don’t have access to my production fog server at the moment, but I’m wondering if the history table keeps track of “deploy image” imaging…

This bit probably won’t help you retrospectively, but in my environment we don’t register the target computers with FOG, we use the “Deploy image” route. We do use MDT to build our golden image though. In MDT we have a task sequence that creates a registry key with the build date the golden image is created because we typically rebuild our golden image once a quarter. With a PS query we can query AD and the target computers to find out the unique build date of all of the deployed images. In a way we could back into the number you are seeking.

So the question for you is… is there something unique that would identify the target computer as being deployed by FOG? Some unique software or registry setting that would say this image was built by our golden image deployment environment?

From a FOG perspective, once you deploy an image via the “Deploy image” iPXE menu FOG forgets the target computer ever existed. The question in my mind is of the history table keeps any lingering memories of the target computer’s mac address or such.