Windows deployment services encountered an error 0x102

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…

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…

My DHCP options include 66 (IP of wds server), 67 (bootx64wdsmgfw.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

Windows deployment services encountered an error 0x102

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

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.

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.

My DHCP options include 66 (IP of wds server), 67 (bootx64wdsmgfw.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.

Источник

Windows deployment services encountered an error 0x102

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

I have ISC DHCP setup with a host block for many hosts pointing to either PXELinux or WDS depending on the OS to install (RHEL, SLES, Windows 2008 R2, Windows 2012). The host block looks like:

hardware ethernet %MAC% ;

next-server %WDS/PXELinux IP% ;

When I point to the PXELinux server, everything works fine. However, if I point to WDS, the nbp file (wdsmgfw.efi) loads and then I receive:

Windows Deployment Services encountered an error:

Error Code: 0x102

I setup Wireshark on the WDS server with filter ip.addr == 10.16.195.8 (DHCP assigned to the test client) and see the TFTP transaction for the nbp file, but then all that is received is «348 DHCP Request — Transaction ID 0x40e20100» until I receive the error.

If I go through Server Manager > WDS > Windows Deployment Services Management Console > Servers > Right-click server > Properties > DHCP and uncheck «Do not listen on DHCP ports» and reboot the client, Windows will install without a problem. However, if I then switch the host to point at the PXELinux server, it will continue to boot and load Windows.

How can I get Windows to load the nbp file and then continue to load without listening to the DHCP ports and breaking PXELinux?

Источник

Windows deployment services encountered an error 0x102

Вопрос

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.

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.

My DHCP options include 66 (IP of wds server), 67 (bootx64wdsmgfw.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.

Источник

Windows deployment services encountered an error 0x102

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

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.

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.

My DHCP options include 66 (IP of wds server), 67 (bootx64wdsmgfw.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.

Источник

Windows deployment services encountered an error 0x102

Вопрос

I have ISC DHCP setup with a host block for many hosts pointing to either PXELinux or WDS depending on the OS to install (RHEL, SLES, Windows 2008 R2, Windows 2012). The host block looks like:

hardware ethernet %MAC% ;

next-server %WDS/PXELinux IP% ;

When I point to the PXELinux server, everything works fine. However, if I point to WDS, the nbp file (wdsmgfw.efi) loads and then I receive:

Windows Deployment Services encountered an error:

Error Code: 0x102

I setup Wireshark on the WDS server with filter ip.addr == 10.16.195.8 (DHCP assigned to the test client) and see the TFTP transaction for the nbp file, but then all that is received is «348 DHCP Request — Transaction ID 0x40e20100» until I receive the error.

If I go through Server Manager > WDS > Windows Deployment Services Management Console > Servers > Right-click server > Properties > DHCP and uncheck «Do not listen on DHCP ports» and reboot the client, Windows will install without a problem. However, if I then switch the host to point at the PXELinux server, it will continue to boot and load Windows.

How can I get Windows to load the nbp file and then continue to load without listening to the DHCP ports and breaking PXELinux?

Источник

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

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

---

• #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

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