djn6022
asked on
Server 2012 R2 WDS Windows 10 UEFI
Hello,
I had WDS working fine with Win 8.1 x46 in legacy but I am now looking to deploy Win 10 with UEFI. I cannot get it to go. The client says PXE-E16 no offer received. I have a boot file there pulled from the Win 10 ISO. I also created a capture image. I ran wireshark and can see the DHCP packets going to my DHCP server and the WDS server. Let me know what from wireshark would be helpful to post. I see UDP 4011 traffic between the client and my WDS box too. My setup:
-AD Integrated WDS server running 2012 R2
-DHCP on a different box (one of my domain controllers)
-My bench and both of the above servers are on the same VLAN
-I do not have DHCP options set nor ip helpers as I have never needed them in the past and most everything I have read regarding UEFI says I do not need them.
TIA
I had WDS working fine with Win 8.1 x46 in legacy but I am now looking to deploy Win 10 with UEFI. I cannot get it to go. The client says PXE-E16 no offer received. I have a boot file there pulled from the Win 10 ISO. I also created a capture image. I ran wireshark and can see the DHCP packets going to my DHCP server and the WDS server. Let me know what from wireshark would be helpful to post. I see UDP 4011 traffic between the client and my WDS box too. My setup:
-AD Integrated WDS server running 2012 R2
-DHCP on a different box (one of my domain controllers)
-My bench and both of the above servers are on the same VLAN
-I do not have DHCP options set nor ip helpers as I have never needed them in the past and most everything I have read regarding UEFI says I do not need them.
TIA
Check error logs for WDS and other services and see if you have something there.
Sometimes, it's related to access permission on the required PXE NBP file for the the service running PXE Server. Especially if your Win10 nodes are set to use x64 version of the OS and it is the first time you deploy some x64 OS, there may be a problem of permission and/or access there.
I did not check yet but win10 deployment may also require its own NBP.
Yet I guess that your error may be related to UEFI implementation of PXE.
If you can, modify the client's BIOS settings and see if you can use "PXE LEgacy mode" and if this solves your issue when you have only your first WDS server.
Also, check for a BIOS/UEFI upgrade for your client nodes since this could be a problem of UEFI-PXE implementation.
Regarding dhcp options, you must NOT set them except for Option 60 set to "PXEClient" in case your DHCP and PXE server runs on the same box. Check my article and its comments for more details:
https://www.experts-exchange.com/articles/2978/PXEClient-dhcp-option-60-what-is-it-for-Can-I-use-PXE-without-it.html
It is strange to me that you can see traffic on UDP 4011 if you do not have DHCP Option 60 set to "PXEClient". If so, this could be an implementation problem in UEFI/PXE. What kind of client nodes are you using?
Sometimes, it's related to access permission on the required PXE NBP file for the the service running PXE Server. Especially if your Win10 nodes are set to use x64 version of the OS and it is the first time you deploy some x64 OS, there may be a problem of permission and/or access there.
I did not check yet but win10 deployment may also require its own NBP.
Yet I guess that your error may be related to UEFI implementation of PXE.
If you can, modify the client's BIOS settings and see if you can use "PXE LEgacy mode" and if this solves your issue when you have only your first WDS server.
Also, check for a BIOS/UEFI upgrade for your client nodes since this could be a problem of UEFI-PXE implementation.
Regarding dhcp options, you must NOT set them except for Option 60 set to "PXEClient" in case your DHCP and PXE server runs on the same box. Check my article and its comments for more details:
https://www.experts-exchange.com/articles/2978/PXEClient-dhcp-option-60-what-is-it-for-Can-I-use-PXE-without-it.html
It is strange to me that you can see traffic on UDP 4011 if you do not have DHCP Option 60 set to "PXEClient". If so, this could be an implementation problem in UEFI/PXE. What kind of client nodes are you using?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The issue revolved around WDS and not DHCP options like the gentleman was asking about.
ASKER
Can anyone shed light on this?