@Critchleyb Did you come to a conclusion with this or got a little further with the commands and ideas provided?

I tired options ‘Windows 10’ as well as ‘other’. None of them worked. I even tired DD method for cloning it showed the same errors.

@pa_fog_man I think we have a bit of confusion here (and the 390 is not helping with clarification). First let me say that the Dell’s will let you dynamically boot in the other mode without changing the firmware (where it gets its default value). You can do this dynamic switching from the F12 boot menu. The other issue with the 390s (I can’t speak for personal experience with the 390s, but we have 790s in our fleet) the 790s were the first generation to support UEFI mode. But as far as I know, the 790s don’t support pxe booting in uefi mode. The 7010s was the first generation to support pxe booting in uefi mode. To pxe boot on the 7010s you would have to enable the uefi network stack on the network adapter settings in the bios. Otherwise you would not get ipv4 and ipv6 entries under uefi on the F12 boot menu. Back on point. You MUST select the proper boot kernel for the target system bios mode (legacy/bios or UEFI). If you sent the wrong boot file to the system you will not see the FOG iPXE boot menu. for bios mode you can use ipxe.pxe or undionly.kpxe for uefi mode you can use ipxe.efi or snponly.efi The bold text above are the typical kernels to set for dhcp option 67. You can not mix the boot kernels. This isn’t a FOG issue, but rather a firmware one.

Couple of things to check: Is the original machine in BIOS or UEFI mode? Is the target machine in BIOS or UEFI mode? If both are in UEFI mode, you may have to manually add the boot option in the UEFI of the target machine.

@p4cm4n also, tried cmd and batch from sfx archives, specifically 7zip sfx maker which threw an error trying to run on my own machine and winrar sfx maker. Rar is crappier compression but oh well. One of those worked can’t remember which…but things like wifi configs using it didnt.

Not necessarily the same problem, but I had to work around a certificate error by adding this to my setupcomplete.cmd file that is run after Windows Installs: certutil -delstore "Root" "FOG Server CA" certutil -delstore "Root" "FOG Project" certutil -addstore "Root" "%windir%\System32\Sysprep\fog.ca.cer" certutil -addstore "Root" "%windir%\System32\Sysprep\ca.cert.der" And of course add the certificate files to the folder referenced above.

well, what i needed was the french keyboard for the registration/capture/deploy. I followed Quazz advice (General settings / keymap : azerty) and all is good now ! thanks :)

@reese I am having the same issue. How did you safely downgrade back to 1.4.4. I had no issues there but can’t image an entire lab anymore. Just locks up. Hints on the downgrade process would be appreciated!

@jmg74 said in dell optiplex 3050 avec windows 10 UEFI: @verdierr : have you tried different options in your host config in Fog website, about “Host Bios/EFI Exit Type” ? [FR : As-tu tenté différentes options, pour ton hôte (via le site web de FOG), concernant “Host Bios/EFI Exit Type” ?] we tried every possible combination but none worked. for option 60, we have legacy computers and to try the uefi, we saw on the web that you have to activate option 60?

Has there been any progress with this issue. I am having the issue where the “_” flashes but goes no further and I have been searching for a solution for the past 3 days. In my case, I am attempting to boot a WinPE Environment to run a 3rd party application. I tried both clean boot.wim files from Win7 and Win10, both fail. But when booted from a USB Drive or CD the application boots. Everything worked perfectly when I was running 1.5.0 but no longer in 1.5.4. Dell PowerEdge 910 Windows Server 2016 DHCP ** Option 66 - IP of CentOS 7 Server Running Fog ** Option 67 - undionly.kpxe DNS Hyper-V ** CentOS 7 ** Fog 1.5.4 ** 16 Cores ** 128GB Ram It will sit here forever.

One other possible solution is Veeam Backup Agent (free). This will do a full system backup with bare metal restore. You can back up to a NAS, Veeam B&R Server ($$), or other network storage device. If you have a system failure, you boot from the linux boot cdrom, connect to your storage device and then restore your system. This is one way to protect your fog server. There may be native (Ubuntu) options like Bacula too.

there isn’t anything there yet: anthony@fogserver2:/opt$ ls 1.5.4.tar.gz fogproject-1.5.4

@kermit1991 Do you see this issue on all your clients or just when using an USB ethernet adapter? Have you tried using the ethernet adapter together with different clients. Sometimes adapters and client’s BIOS/UEFI firmware just don’t play together well enough. On the other hand some USB ethernet adapters just don’t play nicely altogether. It’s a long process to figure out what exactly the issue is. So start by telling us more about the exact USB adapter you have and make/model of PC/laptop you use.

@vince-villarreal this is the purpose of the persistent groups plugin. When a host is added, the new host will get whatever the template host has defined. This, to my knowledge, only happens when a new host is added. If you add a host to the group, then later edit the host itself, it should retain the new changes regardless of the template, until you remove and readd the host to the group.

Just for notice, I’m using Fog 1.5.4 normally with ubuntu 16.04 and this function is working fine. Both this option you mentioned and the option to go in the option “power management” work the same. Best regards, Igor.

I started doing that which is what led me to the remi yum repo setup and the binary file download. At this point I think I am just going to attempt to hack it up so that it will work offline and then later see if I can add a switch to the installation file for an offline mode that checks for the dependencies.

@tthurston said in Unable to boot to Fog to capture image UEFI: We were able to get past this stage. From my understanding this is not the case. In the picture you posted first we see a client booting up going straight into a task (probably because one was scheduled for this ethernet adapter’s MAC address) instead of showing the FOG menu. It hangs at this stage. Now you switched to a different ethernet adapter (new MAC address) and get the FOG menu. Now when you select the inventory it tries to go ahead bit possibly hangs just at the very same stage where FOS (FOG OS, essentially a Linux kernel) is loaded. Again, please tell us the exact model an make of computers and ethernet adapters you have. Please try using the adapter you had when taking the first picture and add debug loglevel=7 to the host kernel parameters for this client (see that you have the correct host entry with that MAC address we see in the picture). Then boot up the client. If that does not show more information on screen we might provide a kernel with CONFIG_EARLY_PRINTK enabled to see if we can get any printout from the kernel at all. By the way, which version of FOG do you use?

I can’t see your screen shot, but I had a problem with a similar error message yesterday. Turns out it was because I had moved my image folder and missed one of the configs you have to change. Searching the forum should being up numerous other threads with that error message, I’d try some of those fixes. Philip

@salginer The partition layout looks pretty straight forward. Is your Windows partition bitlocker encrypted? Run manage-bde -status C: in a admin command shell.