<div>
in your customsettings.ini add these logging options once you have set up your logs share (everyone read/write)<br />

<pre><code class="code-1 nolinks" id="code-20-41805916-1"><span>SLShare=\\MDT01\Logs\</span>
<span>SLShareDynamicLogging=\\MDT01\Logs\%OSDComputerName%</span>
</code></pre>
<br />
rerun your capture sequence and upload your bdd.log
</div>


<div>
We have logging options already enabled.<br />
<br />
I'll grab the bdd.log later this am.
</div>


<div>
okay, here is the bdd.log<br />
<a href="https://filedb.experts-exchange.com/incoming/2016/09_w39/1117589/BDDee.LOG" target="_blank" class="file-inline" title="BDDee.LOG (28 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>BDDee.LOG</a>
</div>


BDDee.LOG

<div>
Hi Andrew,<br />
<br />
I was going to look at a normal BDD.log but you beat me to it.<br />
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.<br />
<br />
ComputerName=WIN81REF<br />
UILanguage=en-US<br />
UserLocale=en-US<br />
KeyboardLocale=0409:000004<wbr />09<br />
TimeZoneName=W. Europe Standard Time<br />
TaskSequenceID=WIN81REF<br />
WSUSServer=<a href="http://mdt01.contoso.com:8530" rel="ugc">http://mdt01.contoso.com:8530</a><br />
DoCapture=YES<br />
ComputerBackupLocation=NET<wbr />WORK<br />
BackupShare=\\mdt01.contos<wbr />o.com\OSD<br />
BackupDir=ReferenceImages<br />
BackupFile=Win81EntRefImag<wbr />e.wim<br />
<b>FinishAction=SHUTDOWN</b><br />
<br />
Ref from Nickolaj's site here: <a href="http://www.scconfigmgr.com/2013/09/19/create-a-windows-8-1-enterprise-reference-image-with-mdt-2013/" rel="ugc">http://www.scconfigmgr.com/2013/09/19/create-a-windows-8-1-enterprise-reference-image-with-mdt-2013/</a><br />
<br />
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.<br />
<br />
Mike
</div>


<div>
All seems to be working fine, no idea what's caused this change, but good enough at present for a workaround.<br />
<br />
Images are now being captured.
</div>


<div>
No idea, why we now have to included these in the INI file, but it's good as a solution now.
</div>


<div>
no points: for viewing the log files use cmtrace from sscm makes things much easier
</div>


<div>
<div class="content wysiwyg-content">
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.<br />
<br />
see below<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2016/09_w39/1117369/Windows-8-Test-Build-1.jpg" target="_blank" title="Windows-8-Test-Build-1.jpg (104 KB)"><img alt="Windows-8-Test-Build-1.jpg" class="file-block lazyload" style="max-width: 724px;" data-src="https://filedb.experts-exchange.com/incoming/2016/09_w39/1117369/Windows-8-Test-Build-1.jpg" /></a><br />
1. The current Windows 8.1 image Task Sequence can be deployed successfully.<br />
2. The current Windows 10 image Task Sequence can be deployed successfully. (Vanilla Image from WIM Imported ISO)<br />
3. Captures for Windows 8.1 fail.<br />
4. Captures for Windows 10 fail.<br />
5. A new Capture Task Sequence has been created, and also fails.<br />
6. This was working in July 2015, last time an image was captured.<br />
7. Between July 2015 - January 2016, something has broken.<br />
8. Only Windows Updates have been applied to MDT 2013.<br />
<br />
We really need a MDT expert, that uses this on a daily basis, to discuss this issue, unless you have seen this issue.<br />
<br />
(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!)
</div>
</div>


Windows-8-Test-Build-1.jpg

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



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!)

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

Software is any set of instructions that directs a computer to perform specific tasks or operations. Computer software consists of programs, libraries and related non-executable data (such as documentation). Computer software is non-tangible, contrasted with computer hardware, which is the physical component of computers. Software written in a machine language is known as "machine code". However, in practice, software is usually written in high-level programming languages than machine language. High-level languages are translated into machine language using a compiler or interpreter or a combination of the two.

Software

IT Administration is the processes and best practices for programming and development, and incorporates methodologies for managing activities and projects. Common methodologies include waterfall, prototyping, iterative and incremental development, spiral development, rapid application development, extreme programming and various types of agile methodology. The life-cycle "model" is a more general term for a category of methodologies, and a software development "process" a more specific term to refer to a specific process chosen by a specific organization.

IT Administration

Windows Server 2012 is the server version of Windows 8 and the successor to Windows Server 2008 R2. Windows Server 2012 is the first version of Windows Server to have no support for Itanium-based computers since Windows NT 4.0. Windows Server 2012, now in its second release (Windows Server 2012 Release 2) includes Foundation, Essentials, Standard and Datacenter, and does not support IA-32 or IA-64 processors.

Windows Server 2012

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

Windows 8 is a personal computer operating system developed by Microsoft as part of the Windows NT family of operating systems, with an emphasis on improving its user experience on tablets. In particular, these changes included a touch-optimized Windows shell based on Microsoft's "Metro" design language, the Start screen, a new platform for developing apps with an emphasis on touchscreen input, integration with online services, support for USB 3.0, Advanced Format hard drives, near field communications, and cloud computing. Additional security features were introduced, such as built-in antivirus software, integration with Microsoft SmartScreen phishing filtering service and support for UEFI Secure Boot on supported devices with UEFI firmware.