question

RogerSchneiter-6398 avatar image
0 Votes"
RogerSchneiter-6398 asked RogerSchneiter-6398 commented

How to avoid Boot Loop with MDT and WDS via PXE Network Boot

Hello Everyone

This is my setup:
1) I have a AD DS, DNS and DHCP set up in my envorioment on Windows Server 2016
2) I have MDT and WDS set up on another Windows Server 2016
3) I have Controllers (custom-made Mini Computers with boot order set to Prio 1 = PXE Boot, Prio 2 = Harddisk) that need to be staged with Windows 10 Enterprise LTSC 2019 and some custom Software.

What I did:
I configured everything in MDT for a ZeroTouch Deployment. Task Sequence and everything. Also set up WDS Server to deploy the Image from MDT on to all requesting clients without pressing F12.

I tested it with a virtual Machine in the same network.
This does work perfectly. Since the VM is empty, it will automatically try to PXE boot. No boot loop. It installs perfectly.

Now when I plug in the Controller to the network it starts the boot from PXE without having to press anything. So far so good.
But with the first reboot during the MDT installation, it loads the Image again from the WDS and starts everything again. Boot Loop

I have done a lot of research. I have found some things regarding NetbootMachineFilePath property in Active Directory.
But that means that I have to prestage the Controller, right?
What I need is, that you can just plug the Controller to the switch and let it do its thing. Without having to configure something in advance.

I read something about WDS being able to overwrite the BootProgram when ResetBootProgram parameter is set to DWORD Value 0000001. Which I have.
So that It would need an F12 press on the second time the Controller tries to boot, which would just time out and send it to the Boot Priority 2 --> Hard Disk.
I can't get this to work though. What Am I doing wrong?

Thanks for all suggestions <3

Greetings from Switzerland

mem-mdt
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

AllenLiu-MSFT avatar image
0 Votes"
AllenLiu-MSFT answered RogerSchneiter-6398 commented

Hi, @RogerSchneiter-6398
Thank you for posting in Microsoft Q&A forum.
It seems a known MDT issue with LTIApply.wsf file. It needs to be manually changed to correct the network boot loop.
https://serverfault.com/questions/893467/wds-mdt-how-to-avoid-pxe-boot-loop


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.


· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

It seems there is no update for a couple of days. May we know the current status of the problem? Is there any other assistance we can provide?

0 Votes 0 ·

Hello Allen
Thank you very much for the answer.

The solution you provided needs Prestageing in AD, right? If not, could you explain the steps I need to take? I don't get it...

I can't have that. The company I work for doesn't want this.

Endgoal is:
Controller delivered.
Controller pluged in with Ethernet.
Wait couple of hours.
Controllers are fully staged and ready to use.


I had a couple other approaches which all failed:
- In WinPE, create a file on the hard disk, then when it starts again into WinPE (Loop), i check if the file is there. And if it is --> Boot from HD or abort PXE boot. That would work, but I dont know how to tell the system to Boot from next Priority (HD), so it would continue the Installation....

  • Powershell skript before first restart (before the bootloop starts...) which remotely adds the Computer to the Prestaged Devices (Which would have worked, but in the limited WinPE Powershell Remoting is disabled...) So this didnt work either...


0 Votes 0 ·