MDT PXE Boot Issue

[Iain.Faulkner]

Hi all,

 

Slightly strange issue that's occurring. I've got a Windows Server 2016 VM running MDT/WDS for the purposes of rolling out my Windows 10 image in the summer. It was working fine up until a couple of weeks ago. At the start of this issue, when I PXE booted to the server the process would display the normal background it shows prior to showing the task sequences and would then reboot. Since then I've reinstalled/upgraded MDT, WINPE and ADK and now when I pxe boot rather than displaying the task sequences it boots into a command prompt.

 

Anyone come across something similar?

 

Thanks in advance

 

Iain

[sted]

when it boots it should show the ip of the wds server is that the right one?

 

have you updated the wim file in wds maybe thats wrong (worth trying adding a 2nd (or extra if you have more than 1) just borrow the boot.wim from a win10/server20xx dvd and as as is and boot to that see what happens (it should look like the normal install from disk process iirc)

 

if you upgraded the wadk stuff did you also download the winpe addon (its now a separate part) and did you rebuild the bot image in mdt after you updated the deployment share

Edited March 7, 2019 by sted

[Iain.Faulkner]

when it boots it should show the ip of the wds server is that the right one?

 

have you updated the wim file in wds maybe thats wrong (worth trying adding a 2nd (or extra if you have more than 1) just borrow the boot.wim from a win10/server20xx dvd and as as is and boot to that see what happens (it should look like the normal install from disk process iirc)

 

if you upgraded the wadk stuff did you also download the winpe addon (its now a separate part) and did you rebuild the bot image in mdt after you updated the deployment share

 

Thanks for that, some of this I'd already checked but double checked it anyway.

 

The IP address is correct and I did also download and install the WINPE addon. I hadn't rebuilt the boot image in MDT after doing the WINPE though so I've done that and the issue still remains. I'm going to try adding the additional wim file now just to see what happens.

 

My only other thought is that I know this was working prior to half term, so I might restore the server to then and see what happens and if I can recreate the issue just so I know what the cause is.

[Iain.Faulkner]

Ok, so I've added a boot image from a Win 10 DVD and PXE booted to it. That boots absolutely fine and takes me through the general installation steps for Windows 10

[sted]

Ok, so I've added a boot image from a Win 10 DVD and PXE booted to it. That boots absolutely fine and takes me through the general installation steps for Windows 10

id go to mdt and do a complete rebuild of your boot image im guessing somethings made it funny probably updating the wadk at a guess

 

[Iain.Faulkner]

id go to mdt and do a complete rebuild of your boot image im guessing somethings made it funny probably updating the wadk at a guess

 

[ATTACH=CONFIG]52499[/ATTACH]

 

Sorry, should have added that I've already done this

[Iain.Faulkner]

Just wanted to add to this, with thanks to someone on another forum, it looks like we've resolved this.

 

The fix was to run something called LTICleanup, as detailed here - https://mdtguy.wordpress.com/page/2/ I ran this through the command prompt that was being booted into and it resolved it.