@Fernando-Gietz that is absolutely not normal. i have no idea why it would be doing that.

@deepak727 “junk in compressed archive” you may want to verify the integrity of your files

@deepak727 have you tried the options here? https://forums.fogproject.org/topic/9606/trying-to-add-clonezilla-to-pxe-menu/10

@rwakc well, it would be technically possible to set up a method where you could be automatically imaging any device pxe booted from the network, and set up multiple dhcp scopes on different network ports, serving out different pxe boot files with embedded scripts. that way, you’d be able to choose what image the system gets imaged with by choosing what network you plug the device into.

@george1421 or, he could temporarily attach a keyboard

@TCS_Taylor files are no longer used the way they were in FOG 0.3x
ipxe can request the files over http instead of just tftp like pxelinux could, so we generate the boot information on demand using php.

@Benjamin_D you have been misinformed. the client can be used to schedule the capture task, but the system needs to reboot to begin pulling the image.
FOG is not typically used to capture systems that have been in use by users, but rather used to deploy a standardized image to systems.

@scgsg what are the specs of your server? have you tried capturing them in reverse order?

@Benjamin_D look into the location plugin. i think you should be able to do what you want to do, but i don’t think anyone has done it before.

@bertalanimre that doesn’t look correct. options 66 and 67 aren’t just things you have to enable, they’re configured. dnsmasq calls these options next-server and filename, i believe.
try adding this line to your config

dhcp-boot=undionly.kpxe,,<fog_server_IP>