Vista - Hyper-V and PXE Requests

I have a domain environment setup. Within the environment I have two
separate servers.
Server 1: DHCP Server
Server 2: Hyper-V Server with WDS

They DHCP Server is successfully able to connect to the Hyper-V server via
the SCVMM Admin Console. Virtual Machines running on the Hyper-V server are
also able to receive an IP Address from the DHCP Server and have access to
the network.

The problem that I am having is that the virtual machines are not able to
PXE boot. They are able to receive an IP Address from the DHCP Server but
that is about it. Eventually an message is returned saying: "Boot failure.
Reboot and Select proper Boot device or Insert Boot Media in selected Boot
device"

The virtual machine IS configured to use an Emulated NIC. This is verified
becuase when the virtual machine tries to start it attempts to get a PXE
response as would normally be the case if this were not a virtual environment.

Also, the DHCP server is configured to respond to both PXE and DHCP
responses. The DHCP server also has the below options set:
* Option 60 - PXEClient
* Option 66 - 192.168.0.5 (I have also used the FQDN)
* Option 67 - boot\x86\wdsnbt.com

Within WDS on the Hyper-V server I have the option checked to "Authorize
this Windows Deployment Services server in DHCP" under the DHCP Authorization
section of the Advanced tab.

I also have a simple WinPE image added to the "Boot Images" of the WDS
server. Why am I not able to PXE boot?

Any assistance is greatly appreciated.

Thank you.

Perhaps I misunderstood your terminology, but you need to have a Legacy
Network Adapter installed in your VM.

--
Ryan Sokolowski
MVP - Clustering
MCT, MCITP x3, MCTS x8, MCSE x2, CCNA, CCDA, BCFP


"Edwin" <Edwin@xxxxxx> wrote in message
news:4C594942-CC65-4BBD-A249-EDC47E708852@xxxxxx

Yes. You are correct. There was a difference in terminology.

In other words I am NOT using the Synthetic Network Adapter for the VM. I
am using the Legacy Network Adapter for the VM.

Thank you.

"Ryan Sokolowski [MVP]" <ryan@xxxxxx> wrote in message
newsE7BCF7D-9BEA-4790-ADC8-3E0E64939FEA@xxxxxx