You need to implement a networking solution that ensures that all of the virtual machines use PXE to boot when they connect to Windows Deployment Server (WDS)

You have a server named Host1 that runs Windows Server 2012 and has the Hyper-V server role
installed.
Host1 has one physical network adapter. You plan to deploy 15 virtual machines on Host1.
You need to implement a networking solution that ensures that all of the virtual machines use PXE to
boot when they connect to Windows Deployment Server (WDS).
What should you do?

You have a server named Host1 that runs Windows Server 2012 and has the Hyper-V server role
installed.
Host1 has one physical network adapter. You plan to deploy 15 virtual machines on Host1.
You need to implement a networking solution that ensures that all of the virtual machines use PXE to
boot when they connect to Windows Deployment Server (WDS).
What should you do?

A.
Install legacy network adapters for each virtual machine.

B.
Modify the settings of the virtual switch.

C.
Modify the settings of the network adapter for each virtual machine.

D.
Install a second physical network adapter.

Explanation:
Since Windows Server 2012 R2 (WS2012 R2) Hyper-V and Windows 8.1 Client Hyper-V, there are two
generations of virtual machine hardware specification. Generation 1 virtual machines (the only
generation on legacy versions of Hyper-V) make things a little tricky when it comes to PXE booting. The
default (and better performing) synthetic Network Adapter (that leverages the Hyper-V integration
components) does not support booting off of the network in Generation 1 virtual machines. If you do
want to boot this type of virtual hardware using PXE then you must add an emulated Legacy Network
Adapter.
Boot a Hyper-V Virtual Machine Using PXE
https://www.petri.com/boot-hyper-v-virtual-machine-using-pxe



Leave a Reply 0

Your email address will not be published. Required fields are marked *