Correct Answer:
Explanation/Reference:
Explanation:
Virtual machines can be deployed to Hyper-V using Windows Deployment Services (WDS). To accomplish this requires the proper WDS infrastructure be in place and that the VM PXE boot using a Legacy Network Adapter.
By default, there is only a gStandard Network Adapterh installed on the Virtual Machine, but for PXE functionality you will need to add a gLegacy Network Adapterh.
Go to the gLegacy Network Adapterh that you just added and specify that it should use the Virtual Switch that you just created.
Last but not least, you should change the BIOS boot priority to make sure that the Virtual Machine always tries to boot first using the gLegacy Network Adapterh. Just select the gLegacy Network Adapterh and move it to the top using the buttons.
Start your Virtual Machine and now PXE boot should work.
The Pre-Boot Execution Environment (PXE) provider for Windows Deployment Services provides client boot services over the network. It registers itself with the WDS Server service (the main server-side service of the Windows Deployment Services solution) and requests a remote procedure call (RPC) endpoint.
After the Windows Deployment Services server role is installed, you must configure the server by using either the Windows Deployment Services MMC snap-in or the /Initialize-Server command-line option. The PXE provider must be configured properly before it can provide client boot services over the network.
References:
http://technet.microsoft.com/en-us/library/cc726550%28v=WS.10%29.aspx
