Preboot execution environment (commonly known as PXE) is used to boot a device or virtual machine over a network. You can use PXE to achieve the following scenarios and this is used to remotely install a guest operating system over a network without needing the operating system installation media.
Hyper-V currently has two generations of VM hardware which are;
– Generation 1: These VMs have a legacy version of Hyper-V, and have a little bit of overhead when it comes to using PXE boot because it uses the legacy BIOS.
– Generation 2: Hyper-V machine is a UEFI-based VMs.
Note: A machine configured with UEFI will use bootx64wdsmgfw.efi on the WDS server when starting the boot. A legacy boot will use bootx64wdsnbp.com.
The generation of the Hyper-V virtual machine matters, because PXE uses different boot files depending on if the machine boots either using Legacy BIOS or UEFI. It is recommended to use Generation 2 VMs and if you do not feel the need to, this could be because you have not yet enabled UEFI in your environment.
See the link on why to choose Generation 1 or 2 http://bit.ly/379FwMz
Generation 2 VM Installation
– In the Installation Option
– Select Install an Operating System later
Click on Next or finish.
Note: When you click on next, it will show you the summary screen of the VM Installation, next click on finish Hardware configuration to support PXE
– Ensure you have your network at the top.
Ensure under Network Adapter
– Under Advanced features that the checkbox is selected for Protected Network (This absolutely depends on your environment need).
For how this is done on Generation 1 Hyper-V, see the link for how this is done https://techdirectarchive.com/2020/01/19/how-to-setup-a-vm-via-pxe-boot-on-a-generation-1-vm-hyper-v/
Note: Depending on your environment, you have to set a Static MAC address that will enable the VM search for the WDS server on the network.
Now connect to the VM
When this process completes, deployment success will be displayed as shown below.