Problems with PXE Boot (BIOS/UEFI) with Windows Hyper-V VM
-
@george1421 said in Problems with PXE Boot (BIOS/UEFI) with Windows Hyper-V VM:
My initial reaction is that you have 2 dhcp servers on your network.
I agree with George.
-
@CMTprj Maybe that Hyper-V network adapter is set to NAT instead of bridged. If not then follow Georg’s great post.
-
We are currently using the undionly.kkpxe file instead of undionly.kpxe to boot Hyper-V Gen1 /bios VMs. This file is also working correctly for the physical hardware that we have tried it on so far.
-
Thank you for the help. I used Wireshark and found my rogue DHCP server. Turned out to be an AudioCodes SIP Appliance that was recently added to our network. I have that disabled and now when my Hyper-V GEN1 virtual machine boots it is asking for the TFTP server ip address.
This is not the behavior I want… When I do type in the address if times out
-
@cmtprj If iPXE asks for a tftp server then your dhcp server isn’t filling out the pxe boot request correctly. You need to have the next-server and boot-file fields set correctly in the dhcp offer header.
What device is your dhcp server?
-
I am using a Windows 2016 server for my DHCP services.
-
@cmtprj if you can, is it possible to get a pcap of the exact communications where you need to key in the tftp IP address? There is something going on there that we need to understand.
-
I am in doing a training for my Company tomorrow then heading out for vacation. Let me catch up with you when I return next week.
-
@CMTprj Any news on this?
-
Sorry for the late response. I have not solved the issue but I also need to get some other items finished. I believe the root cause in this situation is not FOG but SCCM getting in the way. I might not have time to circle back to this until next month. I am leaving for our Florida office in a few days to help with things down there and attending Microsoft Ignite that last week of the month.
