![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Trying to enable WDS for our Hyper-V testing environment. VM's are spun up on this environment for development and testing purposes for our software and testing departments. We are trying to enable PXE booting so these users can reimage the VM's themselves and not have to go through the help desk to get the VM's erased and recreated when they have a new scenario and need a clean VM.
I have it setup perfectly from a WDS standpoint where they just network boot, select the image and everything is done via unattend files and they can get new clean VM in 30 minutes.
Issue: this requires the legacy network adapter apparently. Anyway around this? From a technical perspective, I understand whats different between the two adapters in Hyper V, but was hoping there was a way around this and not have to enable it on the VM's. I guess we can dual boot the VM's with one regular adapter and one legacy adapter so they can make use of PXE and just instruct them to disable the legacy network adapter (dont want it eating up DHCP addresses), but was hoping there was a way around this limitation.
This is Hyper V on Server 2008 R2.
I have it setup perfectly from a WDS standpoint where they just network boot, select the image and everything is done via unattend files and they can get new clean VM in 30 minutes.
Issue: this requires the legacy network adapter apparently. Anyway around this? From a technical perspective, I understand whats different between the two adapters in Hyper V, but was hoping there was a way around this and not have to enable it on the VM's. I guess we can dual boot the VM's with one regular adapter and one legacy adapter so they can make use of PXE and just instruct them to disable the legacy network adapter (dont want it eating up DHCP addresses), but was hoping there was a way around this limitation.
This is Hyper V on Server 2008 R2.