This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 86%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAZ%3C/text%3E%3C/svg%3E)
Hello
I am trying to deploy a newly created image in MDT, captured using MDT. I get the error message:
NBP filesize is 0 bytes
PXE-E99: Unexpected network error
I have:
Server 2019 DC with DHCP and DNS roles, on the same subnet as the machines I will be imaging/capturing
Added 060, 066 and 067 entries in DHCP. 060 = PXEClient, 066 = server IP, 067 = \smsboot\x64\bootmgfw.efi
Captured a Win 10 Pro x64 HP laptop image using MDT, which was successful, using MDT.
I read somewhere that to deploy images, I need WDS installed as a role then configured. I was under the impression MDT took care of captures and deployment, without the use of WDS. I have nevertheless installed WDS, but not have not added anything to it, just installed and added my DC as a server and made sure I ticked the "do not listen" boxes, and "accept any computer".
Am I wrong in thinking that MDT and WDS are needed to capture then deploy? Do they go hand in hand?
In addition, have I missed anything which will stop the PXE-E99 error from appearing?
Many thanks.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 99%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERS%3C/text%3E%3C/svg%3E)
Not sure about that PXE-E99 but I will look it up, because I believe I encountered that once.
MDT will capture an image, as well as deploy an image.
Where WDS comes in to play is the boot information to 'get to' your
MDTServer. When I started with MDT, each tech had a USB drive with all
of the instructions, CustomSettings info and Rules. We needed the USB every time we imaged a pc because the USB was coded to get to our MDTServer.
Using PXE/WDS, you can enable that feature on your server and copy that boot.wim to one location, WDS, and get rid of the USB (my example). Now,
every time I inject new WinPE drivers or change my bootstrap file, I create a new boot.wim file and put that in place of the one in WDS. It's just one set of instructions for every pc, rather than having individual external drives telling the pc where to go to access MDT.
I hope that helps.
For PXE-E99
You can also do this on the WDS side...
Go into WDS, expand the servers. Right click on the server and select Properties. On the TFTP tab uncheck "Enable Variable Windows Extension".
Hi Rick
The PXE-99 error has now gone. I wonder if it was a mixture of me setting up 60,66 and 67 on DHCP and unticking the Enable Variable Windows Extensions.
However, the laptop now shows "Start PXE over IPV4" and nothing happens.
Am I supposed to configure something on WDS, such as a boot image? If so, what do I need to do?
If your pc sits at starting with ipv4, perhaps your pc just isn't seeing the LAN.
However, if you're booting to WDS, first you need to create a Litetouch.wim by updating your whole deploy share. Then go to the location of that wim, copy it to the Boot section in Wds, delete the boot.wim already there, paste in your Litetouch.wim then rename it to boot.wim.
Lastly, restart the service by right- clicking on your server listed in WDS, All Tasks and choose restart.
If it is still stuck at pxe/ipv4, is dhcp on this same server or is there a separate dhcp server?
This has been my resolution when I encountered this issue:
For PXE-E99
You can also do this on the WDS side...
Go into WDS, expand the servers. Right click on the server and select Properties. On the TFTP tab uncheck "Enable Variable Windows Extension".
Thank you. I shall try this next week, all being well.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 78%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKB%3C/text%3E%3C/svg%3E)
Hello,
I think this thread is dead, but I ran into this exact issue today so maybe it will help someone. What worked for me was making sure the 'Windows Deployment Services Server' service was running. As soon as the service was successfully running, I could once again PXE boot.
Hi,
Thank you very much for sharing! I think maybe other peoples with the same issue will benefit from it.
Have a nice day!
Best regards,
Simon
Hi,
Thanks for posting in Microsoft Q&A forum.
1, May we know if you are using PXE boot? If yes, do not use DHCP options 60,66 and 67 on your DHCP servers. If the options are configured, the DHCP server will masquerade as a PXE server and respond to the client with path to the network boot program, then the PXE may fail. Refer to: You want to PXE Boot? Don't use DHCP Options.
2, We recommend that you refer to the official article to build your MDT environment: Prepare for deployment with MDT
Best regards,
Simon
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Hi,
Hope everything goes well. We haven't heard from you for a few days and would like to know the current status of the problem. If there is any chance to try above suggestions? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.
Thanks for your time.
Best regards,
Simon
Thank you. I shall try this next week, all being well.
Yes, thank you for your answer. Unfortunately, I was not able to dedicate any time this week, but hopefully can get back to MDT/WDS next week.
Hi,
Thanks for your feedback. Look forward to hearing from you. If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.
Best regards,
Simon
Hi Simon
I have removed options 60. 66 and 67 from DHCP.
Now the laptop boots (upon hitting F12) with "Start PXE over IPV4" and it sits there for a minute or so, then returns back to the boot menu. I asked above if I am supposed to configure something else in WDS...
