Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

MDT 2013 (Microsoft Deployment Toolkit) Using Litetouch.vbs does not capture an image.

Posted on 2016-09-19
8
Medium Priority
?
351 Views
Last Modified: 2016-09-21
Our MDT 2013 fails to capture an image, when we run cscript litetouch.vbs, it skips the prompt for the location of the image, and completes.

see below

Windows-8-Test-Build-1.jpg
1. The current Windows 8.1 image Task Sequence can be deployed successfully.
2. The current Windows 10 image Task Sequence can be deployed successfully. (Vanilla Image from WIM Imported ISO)
3. Captures for Windows 8.1 fail.
4. Captures for Windows 10 fail.
5. A new Capture Task Sequence has been created, and also fails.
6. This was working in July 2015, last time an image was captured.
7. Between July 2015 - January 2016, something has broken.
8. Only Windows Updates have been applied to MDT 2013.

We really need a MDT expert, that uses this on a daily basis, to discuss this issue, unless you have seen this issue.

(We've also tried updating to MDT 2013 Update 2, ADK 10, and the issue also remains, so this is something that has changed which causes this!)
0
Comment
  • 5
  • 2
8 Comments
 
LVL 84

Expert Comment

by:David Johnson, CD, MVP
ID: 41805916
in your customsettings.ini add these logging options once you have set up your logs share (everyone read/write)
SLShare=\\MDT01\Logs\
SLShareDynamicLogging=\\MDT01\Logs\%OSDComputerName%

Open in new window


rerun your capture sequence and upload your bdd.log
0
 
LVL 124
ID: 41805995
We have logging options already enabled.

I'll grab the bdd.log later this am.
0
 
LVL 124
ID: 41806410
okay, here is the bdd.log
BDDee.LOG
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LVL 124

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 0 total points
ID: 41808586
Some success, and I've no idea, why I've had to add these to my CustomSettings.ini

DoCapture=YES

ComputerBackupLocation=NETWORK
BackupShare=\\WDS2012\DeploymentShare$
BackupDir=Captures
BackupFile=%OSDComputerName%.wim

The process now continues, Syspreps, reboots, mounts WinPE, and starts the Create Wim Process to the Capture share.

Never had to add them in the past, there was a Dialogue page, where we could enter these details.

It did not work with just adding DoCapture=YES, it needed all the other details, so we will wait and see what happens.

Its a workaround, and that helps us...
0
 
LVL 19

Expert Comment

by:Mike T
ID: 41808654
Hi Andrew,

I was going to look at a normal BDD.log but you beat me to it.
The customsettings.ini (yes, an INI file) pretty much controls the whole of MDT. the settings you have now are normal, as in, what I would expect for a build and capture ruleset.

ComputerName=WIN81REF
UILanguage=en-US
UserLocale=en-US
KeyboardLocale=0409:00000409
TimeZoneName=W. Europe Standard Time
TaskSequenceID=WIN81REF
WSUSServer=http://mdt01.contoso.com:8530
DoCapture=YES
ComputerBackupLocation=NETWORK
BackupShare=\\mdt01.contoso.com\OSD
BackupDir=ReferenceImages
BackupFile=Win81EntRefImage.wim
FinishAction=SHUTDOWN

Ref from Nickolaj's site here: http://www.scconfigmgr.com/2013/09/19/create-a-windows-8-1-enterprise-reference-image-with-mdt-2013/

If you were being prompted by a wizard previously it means certain values were not set and the wizard will appear. Quite what changed and where seems odd, but if you're happy NOT to be prompted, then you're all done. FinishAction is handy for building VMs.

Mike
0
 
LVL 124
ID: 41808773
All seems to be working fine, no idea what's caused this change, but good enough at present for a workaround.

Images are now being captured.
0
 
LVL 124

Author Closing Comment

by:Andrew Hancock (VMware vExpert / EE MVE^2)
ID: 41808774
No idea, why we now have to included these in the INI file, but it's good as a solution now.
0
 
LVL 84

Expert Comment

by:David Johnson, CD, MVP
ID: 41809999
no points: for viewing the log files use cmtrace from sscm makes things much easier
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Tech spooks aren't just for those who are tech savvy, it also happens to those of us running a business. Check out the top tech spooks for business owners.
This article is about my experience upgrading my consulting machine to Windows 10 Version 1709 (The Fall 2017 Creator Update)
Hi friends,  in this video  I'll show you how new windows 10 user can learn the using of windows 10. Thank you.
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
Suggested Courses

916 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question