HOTSPOT
Your network contains two servers named Server1 and Server2 that run Windows Server 2012 R2. Server1
has the Hyper-V server role installed. Server2 has the Windows Deployment Services server role installed.
On Server1, you have a virtual machine named VM1.
You plan to deploy an image to VM1 by using Windows Deployment Services (WDS).
You need to ensure that VM1 can connect to Server1 by using PXE.
Which settings should you configure on VM1? To answer, select the appropriate settings in the answer area.
Hot Area:
Answer: 
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 “Standard Network Adapter” installed on the Virtual Machine, but for PXE functionality
you will need to add a “Legacy Network Adapter”.
Go to the “Legacy Network Adapter” 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 “Legacy Network Adapter”. Just select the “Legacy Network Adapter” 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.http://technet.microsoft.com/en-us/library/cc726550%28v=WS.10%29.aspx