Sysprep & Capture - Rebooting with No Capture

Question

First off, thanks for looking at my issue! I've had an MDT server and I have created two task sequences. One to deploy an image that I captured a couple of years ago, and another to capture. It's been awhile since I've captured an image, so I figured I'd update a PC all the way and do another capture.

I'm on the PC I'm trying to capture and I run the litetouch.vbs file, it does a bunch of "MDT" things and eventually reboots the PC, but once it auto-logs in it doesn't continue with anything? I don't see any new windows pop up saying complete or anything, I'm just staring at the desktop. When I go to the MDT server and look in the captures folder, I don't see any new .wim files. The PC has access to the MDT server, I have to access the MDT server in order to run the .vbs file, so I don't think there is any permission issues.

Here are my current Rules:

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=N
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
DoCapture=YES

Any ideas? Let me know if I can show any other info to help figure this out. Thanks all.

Answer 1

Update: I seemed to have fixed it. I have no idea what fixed it but here is what I did:

1. Removed my 2nd deploymentshare (I had created a whole new one when I was trying to figure out what the hell was going on)
2. I decided to try and run the LiteTouch.vbs while logged into the user I set up during Windows First Time setup. Before, I was going into LUSRMGR.msc and re-enabling the Administrator account, then deleting the newly created account that I had set up initially and running LiteTouch using the built-in Administrator account that's disabled during setup (I honestly think it was this that fixed the issue)
3. Removed the changes I did in the Unattend.xml file. I had made changes to the AutoLogon portion of the script and added Administrator and local password. I removed this information.
4. Updated my username/password/domain in the CUSTOM.INI file. I was using another account that wouldn't have worked.

I hope this helps someone else. Just to note, I was also having issues with the sysprep/capture failing due to the Error AppX Package is not installed for all users etc.

Answer 2

Hi, @RS4KING
Thank you for posting in Microsoft Q&A forum.
Someone has the similar issue and fixed by creating a whole new Deployment share called Capture Share with only one capture sequence.
You may refer to Switchbackrack's reply of the link for more details:
https://www.reddit.com/r/MDT/comments/blce42/not_getting_capture_image_page_when_running/

---

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.

Answer 3

Hey sorry for the late response, but I did quite a few things:

1. I created a new Deployment + Task Sequence (SysPrep & Capture)
2. I updated the MDT server, along with reinstalling ADK and WinPE
3. I reformatted the end-user PC, fully updated it as well
4. I also edited the ZTIUtility.vbs script with the following changes... this was recommended on another site.

Look for this line:
If (oTS.SelectSingleNode("//step[@type ='BDD_InstallOS']") is nothing) and
(oTS.SelectSingleNode("//step[@type ='BDD_UpgradeOS']") is nothing) then
And change it to:
If (oTS.SelectSingleNode("//step[@type ='BDD_InstallOS' and @disable='false']") is nothing) and (oTS.SelectSingleNode("//step[@type ='BDD_UpgradeOS' and @disable='false']") is nothing) then

I run LiteTouch.vbs and now it reboots the PC and automatically goes into Microsoft Deployment Toolkit and forces me into CMD (X:\windows\system32). If I close CMD, the PC reboots into the CMD again and continues to do this.

My only solution to this, is to run the following command in CMD RMDIR C:\MININT /q /s to delete the folder and its contents. I close the CMD and it reboots into MDT, but this time it takes me to the "Run the deployment wizard to install a new operating system..." like if I'm trying to image the PC (which I'm not). When I close this MDT window, it takes me back the CMD prompt again. I run the same RMDIR command to delete the MININT folder and close the CMD prompt again, this time it reboots and goes to the DELL logo with a message at the bottom saying "Getting Ready" with the loading circular dots. It then proceeds to a blue screen that says "Just a Moment..." and it sits on "It's taking a bit longer than expected..." for a while.

Once it's done, I get a black screen with an error: "Can not find script file C:\LTIBootstrap.vbs" and I click okay and it takes my back to Windows 10 like normal. I checked C:\deploymentshare\scripts and the LTIbootstrap.vbs file is there so I'm not sure why I got that error.

Anyway, sorry for the long story, but I wanted to be as specific as possible. Thanks in advance.

Answer 4

There seems to be need for another restart here.

In the unattend.xml the configured path is:

<CommandLine>wscript.exe %SystemDrive%\LTIBootstrap.vbs</CommandLine>

This would be on the windows deployment so that the image can be captured.
After some more digging there seems to be a pending reboot that has not been done and since MDT already have changed the boot to WinPE %SystemDrive% has been changed to WinPE.

If you add a reboot just before Imaging in the task sequence this will be resolved.