Hyper-V Gen2 & PXE Boot

[CHiLL]

My Google-Fu and fixes have let me down.

 

I've just built a more powerful machine for my workstation, with the aim that I can use virtualisation on it for testing with VMs. I've installed Hyper-V and created a VM template...however, I cannot get it to PXE boot from our SCCM server. I get the "Start PXE over IPv4" message, though it times out and takes me to a page that says:

 

Microsoft Hyper-V UEFI

 

Virtual Machine Boot Summary

 

1. Network adapter

A boot image was not found.

 

2. SCSI Disk (0,0)

The boot load did not load an operating system.

 

No operating system was loaded. Your virtual machine may be configured incorrectly. Exit and reconfigure your VM or click restart to retry the current boot sequence again.

 

The main causes for this that I've found are:

 

• Make sure network is the first boot order - it is
  
• SCCM/WDS isn't configured for UEFI - it is, as we can PXE boot other UEFI secure boot devices
  
• Create an external vSwitch and use "Allow management operating system to share this network adapter" - I have and it did the same thing
  
• Gen2 only supports x64 - We are only using x64
  
• Use Gen1 instead - I'd rather use Gen2 if possible!
  

 

My knowledge of Hyper-V is quite limited, as most of my experience is with VMware. Any assistance would be appreciated!

Edited April 6, 2023 by CHiLL

[ThatBoringBloke]

You will need to install a Legacy Network Adapter for the VM to PXE boot. Not sure if these are available in Gen2 VM's.

[CHiLL]

I do get the "Start PXE over IPv4" message, though it times out and takes me to a default Windows cannot load an OS menu. It seems similar bhaviour to a device not getting an IP address. Actually, looking at the Networking tab, no IP address has been assigned and I'm getting the same behaviour on both the Default Switch and the External Switch I created.

 

Edit: I deleted and new external vSwitch and created it again. Now it's working, no idea why!

Edited April 6, 2023 by CHiLL

[Aprice]

I do get the "Start PXE over IPv4" message, though it times out and takes me to a default Windows cannot load an OS menu. It seems similar bhaviour to a device not getting an IP address. Actually, looking at the Networking tab, no IP address has been assigned and I'm getting the same behaviour on both the Default Switch and the External Switch I created.

 

Edit: I deleted and new external vSwitch and created it again. Now it's working, no idea why!

 

Might be worth adding the MAC address to the SCCM duplicate Hardware IDs,

 

https://www.systemcenterdudes.com/sccm-duplicate-hardware-identifiers/

[FN-GM]

I had no issues with this. I didn't have to inject any drivers or legacy adapters.

 

However, I had to configure the MAC address on the VM to be static and not dynamically assigned. It kept changing causing headaches!