MDT LiteTouch Deployment Looping RRS feed

  • Question

  • Good afternoon, everyone,

    We are currently using MDT 2013 and Server 2012 R2 in order to deploy a Custom Win10 x64 Ent. Image to approximately 350+ client machines per day using a New Computer Task Sequence (SCCM is not available to us in the immediate future).

    Until a few days ago we were manually entering the One Time Boot Menu (F12) on each machine and selecting the Onboard NIC (IPv4) option to begin Litetouch via the Network.

    In an effort to increase our daily production and reduce actual time on the Integration floor we had our asset supplier pre-configure the UEFI boot sequence to the following:

    Onboard NIC (IPv4)

    Onboard NIC (IPv6)

    Windows Boot Manager

    Installed HDD

    This project has grown beyond it's original conception and many of us are not professionally trained in MDT (Youtube FTW), and we thought this would allow us to hit the power button and walk away until Post-Installation QC (which we require manual verification).

    Instead we are experiencing and MDT Loop.  After MDT finished installing the OS and applying the unattend file the task sequence as a default restart.  The computer reboots and then goes right back into MDT.  Of course you all know what happens next, we get a "Dirty Environment" error.

    We understand that for some reason the boot order is not getting updated with Windows Boot Manager after the OS Install before it boots back to the network but here is where the mystery starts.

    It doesn't infinitely loop.  If we select "Yes" in the Dirty Environment window and tell it to ignore the deployment in progress and start a new one, it doesn't loop back into MDT but finishes correctly and our machine Post-Installs perfectly.

    When we interrupt the 2nd loop, after selecting "Yes," and go into the boot menu (F12) magically there is a Windows Boot Manager at the top!  But if we tried to let the computer boot MDT tries to continue the deployment from the desktop and then things get ugly.

    Can anybody tell me if there is a way to get the Boot Manager to the top of the list prior to it going back into MDT?  Is this something to do with a restart happening to quickly?

    Also, if it's just not possible please say so and why so I can explain it to people without IT degrees.

    Thank you so much!

    Wednesday, August 23, 2017 4:12 PM

All replies

  • Hi,

    set the Bootorder to


    2. IPv4


    Save and reboot.

    Press F12 and choose IPv4 to boot just onetime IPv4 and PXE

    Btw:What hardwarevendor?Dell,Fujitsu etc. have a bios configuration tool!

    Bis dann, Toni! Wenn Dir meine Antwort hilft dann markiere sie bitte als Antwort! Vielen Dank!

    Wednesday, August 23, 2017 10:01 PM