Hi,
I'm running WDS on Server 2008R2 SP1. It's on the same subnet as my Microsoft DHCP server and Domain Controller. I'm attempting to build a UEFI virtual machine. When it pxe boots it gets an IP address, connects to the WDS server and downloads
wdsmgfw.efi. It then tries to contact the WDS server for a couple minutes and ends with the message "Windows Deployment Services encountered an error:" Error Code:0x102 as shown below...Image may be NSFW.
Clik here to view.
Looking at a network trace on the WDs server while the client is trying to contact the WDS server I see repeated DHCP requests to port 4011 immediately followed by the WDS server contacting the domain controller as though it's looking for permission to start the build process or something. My client IP is 192.168.2.5, the WDS server IP is 192.168.2.10, and the domain controller's IP is 192.168.2.3.
The trace is shown below...
Image may be NSFW.
Clik here to view.
My DHCP options include 66 (IP of wds server), 67 (boot\x64\wdsmgfw.efi), and 003 (IP of gateway/router). The wdsmgfw.efi file came from a Windows 2012R2 boot.wim. I've also tried eliminating options 66 and 67 but then the client won't download the wdsmgfw.efi file. If I set option 60 to PXEClient it won't download the wdsmgfw.efi file either.
WDS is configured to respond to all client computers (known or unknown).
WDS is configured to respond to not join computers to the domain.
WDS is configured to respond to not listen on port 67 - although I've tried listening without success as well.
WDS is configured as authorized in DHCP - although I've tried unathorized without success as well.
I can build non-uefi servers just fine.
If I use a WDS server running on Windows 2012R2 I can build just fine but I really don't want to upgrade all my WDS servers if I don't have to.
Does anyone have any ideas what is going on here? Why would my WDS server be reaching out to my domain controller instead of just presenting my boot images? Any help would be much appreciated.
Thanks
