Hello,
I have successfully setup Windows Deployment Services with MDT 2013 in the past in a lab environment in VMware. However, I am working on deploying this at the office now and am having a difficult time getting UEFI Devices to boot into WDS.
I can successfully PXE Boot to BIOS with no issues if I modify the Scope Options.
DHCP Server and WDS are on the same VLAN, but separate servers. The client devices are on a separate VLAN from the servers.
I’ve spent a few days troubleshooting, reading articles, and can not figure out why this is not working. I have tried from multiple UEFI only machines. Any help would be appreciated. Below is an example configuration on how everything is setup.
Configuration
Layer 3 Switch
- VLAN 22 «Server VLAN»
- VLAN 33 «WDS Client VLAN»
interface Vlan22
description Servers
ip address 192.168.22.1 255.255.255.0
no ip redirects
no ip unreachables
ip route-cache same-interface
ip route-cache policy
no ip mroute-cache
load-interval 30
!
interface Vlan33
description PXE-BOOT-WDS-CLIENTS
ip address 192.168.33.1 255.255.255.0
ip helper-address 192.168.22.15 «Primary DHCP Server»
ip helper-address 192.168.22.25 «Secondary DHCP Server»
ip helper-address 192.168.22.150 «WDS Server»
no ip redirects
no ip unreachables
ip route-cache same-interface
ip route-cache policy
no ip mroute-cache
load-interval 30
ip forward-protocol udp 4011
ip forward-protocol udp 66
ip forward-protocol udp 60
Layer 2 Switch — Ports Trunked to Layer 3 Switch
interface GigabitEthernet0/1
description WDS Client Port
switchport access vlan 33
switchport mode access
logging event trunk-status
logging event bundle-status
logging event spanning-tree
logging event status
load-interval 30
spanning-tree portfast
spanning-tree bpduguard enable
Servers
- DC1.DOMAIN.COM «DHCP» 192.168.22.15
- DC2.DOMAIN.COM «DHCP» 192.168.22.25
- WDS.DOMAIN.COM «WDS Server 192.168.22.150»
DHCP Scopes
- VLAN 22 — No Scopes «Vlan 22 Static IP’s Only — Servers»
- VLAN 33
VLAN 33 Scope Options
- 003 Router — 192.168.33.1
- 006 DNS Servers — 192.168.22.15, 192.168.22.25
- 015 DNS Domain Name — DOMAIN.COM
- 044 WINS/NBNS Servers — 192.168.22.15, 192.168.22.25
- 060 PXEClient — PXEClient
- 066 Boot Server Host Name — 192.168.22.150 — WDS Server
- 067 — Bootfile Name — bootx64wdsmgfw.efi
Client Device
Microsoft Surface Pro 3
Windows Deployment Services
Error Code: 0x102
#1
moob
-
- Members
-
- 12 posts
Newbie
-
Switzerland
Posted 26 May 2015 — 09:05 AM
I’ve got a WDS 2012 and a DHCP Server 2012 running on the same subnet.
My WDS 2012 has been deploying Windows 8.1 x64 without any issues, using DHCP Options 66 and 67.
PXE-Boot works fine with BIOS Computers and bootfile name bootx64wdsnbp.com
Now I am trying to deploy Windows 8.1 x64 to HP Computers with UEFI.
In order to be able to boot my UEFI-Client from LAN I changed DHCP Option 67 bootfile name to bootx64wdsmgfw.efi.
When the UEFI Client tries to boot from LAN, it loads wdsmgfw.efi, then it says «Contacting Server (IP-Address of WDS)» for some minutes and then it stops with error message 0x102.
Windows Deployment Services encountered an error:
Error Code: 0x102
I’ve been fiddling about with default.bcd but no avail. I guess I am missing something here, but I don’t know what it is.
Option 60 does not seem to be an option, because dhcp and wds are on dedicated servers.
As soon as I switch back to BIOS and wdsnbp.com everything works again.
- Back to top
#2
erwan.l
erwan.l
-
-
Developer
-
- 3041 posts
Platinum Member
- Location:Nantes — France
-
France
Posted 26 May 2015 — 10:11 AM
I’ve got a WDS 2012 and a DHCP Server 2012 running on the same subnet.
My WDS 2012 has been deploying Windows 8.1 x64 without any issues, using DHCP Options 66 and 67.
PXE-Boot works fine with BIOS Computers and bootfile name bootx64wdsnbp.com
Now I am trying to deploy Windows 8.1 x64 to HP Computers with UEFI.
In order to be able to boot my UEFI-Client from LAN I changed DHCP Option 67 bootfile name to bootx64wdsmgfw.efi.
When the UEFI Client tries to boot from LAN, it loads wdsmgfw.efi, then it says «Contacting Server (IP-Address of WDS)» for some minutes and then it stops with error message 0x102.
Windows Deployment Services encountered an error:
Error Code: 0x102I’ve been fiddling about with default.bcd but no avail. I guess I am missing something here, but I don’t know what it is.
Option 60 does not seem to be an option, because dhcp and wds are on dedicated servers.
As soon as I switch back to BIOS and wdsnbp.com everything works again.
Hi,
Sorry to insist on option 60.
I have read elsewhere that this option 60=PXEClient makes a difference when using wds+efi.
Do you mean you cannot alter this option or you did, and it had no (positive) impact.
Regards,
Erwan
- Back to top
#3
moob
moob
-
- Members
-
- 12 posts
Newbie
-
Switzerland
Posted 26 May 2015 — 11:19 AM
Hi
I could add and alter this option, but with option 60 set to PXEClient my client would not even find the bootfile.
I also read that «The DHCP server must not include server option 060 if PXE and DHCP reside on separate servers.»
- Back to top
#4
erwan.l
erwan.l
-
-
Developer
-
- 3041 posts
Platinum Member
- Location:Nantes — France
-
France
Posted 26 May 2015 — 11:56 AM
Error 0x102 more or less means ‘server unavailable’ which is not very helpful as it can mean several things :
-your (efi) client, once it has loaded the wds firmware, has no more network connectivity
-your server (which works fine in bios mode) denies the requests coming from you efi client
A wireshark capture will help you understand what happens (both for a bios and efi run).
Looking at the server logs could also help asserting one of the scenarios above.
- Back to top
#5
Tripredacus
Tripredacus
-
-
Expert
-
- 234 posts
Frequent Member
- Interests:K-Mart-ian Legend
-
United States
Posted 27 May 2015 — 02:42 PM
Oh you posted this on Technet as well. As I post there (and here) is that Server 2012 can figure out what boot rom to use automatically and you don’t need to change it.
- Back to top
#6
moob
moob
-
- Members
-
- 12 posts
Newbie
-
Switzerland
Posted 29 May 2015 — 03:15 PM
I ran a wireshark scan and as far as I can tell the wds server just does not respond to requests coming from the efi client. I’m clueless.
- Back to top
#7
Tripredacus
Tripredacus
-
-
Expert
-
- 234 posts
Frequent Member
- Interests:K-Mart-ian Legend
-
United States
Posted 29 May 2015 — 03:29 PM
Remove Option 67 from the DHCP Server.
- Back to top
#8
moob
moob
-
- Members
-
- 12 posts
Newbie
-
Switzerland
Posted 01 June 2015 — 12:27 PM
Without option 67 there are:
BIOS: PXE-E53 No bootfile name received
UEFI: PXE-E18 Server response timeout
- Back to top
#9
Tripredacus
Tripredacus
-
-
Expert
-
- 234 posts
Frequent Member
- Interests:K-Mart-ian Legend
-
United States
Posted 01 June 2015 — 03:57 PM
moob reported this fixed by removing options and using «ip helpers» … which is something I also never did. So many different ways you can configure a network, sometimes difficult to get the right fix for people. 
Topic here:
https://social.techn…=w8itproinstall
Edited by Tripredacus, 01 June 2015 — 03:58 PM.
- Back to top
#10
erwan.l
erwan.l
-
-
Developer
-
- 3041 posts
Platinum Member
- Location:Nantes — France
-
France
Posted 01 June 2015 — 06:48 PM
moob reported this fixed by removing options and using «ip helpers» … which is something I also never did. So many different ways you can configure a network, sometimes difficult to get the right fix for people.
Topic here:
https://social.techn…=w8itproinstall
If he need to remove ip helpers it means the dhcp request was caught by a layer 3 switch and sent onto another vlan.
Surprising since he mentionned that it all sits on the same subnet?
- Back to top
#11
moob
moob
-
- Members
-
- 12 posts
Newbie
-
Switzerland
Posted 02 June 2015 — 06:29 AM
Solved: Removed dhcp options 66 and 67 and added ip helper address pointing to wds. thank you guys!
- Back to top
#12
erwan.l
erwan.l
-
-
Developer
-
- 3041 posts
Platinum Member
- Location:Nantes — France
-
France
Posted 02 June 2015 — 06:37 AM
Solved: Removed dhcp options 66 and 67 and added ip helper address pointing to wds. thank you guys!
you mean you modified your layer 3 switch/router (where the ip helper is setup) to point to wds pointing an another vlan/subnet?
- Back to top
#13
moob
moob
-
- Members
-
- 12 posts
Newbie
-
Switzerland
Posted 02 June 2015 — 06:44 AM
Yes sir. Previously we had an ip helper configured on the switch, pointing to dhcp. Now there are 2 ip helpers (ip relay address), one pointing to dhcp, one pointing to wds. But I also had to remove the dhcp options.
- Back to top
#14
erwan.l
erwan.l
-
-
Developer
-
- 3041 posts
Platinum Member
- Location:Nantes — France
-
France
Posted 02 June 2015 — 06:52 AM
Yes sir. Previously we had an ip helper configured on the switch, pointing to dhcp. Now there are 2 ip helpers (ip relay address), one pointing to dhcp, one pointing to wds. But I also had to remove the dhcp options.
ok makes sense.
i was confused as you initially reported your wds and dhcp were on the same subnet.
i had not thought that your clients could be on another vlan.
usually if you go for opton 66/67, you have to fill in option 60 as well.
or the alternative is to go for «plain» dhcp options, i.e not use option 66/67 (and therefore option 60).
I have the feeling that you could probably leave option 66/67 if you updated option 60 to «PXEClient».
- Back to top
#15
moob
moob
-
- Members
-
- 12 posts
Newbie
-
Switzerland
Posted 02 June 2015 — 07:13 AM
ok makes sense.
i was confused as you initially reported your wds and dhcp were on the same subnet.
i had not thought that your clients could be on another vlan.
usually if you go for opton 66/67, you have to fill in option 60 as well.
or the alternative is to go for «plain» dhcp options, i.e not use option 66/67 (and therefore option 60).
I have the feeling that you could probably leave option 66/67 if you updated option 60 to «PXEClient».
Yeah, sorry, should have pointed out that clients are on a different vlan.
Edited by moob, 02 June 2015 — 07:14 AM.
- Back to top
#16
moob
moob
-
- Members
-
- 12 posts
Newbie
-
Switzerland
Posted 08 June 2015 — 06:41 AM
for 2 days it worked fine without dhcp options and with additional ip relay address pointing to wds. suddenly, pxe boot stopped working: clients would not get ip addresses any longer from dhcp. we then removed the ip helper pointing to wds and re-enabled dhcp-options.
- Back to top
#17
moob
moob
-
- Members
-
- 12 posts
Newbie
-
Switzerland
Posted 16 June 2015 — 05:48 AM
once again. yesterday it worked without dhcp options and with 2 ip helpers in place, one pointing to wds, the other one pointing to dhcp.
this morning: error pxe-e53 (bios) pxe-e16 (uefi)
I don’t get it. I guess I’ll set up a dhcp server on my wds box…
- Back to top
Hi,
I’ve been reading a lot on these forums the last couple of weeks, mostly regarding SCCM etc, but at the moment I’ve got an issue I haven’t been able to wrap my head around.
We’re using a standard win 2k8 r2 domain environment. This environment used to contain a server with MDT 2010 and WDS 2008 (server 2008 r2), used for deploying win7 etc, the environment used to work pretty well.
Then somebody thought it was a good idea to buy some tablet computers, to be specific the HP Elitepad 900. Specs for this tablet computer indicate it is able to do PXE boot (there is an ethernet port on the docking), but due to limitations this only works using UEFI (BIOS not supported). After a lot of reading I found that wds 2008 does not support x86 uefi, so the server was upgraded (no fresh install) to windows server 2012 (with wds 2012) and mdt 2012 update 1.
Legacy computers are still able to PXE boot correctly (and complete installation), but UEFI machines, or machines starting in UEFI mode can’t do this at the moment.
What happens is:
— boot the computer over network (or tablet), we mainly want the elitepad to get working (x86 uefi), but I’ve also tried booting another machine using x64 UEFI with the same result
— the following is shown:
>>Start PXE over IPv4, Press [ESC] to exit…
Station IP address is x.x.x.x
Server IP address is x.x.x.x
NBP filename is bootx86wdsmgfw.efi
NBP filesize is xxxxx bytes
Downloading NBP File
Succeed to download NBP file.
[EDIT] Not sure if it’s NEP or NBP file, not very clear on the screen
Then the screen changes and I see:
Windows Depoyment Services (server IP: x.x.x.x)
Contacting Server (x.x.x.x): — (this is like turning / — — / — …)
ESC= Exit
After a while (timeout)the computer shows:
Windows Deployment Services encountered an error:
Error Code: 0x102
ENTER=Reboot
What I’ve tried/changed so far:
Changed the NBP filename in DHCP options, it used to be bootx86wdsnbp.com (when not using UEFI), before changing this I simply got network error when trying to network boot.
Added NIC (and other) drivers in WDS 2012, regenerated the boot image afterwards etc.
Tried reinstalling WDS on a newly installed windows server 2012 (without mdt) in standalone mode.
Other stuff I can’t think of at the moment 
PXE booting of our SCCM 2012 update 1 (only used for updates & endpoint protection at the moment), but with the same result
Any thoughts/ideas? I have a feeling I’m overlooking something stupid, but then again it may not be stupid.
Thank you
[EDIT]
Sorry I should have posted this in
http://www.windows-noob.com/forums/index.php?/forum/43-windows-deployment-services-wds/
[/EDIT]
Edited November 12, 2013 by anyweb
replacing NEP with NBP
-
#2
What error do you get when you PXE boot the clients (HP Probook’s like 650 G3 or 650 G4)?.
-
Thread Starter
-
#3
Hi,
I get the following error code:
Windows Deployment Services (SERVER IP: (server IP SCCM Server))
Windows Deployment Services encountered an error:
Error Code: 0x102
See screenshot as attachment.
-
SCCM_error.jpg
315.6 KB
· Views: 12
-
#4
Are you using IP helpers or DHCP options ?.
-
Thread Starter
-
#5
We use both, IP-helpers are configured on the switch and DHCP options are active on the scope.
Before updating to the newest hotfix everything works fine, after the update one or two models can’t connect with PXE.
-
#6
Hi,
Did you get a resolution to this issue?
I upgraded our ADK and WinPE Extensions to 2004 and now PXE boot is not working.
PXE attempts just fail and error with the same error you have posted.
-
Thread Starter
-
#7
No, this one specific device will not deploy PXE or connect to PXE. Other devices works fine.
-
#8
I’m getting this same issue on some laptops and desktops as well. Seems completely random
— HP EliteBook 840 G6
— HP ProDesk 600 G4 Mini Desktop
I’ve seen on other forums that switching to IP Helpers instead of DHCP options resolves this issue but I’m not exactly sold on that. I know IP Helpers should be used in general — although I need to jump through hoops to get my network team to make this change across all our networks.
Any other suggestions?
-
#9
We have configured an OSD server on VM. Getting this error while starting PXE boot. We have updated DHCP scope option 66 and 67. Can anybody help please?
-
WDS Error.PNG
112.3 KB
· Views: 4
-
#10
Hi all
I have the same problem
You have resolve?
-
#11
Having the same problem with a specific model of drop-in PC module from Viewsonic (WDS Error Code: 0x102 when trying to contact the server). All other devices in our inventory are PXE booting/imaging without error.
I am told that IP helper addresses are configured, but much like Chris F stated above, I cannot confirm this, as I work in an organization large enough to have some degree of separation between the systems admin and network infrastructure teams. The DHCP options are configured, but when they are removed, PXE boot fails for all devices — not just the new Viewsonics we’re currently having an issue with.
This leads me to believe that the IP helper addresses are not correctly configured, but the issue remains that with the use of DHCP options, we can successfully PXE boot/image everything in our inventory with the exception of this model (VPC25-W33-P1-1T/VS18617).
Version 2111
Site version: 5.0.9068.1000
Last edited: Aug 3, 2022