I finally solved this using the WOL broadcast plugin. Steps:
Created WOL broadcast with the public ip of the site where those computers are
On the router from the second site added static arp for private ip 10.148.17.254 to mac ff:ff:ff:ff:ff:ff (broadcast)
On the same router forwarded port 9 udp to 10.148.17.254
You can mark this as solved. Thank you!
For others: The remote site has computers with activated and working wake on lan and the router configured for DHCP with next server the IP of the FOG server and filename undionly.kpxe (for legacy BIOS boot).
@rmishra1004 is this happening on all hosts or just this one? Have you tried hitting the ‘reset host encryption keys’ on the host in the webgui?
If you copy past the url that fails, what happens? I believe you should see an error message like this
I don’t see the file, I have tested it on my desktop and I do see it should I just transfer the file to the VM. Also,
This statement confuses me a bit. We are still talking about usb booting into ipxe right? The file is on the fog server in the /tftpboot directory. Its called ipxe.efi. If the /tftpboot directory is not there you can search for the file with sudo find / -name ipxe.efi But it should be in the /tftpboot directory.
@george1421 Thanks for the response. I think I might’ve actually figured it out. If you Legacy PXE boot, it errors out on a UEFI based machine. However, if you use the Network Stack PXE boot (UEFI), it will correctly boot. The DVD does work for both UEFI and Legacy. I don’t know why I didn’t think to try that first.
@mpatel as others have mentioned here - speed is the key; we’re in an identical situation, all sites connect to HQ via VPN but then all sites have Gig Internet so imaging machines at the remote sites has never been an issue, you just talk the end user over the phone to his F12 and that’s that (FOG job must be submitted ahead of time of course).
Well you have a few things in you need to think about.
Moving netboot services to the FOG server. This is pretty easy enough to do. You change the dhcp options 66 and 67 to point to your FOG server from your current netboot server. I do have a tutorial on how to setup FOG as a netboot server here: https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images This system uses FOG to create the custom iPXE menu entries to boot into your linix distro’s live installer environment. You may have to tweak the kernel parameters to load your installer seed file. The nfs disk structure and preseed file organization is up to you since netbooting is not a supported feature of FOG, but a hack using the FOG infrastructure for netbooting.
Once you have your netboot installer for linux configured then you can focus on the windows bits.