@PhilienTaylor I’m not sure what your question is here. Your end goal is not clear based on what you have posted.

FOG doesn’t support imaging over Torrent. FOG doesn’t support Secure boot. There is a tutorial on how you can create your own keys and then sign the boot files. This will require you to upload the certificates into each hardware. Or to go to microsoft and go through the process to get microsoft signed signing keys for what you want to boot on the target hardware. FOG doesn’t have any utlity for hypervisor environments. The FOG server can run as a vm client, but FOG has no relationship with virtualization.

@Warsonix Great you figured out how to switch to a different iPXE binary. You are welcome. Feel free to ask whatever issue you run into in a new topic.

@joanmarzo Laptop bios/firmware settings.

@tom-elliott I’m looking forwards to it! There’s a lot about FOG I don’t know yet and I’m just starting to dip my toes in.

@ice4192 Like this?
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

@wmw509 Disabling CSM makes sense. I’ve seen a lot of bioses that if CSM is enabled it only lets you use the legacy/bios pxe boot. I’ve had that disabled on all my hardware for so long I forgot it was a thing.

@brakcounty To get some more information, can you please schedule a debug deploy task (same as you would do a normal deploy task but just before you hit the last button in the web UI there is a check box for debug). Boot up the client as usual and let it boot up. Then you need to hit ENTER twice to get to the shell. Now type fog and ENTER again to start and step through all the process till you hit the error. It will throw you back to the shell. Now type:

sgdisk -gl /images/Win10Standard_GPT_EFI/d1.mbr /dev/sda

It surely will fail. Take a picture of the screen and post that here.

I realize this post is a bit old, but I wanted to thank everyone for their suggestions and give our experience to back up what has been said in this topic already. We experienced an image that should have been about 120gb, but was showing in FOG as the full 500GB hard drive. After referencing this thread, it fixed the issue. The steps we took are below in order:

Verified that the PC didn’t have a second drive or second large partition it was capturing
Verified that bitlocker encryption was OFF using the command prompt command “manage-bde -off C:”
Ran Disk Cleanup (to get rid of old unused files)
Ran Tools > Check to scan for hard drive errors (may require reboot to fix)
Ran Tools > Tools > Optimize and defagment
Capture Image again

Once we did those steps, the newly captured image only takes up the actual amount used on the hard drive.

dhcp general settings on LAN:

0_1542798476261_2368dc54-6215-4e93-855b-ada35d7e0f02-image.png

dhcp settings on other VLAN:

0_1542798558095_52779031-4102-4b2d-84c6-f1b69ab59a94-image.png

@jjsplitter Since you still had firewalld enabled, did you remember to set selinux to permissive? If not you will have a sad time when you try to capture an image.

Just cross-linking this here: https://forums.fogproject.org/topic/10615/ipxe-booting-possibly-broken-on-os-x-sierra-update

@Tom-Elliott this fixed the issue!

Thank you very much!

@craigcoulson said in Debian + svn = error:

nevermind all - i rebuilt the server with only minimal packages and re-ran the svn install of Fog and it worked fine - go figure.

Glad to hear you got it working 😉

@Tom-Elliott And you can’t calculate all the hours you’ve saved for other admins.

@fdrouard wol/wol.php path no longer exists.

@Sebastian-Roth said in Impossible to boot on PXE......:

Wireshark filter bootp && tftp is great for this

This has been in the wiki for some time, here:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_TFTP

Ok thanks so i will write a expect script to install fog automaticly

I have solved this thread because as @Junkhacker stated, this is fixed in the dev builds as I am not using gzip compression on the page at all any more. If you are worried about the display, please update to Dev.

@Omanimous said:

Changed Option 67 in DHCP to undionly.kkpxe and it seems to be working fine.

lol glad you got it working. I’m sure it will be fine.

In the future, when you have network booting issues, the boot file should always be your first thing to inspect and think about 🙂