@george1421 I am very embarrassed to be typing this, but I believe I’ve figured out the issue. When I go to create a VM in VMWare Workstation 16, I have two options of “Typical” which uses Easy Install and does most of the installation in the background, as well as “Custom” install, where I choose all of the settings manually.

I also have several different ISO versions of Windows 10, including “Windows 10 (Version 1809)”, “Windows 10 (Version 20H2”, and “Windows 10 (Enterprise Editions)”. Both “Windows 10 (Version 1809)” and “Windows 10 (Version 20H2)” are 64-bit while “Windows 10 (Enterprise Edition)” is 32-bit

Now when I was creating a new VM just about an hour ago to do some more testing, I was using both “Easy Install” and the “Windows 10 (Enterprise Edition)” ISO, which Easy Install listed just as “Windows 10”, while using “Windows 10 (Version 20H2)”, Easy Install says “Windows 10 x64”

After seeing this, I continued with creating the “Windows 10 (Enterprise Edition)” VM and once again, I couldn’t get it to PXE-Boot, also correlating to Wireshark detecting a 32-bit OS. However, when I went to create a “Windows 10 (Version 20H2)” and/or a “Windows 10 (Version 1809)” VM, it would PXE-Boot no problem at all, so I believe the issue was with the actual ISO and is now resolved!

Thanks so much for your help!

@thecount1829 @george1421 here is also my uploaded Wireshark Capure

output.pcap

@george1421 Sorry for the late reply!

I have just renamed my “ipxe.efi” to “ipxe.sav” and than rebooted the FOG Server to make sure the changes were applied, and the strange thing is that the virtual machines are still booting to FOG without an issue:

@george1421 So, some great news and some (still good but not great news) The VM that wasn’t PXE Booting now is after adding the “i386-efi/ipxe.efi”, but I am now getting this error instead, and once again only on this VM

@george1421 Thanks!
You’re 100% correct! iPXE.efi and a folder called “i386” are in the “tftpboot” directory!

@george1421 Thanks!

Just to confirm, is the “i386/” need to be included in the “UEFI32” filename?

@george1421

Thanks for the reply! All VMs are on the same /24 subnet. I did have a Server 2016 DHCP server that was handling DHCP before, but that has since been turned off, although it’s not entirely erased from the disk. I’ll give that a shot tonight!

@sebastian-roth Thanks for the reply!

All VMs are set to the same - UEFI with “Secure Boot” turned off. However, I did notice that if I change them to “BIOS” and than change the BIOS filename on PFSense to kdionly.pxe, they boot every time

Hey everyone!

About six months ago, I setup a FOG Server Virtual Machine for deploying images to my other virtual machnes.

For the past month, I’ve noticed that if I create a new Virtual Machine and try to PXE-Boot off of my network, sometimes it works and connects to the FOG Server without any issues, but other times when it PXE Boots, it grabs an IP address and says “Downloading NBP File” but it than automatically goes back to the boot menu, with subsequent attempts saying “Downloading NBP File…” for half a second and than going back to the boot menu

I’ve looked at the differences between the VMs that can PXE Boot and the ones that can’t and the only differences are the amount of RAM and the size of the HDD/SSD, everything else is exactly the same.

Here is my following network setup:
PFSense - Router & DHCP Server | Network Booting is enabled and points to my Ubuntu VM, which hosts FOG
The default BIOS filename I’m using is “ipxe.efi” as all my virtual machines are set to UEFI

Ubuntu - FOG Project Server | Hosts the FOG Project

Server 2019 - Domain Controller | My Domain Controller for my environment

I’ve also attached a video demonstrating the “Downloading NBP File” issue as well.

If anyone has any suggestions, please feel free to respond!

Please note that during the “Page Swipe”, I shut down the VM and than turned it back on

Video Link - https://i.imgur.com/tJfQ0AM.mp4