Hi Guys,
I discovered that we have Windows Deployment services Running on our Domain and that it has Win Server 2008 R2 images on it. The current techy here has never used it but it appears set up correctly. I thought I would test it out by creating a VM and PXE booting it.
WDS is installed on a DC. The DHCP options (60,66) have been ticked.
On the Hyper-V machine I have installed the legacy adapter.
When I start the machine I see that it starts with the standard black screen with DHCP and the GUID.
It then fails to get a DHCP address and displays the standard “boot failure” message…
I tried to pre-stage the deployment by adding the NetBootGuid to an AD computer record and still not joy.
Am I missing something glaringly obvious?
2 Spice ups
ewillie
(E_Willie)
2
I am stating something obvious here but is the WDS Service started? I beat my head against my desk for a while until i realized ours was off for some reason.
1 Spice up
Hi,
Make sure that the “Legacy Network Adapter” that you just added and specify that it should use the Virtual Switch as “Bridged” from the dropdown list.And 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.
I had a similar problem and the way that I found that worked for me was using DHCP options 66 and 67. I basically followed most of the instructions found here, Windows Server 2012 - WDS - Deploying Windows 8 - Part 1 | PeteNetLive , without any problems. The only difference is that mine is running Windows Server 2012, as are the instructions.
