Hello everyone,
Trying to deploy WDS on a virtual lab with Hyper-V (Running on a Windows 10 1803 17314 host).
I finish my configuration on a VM server which runs WDS and DHCP at the same time (also a domain controller, DNS), which we will call192.168.0.1 (Windows Server 2012 R2 Standard Build 9600).
I set the scope options of 60, 66 and 67 as usually mentioned when you are running both services in the same computer:
![]()
Problem is, I don't have this so called "wdsmgfw.efi" file in my boot base of the WDS files, the only .efi file I have there its called bootmgfw.efi, which doesn't do anything if declared on that option. I
tried almost all boot files, including .com BIOS files on that folder and files on x86 folder, but obviously didn't worked as well, since Gen 2 machines works with UEFI.
What happens when I boot a VM Gen2 machine alternating between those files:
wdsmgfw.efi: It says that the file weighs 0 bytes (as this file doesn't exist) and returns error PXE-E23: TFTP error from server. restarting the boot process.
bootmgfw.efi: It returns a error screen saying that failed to start, a recent hardware or software change might be the cause with the code: 0xc000000f: The Boot configuration Data for your PC is missing or contains errors.
wdsbnp.com (any .com files): It says that the file has X bytes, downloading the NBP file, successfully downloaded NBP file and restart the boot proccess.
If I don't declare any file on Option 67, he tries the default wdsmgfw.efifor the error above.
Right now, if I choose the wdsnbp.com file and try to boot on a Gen 1 machine, it works normally, I can access the boot files of WDS Server. But since I'm deploying Windows 10 images in this scenario, I need a solution that will apply to Gen 2 machines.
Last year (on build 1709 of Windows 10 maybe) I was able to successfuly do this lab with no issues, and deployed a Windows 10 Client Customized Image to my clients on network, which was Gen 2 machines as well, but I don't remember now what am I doing wrong,
or if something is different on Hyper-V running on this build 1803 of my host.
Any suggestions?
Edit¹: Tried with the Secure boot disabled and enabled which doesn't do any difference on scenarios above.