Problems with PXE Boot (BIOS/UEFI) with Windows Hyper-V VM

[CMTprj]

FOG Server

• FOG Version: 1.44 (6077) running on Kubuntu 16.04.3 LTS
  Static IP: 192.168.20.251

DHCP Server

• Windows 2016 (patches up to date)
  Static IP: 192.168.20.208
  Option 66 = 192.168.20.251
  Option 67 = undionly.kpxe

Client

Windows 2016 Hyper-V Host
New Virtual Machine (Gen1 - using Microsoft defaults)
DHCP

Description

My company has an SCCM setup that is 2-3 years old and we want to move away from SCCM to FOG for our imaging. I have disabled PXE on the SCCM server.

I have setup a new server and successfully have FOG installed and running. I need some assistance in setting up the PXE Booting for both BOIS and UEFI. I want to work on BIOS first. Once I have this correctly completed I will work on UEFI.

I thought I had everything correctly created but my VM will not successfully boot with a BIOS based PXE boot. See screen shots.

Thank you for your help

[Wayne Workman]

is 192.168.0.1 your fog server IP? have you updated your DHCP option 66 and 67 to point to the fog server? Have you looked through these articles:
https://wiki.fogproject.org/wiki/index.php?title=Modifying_existing_DHCP_server_to_work_with_FOG
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

[CMTprj]

Thank you for the quick reply - I have reviewed these documents and confirmed that my fog server is 192.168.20.251 and have the options 66 set to 192.168.20.251
Here are a few screen shots of my FOG settings. I set the static IP prior to the FOG install and am running defaults at this point.

[george1421]

My initial reaction is that you have 2 dhcp servers on your network.

If your fog server, dhcp server, and pxe booting client are on the same subnet, we can use the FOG server to eavesdrop on the pxe booting process to tell us what is going on.

Please follow these instructions: https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue

Upload the pcap to a google drive or drop box and post the link here. If you don’t want to post the link in a public forum, send me an IM and we’ll take a look at it. The captured file will tell us the actors in your pxe booting play.

[Wayne Workman]

@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.

[Sebastian Roth]

@CMTprj Maybe that Hyper-V network adapter is set to NAT instead of bridged. If not then follow Georg’s great post.

[jschoffstall]

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.

[CMTprj]

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

[george1421]

@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?

[CMTprj]

I am using a Windows 2016 server for my DHCP services.

[george1421]

@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.

[CMTprj]

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.

[Sebastian Roth]

@CMTprj Any news on this?

[CMTprj]

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.