Some notes:
1. If you launch Litetouch from within the old OS, as in a refresh scenario using "cscript.exe \\server\path\Litetouch.vbs <file:///\\server\path\Litetouch.vbs> " then MDT should *automatically* remove the c:\minint folder. 2. If you are launching MDT from within WinPE, as in a "newcomputer" scenario, these should be rare, check the bdd.log files under c:\minint to see what state the machine was in when it was last run. 3. Finally, if you are modifying the BIOS boot order to get the machine to boot to a USB stick, you will get this error message after the "Post-Install" phase, when MDT expects that you will boot into the Windows OOBE setup, but you instead booted back into WinPE, Whoops! I never recommend modifications of the BIOS boot order for just this reason. All good OEM makers support the ability to temporally select a boot device from the boot menu without changing the boot order. -k From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Sunday, July 6, 2014 7:53 PM To: [email protected] Subject: [MDT-OSD] RE: Dealing with old MININT folders What version of MDT are you using? As of 2012u1 (IIRC) it will prompt you asking if you want to ignore the existing deployment. _____ From: [email protected] <mailto:[email protected]> [[email protected]] on behalf of Bain.John [[email protected]] Sent: Wednesday, July 02, 2014 10:53 AM To: '[email protected]' Subject: [MDT-OSD] Dealing with old MININT folders Hello, Technicians in my group are running into the problem of not being able to properly start a MDT deployment when an old c:\minint folder exists. Is there a way to tell the deployment to ignore the old c:\minint folder and start a fresh install ? John
