MDT loading to cmd prompt
I was running an MDT LiteTouch deployment and the computer kept getting stuck at a command prompt after loading into MDT environment. Normally it should have launched right into the LiteTouch wizard, but for whatever reason, it just didn’t want to go beyond this point on its own. I discovered two possible ways to circumvent it.
I had used this same means of deployment on other machines of the same make and model, with the same Task Sequence, so I knew it wasn’t a driver issue as many eluded to in the various forums I looked at. However, I went ahead and did an “ipconfig” and also tried to mount the MDT share using “net use“, just to make sure there was no network issues. net use z:\\<servername>\deploymentshare$ Well, it turned out that I did already have an IP address and the mapped drive was already in use. So how can I now get on with my deployment?
The first and possibly the easiest way was to just manually launch the LiteTouch. It is as straight forwards as it sounds. I entered the command below into my command prompt, and viola! The LiteTouch wizard came right up and I continued on my way. X:\windows\system32> Z:\scripts\LiteTouch.vbs
The second method, really isn’t any more difficult than the first. Sometimes a folder named “MININIT” already exists on the computer’s C: drive and it can cause issues when trying to do a new deployment. The way around that is just to wipe the drive and essentially start back at square one. Warning though – Following this method WILL erase the drive and wipe any data that is on it. While it probably doesn’t matter, as you’re stuck anyways, but it is just something to be aware of.
At the first Wizard window, press F8. Then type:
Diskpart (enter)List disk (enter)Select disk 0 (choose your main OS disk) (enter)Clean (enter)Reboot and start your imaging process again.
After wiping the disk of any pre-existing partitions your next deployment attempt should go smoothly as it now has a blank HDD to work on.
Thanks for this. Had same problem. I had tried to start litetouch from the command prompt with no success and then found this article. Didn’t think to clean the disk. Worked perfectly.
This works! It was the last section for me (command prompt stuff). Thank you!
Thank you for this post.
How do i recall a specific Task sequence by ID while skipping all other TS from command line?
Can’t recall the command with either BDRun or Wizard.hta, i guess.
Thanks, this helped me!
Hi
I have the same issue except I have tried all of the steps you have kindly provided and I’m still having the same issue.
My setup is WDS booting to MDT, 3 task sequences Laptops, Workstations and Lenovo’s. They all have subtle differences however MDT Database picks the task sequence depending on Make and Model (Bitlocker deployed for laptops), computer name configured per machine by UUID, Serial and MAC Address) and the remaining fields are populated by Location. This all works for every other machine, I simply boot the machine to network and it completes the deployment completely unattended. However I have a batch of Dell Vostro 5468 machines that will not image, they load to WinPE 10 and do the Database checks from CustomSettings.ini (prior to running the task sequence) and then just loads command prompt.
I have checked the IPConfig and it has an IP Address and can see and access the network share using Notepad (mapped as both X and Z for some reason). Only other drive that shows is X.
When I run DiskPart I can see the drive exists and can run the below commands;
List Disk
Select Disk 0
Clean
Exit
Exit
(Machine reboots)
The machine boots form Network and loads from WDS and then MDT, then it runs the Database checks from CustomSettings.ini and again loads the Command Prompt. As mentioned above the same runs perfectly on every other machine HP’s Lenovo’s and Dell’s, only effecting the Vostro 5468.
Any help you can provide would be greatly appreciated.
Hi Phil, you’re going to need to check the SMS logs to see what is happening and why it is getting stuck. Try this_article (no affiliation, was just the top Google result) that describes how to view the deployment log on your device. I’m pretty sure the logs will tell you what’s going on, or at least point you in the right direction. G’luck!
I had this on 2 devices didn’t have the brain capacity to think to try a 3rd which would’ve told me it wasn’t MDT being broken. On the bright side I discovered a much larger issue through trying to fix this.
In the end simply wiping the disks resolved my issue cheers for your help.