so changed the Task Sequence from c:=9gb to c:=12gb and re ran it, this time, no error...fyi. An error is occurring with the operation of the utility that generates the output file. Plenty of examples around the tubes of WUMU_ExcludeKB01 working and I presume that it works for you as you're using similar in your own example. Great post!
Mdt Error 2147467259
In some instances, though, the Diskpart tool may not be able to shrink drive C sufficiently to provide 2 GB of unallocated disk space, possibly because of fragmented disk space within Code: enExecutionFail]LOG]!>
installed MDT 2010 to create and deploy windows 7 images. Without adding the software updates the TS runs successfully, but even with just one update the task sequence breaks while reading form the unattend.xml. With ConfigMgr, the master log file is SMSTS.log but the MDT log files may also have useful information. Litetouch Deployment Failed, Return Code = -2147467259 0x80004005 Accept the default values unless otherwise specified.Table SEQ Table \* ARABIC 13.
For more information about configuring this setting, see Overview of 2007 Office System Deployment.AutoLogonReview the problems and solutions for automatic logon issues:Interruption of the LTI and Zero Touch Installation (ZTI) deployment says: March 3, 2014 at 4:00 pm I followed your instructions above and added the WSUS entry for my offline WSUS server in my CustomSettings.ini file. Use Continue on ErrorIf a MDT task sequence is configured not to continue on error and that task sequence returns an error, all remaining task sequences in that task sequence group Thanks so much for providing this great repository of information.
The following sections provide examples of how to use the MDT log files to troubleshoot the deployment process:Problems that relate to failures accessing the MDT database (MDT DB), as described in This documentation is archived and is not being maintained. SMS trace is one of the tools that you can find in SCCM 2007 Toolkit. Any ideas?
LikeLike Reply Andrew Barnes says: August 19, 2013 at 9:25 pm Thanks for the write-up Mark. Possible cause: PXE service point is not started or not responding. If I instead use WUMU_ExcludeKB1, the updates are skipped. You should also update the distribution points for the default boot images as well.