MDT 2012 Image Fail
I have created a brand NEW deployment share and will be testing it as soon as the server reboots. I am hoping that this will resolve my issue but in the mean time I am looking to see if any one else has ran in to this issue before. Below are the error(s)
I am getting.
Thank you all in advance for the help!
FAILURE 5627: 2: Run DISM.exe error!
Litetouch deployment failed, Return Code = -2147457259 0×80004005
Failed to run the action: Install Operating Ssytem.
Unknown error (Error: 000015Fb; Source Unknown)
The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted( Error: 80004004; Source :Windows)
Failed to run the last action: Install Operatin System. Execution of task sequence failed.
Unknow error (Error: 000015fb; Source Unknown)
Task Sequence Engine failed: enExecutionFail
Task Sequence execution failed withj error code 80004005
error Task Sequence Manger failed to execute task sequence. Code 0×80004005
Thank you for the information. I have reviewed the logs, but being new to such an indepth issue is new to me and I am working it as I can. Below is some of the information I found in the log files. My setup is MDT 2012, WDS, on a 2KR2 server.
BDD.log
FAILURE Run DISM.exe
smsts.log
The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted( Error: 80004004; Source :Windows)
Failed to run the last action: Install OperatinG System. Execution of task sequence failed.
Unknow error (Error: 000015FB; Source Unknown)
Task Sequence Engine failed: enExecutionFail
Task Sequence execution failed with error code 80004005
DISM.log
Microsoft-Windows-ErrorReportingUI.Resources, Version 6.1.7600.16385.pA = PROCESSOR_ARCHITECTURE_AMD64 (9)
Microsoft-Windows-ErrorReportingCore.Resources Version 6.1.7600.16385.pA = PROCESSOR_ARCHITECTURE_AMD64 (9)
Microsoft-Windows-ErrorReportingFaul.Resources Version 6.1.7600.16385.pA = PROCESSOR_ARCHITECTURE_AMD64 (9)
CBS Failed to find a matching version for servicing stack: C:\Users\........
CBS Failed to find a servicing stack directory in online store, [HResult = 0x80070490 - Error_Not_Found
Multiel CSI errors (Access Denied) for the registry
CSI Processing Namespace
I am hoping some of this helps, becasue the only option I have as of now is to redo the entire computer profile for sysprep and capture. Maybe I configured the default profile wrong or missed a permissions item, not sure, but all help is greatful.
Similar Messages
-
Hello,
I'm hoping someone can assist. I have an image that was working but the builtin admin account was disabled. I went into the image and enabled the account and set a password. I ran sysprep and capture. Now, when i try to deploy either
image, it installs the OS, reboots and then sits at a login (does not go into the admin account to continue). I login and i notice that LTIBootstrap.vbs is sitting on the root of c along with the Minint folder and other MDT folders. I have MDT
on 2 servers and they both do the same thing. Unattend.xml in c:\minint has the correct local admin/password
Customsettings.ini:
[Settings]
Priority=Default
Properties=MyCustomProperties
[Default]
DeployRoot=\\ourserver\D$\DeploymentShare$
ComputerBackupLocation=Network
Home_Page=http://home
OSInstall=Y
SkipAdminPassword=YES
SkipApplications=YES
SkipAppsOnUpgrade=YES
SkipBDDWelcome=YES
SkipBitLocker=YES
SkipComputerName=YES
OSDComputerName=HDQ-%SerialNumber%
SkipComputerBackup=YES
SkipDeploymentType=YES
SkipDomainMembership=YES
JoinDomain=OurDomain
DomainAdmin=xxxx(Account with Join domain rights)
DomainAdminDomain= Our Domain
DomainAdminPassword=Password for account
SkipAdminAccounts=YES
SkipFinalSummary=NO
FinishAction=Reboot
SkipLocaleSelection=YES
KeyboardLocale=en-US
UserLocale=en-US
UILanguage=en-US
SkipPackageDisplay=YES
SkipProductKey=YES
SkipSummary=No
SkipTaskSequence=NO
SkipTimeZone=YES
TimeZoneName=Eastern Standard Time
SkipUserData=YES
EventService=http://OurServer:9800
[Settings]
Priority=Default
[Default]
DeployRoot=\\OurServer\D$\DeploymentShare$
UserID=account to join to domain
USerDomain=Our Domain
UserPassword=Account password to join domain
Any help would be greatly appreciated.
Thanks
Rick
BDD.LOG
<![LOG[ZTINextPhase COMPLETED. Return Value = 0]LOG]!><time="14:10:58.000+000" date="01-13-2014" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase">
<![LOG[ZTINextPhase processing completed successfully.]LOG]!><time="14:10:58.000+000" date="01-13-2014" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase">
<![LOG[Event 41001 sent: ZTINextPhase processing completed successfully.]LOG]!><time="14:10:58.000+000" date="01-13-2014" component="ZTINextPhase" context="" type="1" thread="" file="ZTINextPhase">
<![LOG[Command completed, return code = -2147021886]LOG]!><time="14:10:58.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LTIDirty is now = FALSE]LOG]!><time="14:10:58.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[If there is a drive letter defined, make sure we clear it now so we can *force* recalcutation.]LOG]!><time="14:10:59.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread=""
file="LiteTouch">
<![LOG[Property OSDTargetDriveCache is now = DIRTY]LOG]!><time="14:10:59.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[LTI initiating task sequence-requested reboot.]LOG]!><time="14:10:59.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Event 41017 sent: LTI initiating task sequence-requested reboot.]LOG]!><time="14:10:59.000+000" date="01-13-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">Hi Rick,
To my understanding, sysprep and to be more specific the "gerenalize" step will make sure all personalized information will be removed before entering the capture mode.
I'm aware additional created account's will be preserved, but I can't tell you about the built-in administrator account.
The first thing that comes to mind is that, your Build task sequence uses a Unattend.xml, just the same as your Deploy task sequence does this.
Assuming that you don't do anything you haven't mentioned with the account in the task sequence, like renaming the admin account or setting a different password during the task sequence. Cross checking both your Unattended.xml would be a good place to start.
Also, it is known, that Windows allows the machine to be auto logged on, a couple of times. So please check if this isn't also the case. See this link for more info: http://support.microsoft.com/kb/324737
Lastly if all else fails, you can set the account enabled, and a password by commandline, but this should only be done as a temporarily work around. See these links for more information: http://support.microsoft.com/kb/251394 and http://social.technet.microsoft.com/wiki/contents/articles/3040.enable-disable-the-local-hidden-built-in-administrator-account-in-windows-7.aspx
Good luck!
If this post is helpful please click "Mark for answer", thanks! Kind regards -
I'm trying to create MDT boot images using MDT 2012 U1 on CM 2012 R2 but I keep getting this error message as desribed by this entry on
James Bannan's blog
The suggested fix/workaround is to launch the CM console as administrator. I've tried that with no success and wondered if anyone else has seen this and perhaps knows what the problem is? Any help would be appreciated. Merry Christmas!Thanks, is 2013 required or recommended? The guys running the server re-installed WAIK and the process completed successfully.
-
Windows 7 Image Deployment Failed in HP model D530 using MDT 2012 and ADK 8.0
Hi,
I need your help to sort out the following issue.
I have installed MDT 2012 +ADK 8.0 and created Windows 7 32 bit OS from CD in the deployment share and tried deploying the raw OS from Deployment Share in to a reference machine (HP D530) ,the deployment failed also couldn't able to capture
Image from the machine,even the sysprep failed. This is the error
Your PC needs to restart.
Please hold down the power button.
Error Code:0x0000005D
Parameters:
0x030F0209
0x746E6547
0X49656E69
0X6C65746E
So tried the same in another HP machine ,the deployment was success and also was able to capture the refrence machine.
Need your help to find why this error occurred in this specific HP model D530 alone. Is it the reason that ADK was not supported in that specific model.
D530 is the maximum available HW model in client environment so your help will be much appreciated.
Thanks in Advance!!I have never seen that error before (see identical post). I did a quick internet search and found the following:
http://optimizewindows8.wordpress.com/2013/03/26/how-to-fix-error-code-0x0000005d/
Either:
1) Upgrade your machines with modern processors that support the ADK.
or
2) Downgrade to the WAIK
http://www.microsoft.com/en-us/download/details.aspx?id=5753 and stick with Windows 7.
Keith Garner - keithga.wordpress.com -
MDT 2012 Update 1 Boot Image Creation Fails in SP1
I have my site server (SCCM 2012 SP1) installed on Server 2012 with the Windows 8 ADK installed (I've also tried installing the Win7 WAIK with no change to the below problem). It is hosting the site server, FSP, AIS, and Endpoint protection roles. I
installed MDT 2012 Update 1 (build 6.1.2373.0) and installed ConfigMgr integration. I have a share
\\siteserver\bootimages that I'm creating the boot image to and the system account has full control on both the NTFS and Share permissions. When I create the boot image I get an error almost immediately and
a popup that the Microsoft.BDD.ElevatedProxy has stopped working. Details from the pop-up:
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: microsoft.bdd.elevatedproxy.exe
Problem Signature 02: 3.0.0.0
Problem Signature 03: 50400c36
Problem Signature 04: System.ServiceModel
Problem Signature 05: 3.0.0.0
Problem Signature 06: 4fee6b19
Problem Signature 07: fb9
Problem Signature 08: a7
Problem Signature 09: G3DT0URDW53KGT4VJDEEQCRAUIFCNTLL
OS Version: 6.2.9200.2.0.0.272.7
Locale ID: 1033
The error in the boot image creation wizard is:
Started processing.
Creating boot image.
Error while importing Microsoft Deployment Toolkit Task Sequence.
System.ServiceModel.FaultException: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug>
configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework 3.0 SDK documentation and inspect the server trace logs.
Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at INewBootImage.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
at NewBootImageClient.Create(String platform, String scratchSpace, String[] components, String[] extraContent, String wimFile)
at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)
I haven't found anything online on this particular error, I've seen all the ones about MDT 2012 and ConfigMgr 2012 CU 1. Any ideas? Any logs that may be revealing to the cause of this error? I've tried removing integration components, uninstalling MDT, reboot,
re-installing, etc, but same problem occurs each time.I just tried to create a new boot image again, the DISM.log file does not show any evidence of the attempt to create the boot wim, in fact nothing since 0800 this morning. The most recent logs are as follows:
2013-03-03 20:22:59, Info DISM PID=2252 TID=4312 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2013-03-03 20:22:59, Info DISM PID=2252 TID=4312 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2013-03-03 20:22:59, Info DISM API: PID=2252 TID=4312 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-03 20:22:59, Info DISM API: PID=2252 TID=3088 Deleted g_internalDismSession - DismShutdownInternal
2013-03-03 20:22:59, Info DISM API: PID=2252 TID=3088 Shutdown SessionTable - DismShutdownInternal
2013-03-03 20:22:59, Info DISM API: PID=2252 TID=3088 Leave DismShutdownInternal - DismShutdownInternal
2013-03-03 20:22:59, Info DISM API: PID=2252 TID=3088 DismApi.dll:
- DismShutdownInternal
2013-03-03 20:22:59, Info DISM API: PID=2252 TID=3088 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2013-03-03 20:22:59, Info DISM API: PID=2252 TID=3088 DismApi.dll:
- DismShutdownInternal
2013-03-03 22:02:50, Info DISM API: PID=3544 TID=3672 DismApi.dll:
- DismInitializeInternal
2013-03-03 22:02:50, Info DISM API: PID=3544 TID=3672 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
2013-03-03 22:02:50, Info DISM API: PID=3544 TID=3672 DismApi.dll:
- DismInitializeInternal
2013-03-03 22:02:50, Info DISM API: PID=3544 TID=3672 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
2013-03-03 22:02:50, Info DISM API: PID=3544 TID=3672 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
2013-03-03 22:02:50, Info DISM API: PID=3544 TID=3672 Enter DismInitializeInternal - DismInitializeInternal
2013-03-03 22:02:50, Info DISM API: PID=3544 TID=3672 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
2013-03-03 22:02:50, Info DISM API: PID=3544 TID=3672 Initialized GlobalConfig - DismInitializeInternal
2013-03-03 22:02:50, Info DISM API: PID=3544 TID=3672 Initialized SessionTable - DismInitializeInternal
2013-03-03 22:02:50, Info DISM API: PID=3544 TID=3672 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2013-03-03 22:02:51, Info DISM API: PID=3544 TID=3672 Waiting for m_pInternalThread to start - CCommandThread::Start
2013-03-03 22:02:51, Info DISM API: PID=3544 TID=4172 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-03 22:02:58, Info DISM API: PID=3544 TID=4172 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-03 22:02:58, Info DISM API: PID=3544 TID=3672 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2013-03-03 22:02:58, Info DISM API: PID=3544 TID=3672 m_pInternalThread started - CCommandThread::Start
2013-03-03 22:02:58, Info DISM API: PID=3544 TID=3672 Created g_internalDismSession - DismInitializeInternal
2013-03-03 22:02:58, Info DISM API: PID=3544 TID=3672 Leave DismInitializeInternal - DismInitializeInternal
2013-03-03 22:03:57, Info DISM API: PID=3544 TID=3672 Enter DismShutdownInternal - DismShutdownInternal
2013-03-03 22:03:57, Info DISM API: PID=3544 TID=3672 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2013-03-03 22:03:57, Info DISM API: PID=3544 TID=3672 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2013-03-03 22:03:57, Info DISM API: PID=3544 TID=3672 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2013-03-03 22:03:57, Info DISM API: PID=3544 TID=4172 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2013-03-03 22:03:57, Info DISM API: PID=3544 TID=4172 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2013-03-03 22:03:59, Info DISM API: PID=3544 TID=4172 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2013-03-03 22:03:59, Info DISM API: PID=3544 TID=4172 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-03 22:04:39, Info DISM PID=3544 TID=4172 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
2013-03-03 22:04:39, Info DISM PID=3544 TID=4172 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2013-03-03 22:04:39, Info DISM PID=3544 TID=4172 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2013-03-03 22:04:39, Info DISM API: PID=3544 TID=4172 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-03 22:04:39, Info DISM API: PID=3544 TID=3672 Deleted g_internalDismSession - DismShutdownInternal
2013-03-03 22:04:39, Info DISM API: PID=3544 TID=3672 Shutdown SessionTable - DismShutdownInternal
2013-03-03 22:04:39, Info DISM API: PID=3544 TID=3672 Leave DismShutdownInternal - DismShutdownInternal
2013-03-03 22:04:39, Info DISM API: PID=3544 TID=3672 DismApi.dll:
- DismShutdownInternal
2013-03-03 22:04:39, Info DISM API: PID=3544 TID=3672 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2013-03-03 22:04:39, Info DISM API: PID=3544 TID=3672 DismApi.dll:
- DismShutdownInternal
2013-03-04 08:41:07, Info DISM API: PID=1016 TID=1620 DismApi.dll:
- DismInitializeInternal
2013-03-04 08:41:07, Info DISM API: PID=1016 TID=1620 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
2013-03-04 08:41:07, Info DISM API: PID=1016 TID=1620 DismApi.dll:
- DismInitializeInternal
2013-03-04 08:41:07, Info DISM API: PID=1016 TID=1620 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
2013-03-04 08:41:07, Info DISM API: PID=1016 TID=1620 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
2013-03-04 08:41:07, Info DISM API: PID=1016 TID=1620 Enter DismInitializeInternal - DismInitializeInternal
2013-03-04 08:41:07, Info DISM API: PID=1016 TID=1620 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
2013-03-04 08:41:07, Info DISM API: PID=1016 TID=1620 Initialized GlobalConfig - DismInitializeInternal
2013-03-04 08:41:07, Info DISM API: PID=1016 TID=1620 Initialized SessionTable - DismInitializeInternal
2013-03-04 08:41:07, Info DISM API: PID=1016 TID=1620 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2013-03-04 08:41:08, Info DISM API: PID=1016 TID=1620 Waiting for m_pInternalThread to start - CCommandThread::Start
2013-03-04 08:41:08, Info DISM API: PID=1016 TID=4176 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-04 08:41:09, Info DISM API: PID=1016 TID=4176 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-04 08:41:09, Info DISM API: PID=1016 TID=1620 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2013-03-04 08:41:09, Info DISM API: PID=1016 TID=1620 m_pInternalThread started - CCommandThread::Start
2013-03-04 08:41:09, Info DISM API: PID=1016 TID=1620 Created g_internalDismSession - DismInitializeInternal
2013-03-04 08:41:09, Info DISM API: PID=1016 TID=1620 Leave DismInitializeInternal - DismInitializeInternal
2013-03-04 08:42:25, Info DISM API: PID=1016 TID=1620 Enter DismShutdownInternal - DismShutdownInternal
2013-03-04 08:42:25, Info DISM API: PID=1016 TID=1620 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2013-03-04 08:42:25, Info DISM API: PID=1016 TID=1620 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2013-03-04 08:42:25, Info DISM API: PID=1016 TID=1620 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2013-03-04 08:42:25, Info DISM API: PID=1016 TID=4176 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2013-03-04 08:42:25, Info DISM API: PID=1016 TID=4176 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2013-03-04 08:42:25, Info DISM API: PID=1016 TID=4176 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2013-03-04 08:42:25, Info DISM API: PID=1016 TID=4176 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-04 08:42:44, Info DISM PID=1016 TID=4176 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
2013-03-04 08:42:44, Info DISM PID=1016 TID=4176 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2013-03-04 08:42:44, Info DISM PID=1016 TID=4176 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2013-03-04 08:42:44, Info DISM API: PID=1016 TID=4176 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-04 08:42:44, Info DISM API: PID=1016 TID=1620 Deleted g_internalDismSession - DismShutdownInternal
2013-03-04 08:42:44, Info DISM API: PID=1016 TID=1620 Shutdown SessionTable - DismShutdownInternal
2013-03-04 08:42:44, Info DISM API: PID=1016 TID=1620 Leave DismShutdownInternal - DismShutdownInternal
2013-03-04 08:42:44, Info DISM API: PID=1016 TID=1620 DismApi.dll:
- DismShutdownInternal
2013-03-04 08:42:44, Info DISM API: PID=1016 TID=1620 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2013-03-04 08:42:44, Info DISM API: PID=1016 TID=1620 DismApi.dll:
- DismShutdownInternal
2013-03-05 08:44:10, Info DISM API: PID=4140 TID=3140 DismApi.dll:
- DismInitializeInternal
2013-03-05 08:44:12, Info DISM API: PID=4140 TID=3140 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
2013-03-05 08:44:12, Info DISM API: PID=4140 TID=3140 DismApi.dll:
- DismInitializeInternal
2013-03-05 08:44:12, Info DISM API: PID=4140 TID=3140 DismApi.dll: Version 6.2.9200.16384 - DismInitializeInternal
2013-03-05 08:44:12, Info DISM API: PID=4140 TID=3140 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
2013-03-05 08:44:12, Info DISM API: PID=4140 TID=3140 Enter DismInitializeInternal - DismInitializeInternal
2013-03-05 08:44:12, Info DISM API: PID=4140 TID=3140 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
2013-03-05 08:44:12, Info DISM API: PID=4140 TID=3140 Initialized GlobalConfig - DismInitializeInternal
2013-03-05 08:44:13, Info DISM API: PID=4140 TID=3140 Initialized SessionTable - DismInitializeInternal
2013-03-05 08:44:13, Info DISM API: PID=4140 TID=3140 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2013-03-05 08:44:14, Info DISM API: PID=4140 TID=3140 Waiting for m_pInternalThread to start - CCommandThread::Start
2013-03-05 08:44:14, Info DISM API: PID=4140 TID=640 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-05 08:44:32, Info DISM API: PID=4140 TID=3140 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2013-03-05 08:44:32, Info DISM API: PID=4140 TID=3140 m_pInternalThread started - CCommandThread::Start
2013-03-05 08:44:32, Info DISM API: PID=4140 TID=3140 Created g_internalDismSession - DismInitializeInternal
2013-03-05 08:44:32, Info DISM API: PID=4140 TID=3140 Leave DismInitializeInternal - DismInitializeInternal
2013-03-05 08:44:32, Info DISM API: PID=4140 TID=640 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-05 08:45:56, Info DISM API: PID=4140 TID=1320 Enter DismShutdownInternal - DismShutdownInternal
2013-03-05 08:45:56, Info DISM API: PID=4140 TID=1320 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2013-03-05 08:45:56, Info DISM API: PID=4140 TID=1320 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2013-03-05 08:45:56, Info DISM API: PID=4140 TID=1320 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2013-03-05 08:45:56, Info DISM API: PID=4140 TID=640 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2013-03-05 08:45:56, Info DISM API: PID=4140 TID=640 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2013-03-05 08:45:56, Info DISM API: PID=4140 TID=640 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2013-03-05 08:45:56, Info DISM API: PID=4140 TID=640 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2013-03-05 08:46:18, Info DISM PID=4140 TID=640 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
2013-03-05 08:46:18, Info DISM PID=4140 TID=640 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
2013-03-05 08:46:18, Info DISM PID=4140 TID=640 DismCore.dll version: 6.2.9200.16384 - CDISMManager::FinalConstruct
2013-03-05 08:46:18, Info DISM API: PID=4140 TID=640 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2013-03-05 08:46:18, Info DISM API: PID=4140 TID=1320 Deleted g_internalDismSession - DismShutdownInternal
2013-03-05 08:46:18, Info DISM API: PID=4140 TID=1320 Shutdown SessionTable - DismShutdownInternal
2013-03-05 08:46:18, Info DISM API: PID=4140 TID=1320 Leave DismShutdownInternal - DismShutdownInternal
2013-03-05 08:46:18, Info DISM API: PID=4140 TID=1320 DismApi.dll:
- DismShutdownInternal
2013-03-05 08:46:18, Info DISM API: PID=4140 TID=1320 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2013-03-05 08:46:18, Info DISM API: PID=4140 TID=1320 DismApi.dll: -
Unable to capture image using MDT 2012
After running my Sysprep and Capture task using MDT 2012, MDT begins to capture the image and makes it all the way to ~94% and then stops and returns several errors. Any idea as to what may be causing this? Below are the errors returned during the capture
task and the ZTIBackup.log:
Error creating an image of drive C:, re=2
ZTI ERROR - Non-zero return code by ZTIBackup, rc = 2
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Create WIM.
The system cannot find the file specified. (Error: 00000002; Source: Windows)
The execution of the group (capture Image) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)
Failed to run the last action: Create WIM. Execution of task sequence failed.
The system cannot find the file specified. (Error: 00000002; Source: Windows)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
ZTIBackup.log:
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[The task sequencer log is located at X:\windows\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context=""
type="1" thread="" file="ZTIBackup">
<![LOG[OriginalPartitionIdentifier is set, find disk: SELECT * FROM Win32_LogicalDisk WHERE Size = '299999686656' and VolumeName = '' and VolumeSerialNumber = '2A688632']LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup"
context="" type="1" thread="" file="ZTIBackup">
<![LOG[Search for Drive: OriginalPartitionIdentifier SELECT * FROM Win32_LogicalDisk WHERE Size = '299999686656' and VolumeName = '' and VolumeSerialNumber = '2A688632']LOG]!><time="14:01:12.000+000" date="08-15-2014"
component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Found Drive: C:]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Property OSDisk is now = C:]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[BackupDrive not specified searching for backup drive]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[BackupDrive defaulting to Destination Logical Drive: C:]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Checking to see if we can store the backup locally]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Drive C: 160595120]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Local store path = C:\StateStore]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Total used space: 160595120]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Available space at C:\StateStore: 132373320]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Local store not permitted]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Network store path set to blank]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Network store path set to: \\OCS-MDT\CCBShare$\Captures]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Backup file name already set to: CCB01-8_15_14.wim]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Using the backup path: \\OCS-MDT\CCBShare$\Captures\CCB01-8_15_14.wim]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Validating connection to \\OCS-MDT\CCBShare$\Captures]LOG]!><time="14:01:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Already connected to server OCS-MDT as that is where this script is running from.]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[Beginning backup of drive C:]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[About to run command: "\\OCS-MDT\CCBShare$\Tools\X64\imagex.exe" /capture /compress maximum C: "\\OCS-MDT\CCBShare$\Captures\CCB01-8_15_14.wim" "CCB01CDrive" /flags ENTERPRISE]LOG]!><time="14:01:13.000+000"
date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Command has been started (process ID 1568)]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 1568)]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > ImageX Tool for Windows]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Copyright (C) Microsoft Corp. All rights reserved.]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Version: 6.1.7600.16385]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Files/folders excluded from image capture by default:]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \$windows.~bt]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \$windows.~ls]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \winpepge.sys]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \Windows\CSC]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \Recycled]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \Recycler]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \$Recycle.Bin\*]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \System Volume Information]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \pagefile.sys]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > \hiberfil.sys]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Turning on VERIFY option for network share]LOG]!><time="14:01:13.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > Scanning files and directories...]LOG]!><time="14:01:14.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 0% ] Capturing progress ]LOG]!><time="14:18:10.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 17 minutes (process ID 1568)]LOG]!><time="14:18:10.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 1% ] Capturing progress ]LOG]!><time="14:18:10.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 2% ] Capturing progress: 2:22:22 hrs remaining ]LOG]!><time="14:21:04.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 3% ] Capturing progress: 2:23:19 hrs remaining ]LOG]!><time="14:22:41.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 4% ] Capturing progress: 2:23:01 hrs remaining ]LOG]!><time="14:24:11.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 23 minutes (process ID 1568)]LOG]!><time="14:24:11.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 5% ] Capturing progress: 2:39:46 hrs remaining ]LOG]!><time="14:27:38.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 6% ] Capturing progress: 2:43:14 hrs remaining ]LOG]!><time="14:28:53.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 7% ] Capturing progress: 2:43:42 hrs remaining ]LOG]!><time="14:30:39.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 29 minutes (process ID 1568)]LOG]!><time="14:30:39.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 8% ] Capturing progress: 2:41:26 hrs remaining ]LOG]!><time="14:32:08.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 9% ] Capturing progress: 2:43:24 hrs remaining ]LOG]!><time="14:34:47.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 10% ] Capturing progress: 2:41:57 hrs remaining ]LOG]!><time="14:36:09.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 35 minutes (process ID 1568)]LOG]!><time="14:36:09.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 11% ] Capturing progress: 2:38:33 hrs remaining ]LOG]!><time="14:37:31.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 12% ] Capturing progress: 2:35:51 hrs remaining ]LOG]!><time="14:39:18.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 13% ] Capturing progress: 2:33:30 hrs remaining ]LOG]!><time="14:41:00.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 40 minutes (process ID 1568)]LOG]!><time="14:41:00.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 14% ] Capturing progress: 2:30:39 hrs remaining ]LOG]!><time="14:42:28.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 15% ] Capturing progress: 2:28:39 hrs remaining ]LOG]!><time="14:44:23.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 16% ] Capturing progress: 2:28:06 hrs remaining ]LOG]!><time="14:46:43.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 45 minutes (process ID 1568)]LOG]!><time="14:46:43.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 17% ] Capturing progress: 2:30:58 hrs remaining ]LOG]!><time="14:50:26.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 18% ] Capturing progress: 2:42:16 hrs remaining ]LOG]!><time="14:57:55.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 56 minutes (process ID 1568)]LOG]!><time="14:57:55.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 19% ] Capturing progress: 2:55:09 hrs remaining ]LOG]!><time="15:03:37.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 62 minutes (process ID 1568)]LOG]!><time="15:03:37.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 20% ] Capturing progress: 3:03:46 hrs remaining ]LOG]!><time="15:07:09.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 21% ] Capturing progress: 3:10:17 hrs remaining ]LOG]!><time="15:11:41.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 70 minutes (process ID 1568)]LOG]!><time="15:11:41.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 22% ] Capturing progress: 3:12:08 hrs remaining ]LOG]!><time="15:13:22.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 23% ] Capturing progress: 3:11:13 hrs remaining ]LOG]!><time="15:15:43.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 24% ] Capturing progress: 3:08:56 hrs remaining ]LOG]!><time="15:17:45.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 76 minutes (process ID 1568)]LOG]!><time="15:17:45.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 25% ] Capturing progress: 3:06:17 hrs remaining ]LOG]!><time="15:20:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 26% ] Capturing progress: 3:03:27 hrs remaining ]LOG]!><time="15:22:24.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 81 minutes (process ID 1568)]LOG]!><time="15:22:24.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 27% ] Capturing progress: 3:00:07 hrs remaining ]LOG]!><time="15:24:14.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 28% ] Capturing progress: 2:56:19 hrs remaining ]LOG]!><time="15:25:55.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 29% ] Capturing progress: 2:54:19 hrs remaining ]LOG]!><time="15:30:23.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 89 minutes (process ID 1568)]LOG]!><time="15:30:23.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 30% ] Capturing progress: 2:52:44 hrs remaining ]LOG]!><time="15:32:22.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 31% ] Capturing progress: 2:50:14 hrs remaining ]LOG]!><time="15:34:29.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 32% ] Capturing progress: 2:47:25 hrs remaining ]LOG]!><time="15:36:38.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 95 minutes (process ID 1568)]LOG]!><time="15:36:38.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 33% ] Capturing progress: 2:44:17 hrs remaining ]LOG]!><time="15:38:25.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 34% ] Capturing progress: 2:40:58 hrs remaining ]LOG]!><time="15:40:26.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 35% ] Capturing progress: 2:37:40 hrs remaining ]LOG]!><time="15:42:17.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 101 minutes (process ID 1568)]LOG]!><time="15:42:17.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 36% ] Capturing progress: 2:34:21 hrs remaining ]LOG]!><time="15:44:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 37% ] Capturing progress: 2:31:09 hrs remaining ]LOG]!><time="15:46:18.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 38% ] Capturing progress: 2:28:17 hrs remaining ]LOG]!><time="15:48:53.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 107 minutes (process ID 1568)]LOG]!><time="15:48:53.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 39% ] Capturing progress: 2:25:45 hrs remaining ]LOG]!><time="15:51:14.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 40% ] Capturing progress: 2:23:10 hrs remaining ]LOG]!><time="15:53:14.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 112 minutes (process ID 1568)]LOG]!><time="15:53:14.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 41% ] Capturing progress: 2:20:18 hrs remaining ]LOG]!><time="15:54:44.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 42% ] Capturing progress: 2:17:13 hrs remaining ]LOG]!><time="15:56:48.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 43% ] Capturing progress: 2:14:21 hrs remaining ]LOG]!><time="15:59:07.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 118 minutes (process ID 1568)]LOG]!><time="15:59:07.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 44% ] Capturing progress: 2:11:48 hrs remaining ]LOG]!><time="16:01:55.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 45% ] Capturing progress: 2:09:52 hrs remaining ]LOG]!><time="16:07:04.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 126 minutes (process ID 1568)]LOG]!><time="16:07:04.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 46% ] Capturing progress: 2:09:09 hrs remaining ]LOG]!><time="16:10:37.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 47% ] Capturing progress: 2:08:08 hrs remaining ]LOG]!><time="16:12:58.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 131 minutes (process ID 1568)]LOG]!><time="16:12:58.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 48% ] Capturing progress: 2:06:21 hrs remaining ]LOG]!><time="16:15:22.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 49% ] Capturing progress: 2:04:12 hrs remaining ]LOG]!><time="16:17:26.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 136 minutes (process ID 1568)]LOG]!><time="16:17:26.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 50% ] Capturing progress: 2:01:44 hrs remaining ]LOG]!><time="16:20:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 51% ] Capturing progress: 1:59:26 hrs remaining ]LOG]!><time="16:22:36.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 141 minutes (process ID 1568)]LOG]!><time="16:22:36.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 52% ] Capturing progress: 1:57:05 hrs remaining ]LOG]!><time="16:24:21.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 53% ] Capturing progress: 1:54:22 hrs remaining ]LOG]!><time="16:26:15.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 54% ] Capturing progress: 1:51:34 hrs remaining ]LOG]!><time="16:28:31.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 147 minutes (process ID 1568)]LOG]!><time="16:28:31.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 55% ] Capturing progress: 1:48:56 hrs remaining ]LOG]!><time="16:30:23.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 56% ] Capturing progress: 1:46:05 hrs remaining ]LOG]!><time="16:33:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 152 minutes (process ID 1568)]LOG]!><time="16:33:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 57% ] Capturing progress: 1:43:42 hrs remaining ]LOG]!><time="16:35:25.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 58% ] Capturing progress: 1:41:18 hrs remaining ]LOG]!><time="16:37:12.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 59% ] Capturing progress: 1:38:41 hrs remaining ]LOG]!><time="16:38:57.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 157 minutes (process ID 1568)]LOG]!><time="16:38:57.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 60% ] Capturing progress: 1:36:02 hrs remaining ]LOG]!><time="16:40:19.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 61% ] Capturing progress: 1:33:11 hrs remaining ]LOG]!><time="16:41:53.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 62% ] Capturing progress: 1:30:13 hrs remaining ]LOG]!><time="16:43:58.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 162 minutes (process ID 1568)]LOG]!><time="16:43:58.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 63% ] Capturing progress: 1:27:20 hrs remaining ]LOG]!><time="16:46:48.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 64% ] Capturing progress: 1:24:48 hrs remaining ]LOG]!><time="16:49:52.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 168 minutes (process ID 1568)]LOG]!><time="16:49:52.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 65% ] Capturing progress: 1:22:51 hrs remaining ]LOG]!><time="16:51:34.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 66% ] Capturing progress: 1:20:36 hrs remaining ]LOG]!><time="16:52:56.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 67% ] Capturing progress: 1:17:48 hrs remaining ]LOG]!><time="16:55:22.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 174 minutes (process ID 1568)]LOG]!><time="16:55:22.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 68% ] Capturing progress: 1:15:29 hrs remaining ]LOG]!><time="16:56:51.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 69% ] Capturing progress: 1:12:55 hrs remaining ]LOG]!><time="16:58:32.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 70% ] Capturing progress: 1:10:29 hrs remaining ]LOG]!><time="16:59:44.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 71% ] Capturing progress: 1:07:56 hrs remaining ]LOG]!><time="17:00:45.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 179 minutes (process ID 1568)]LOG]!><time="17:00:45.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 72% ] Capturing progress: 1:05:07 hrs remaining ]LOG]!><time="17:02:14.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 73% ] Capturing progress: 1:02:13 hrs remaining ]LOG]!><time="17:04:24.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 74% ] Capturing progress: 59:21 mins remaining ]LOG]!><time="17:07:21.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 186 minutes (process ID 1568)]LOG]!><time="17:07:21.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 75% ] Capturing progress: 57:19 mins remaining ]LOG]!><time="17:08:59.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 76% ] Capturing progress: 54:21 mins remaining ]LOG]!><time="17:12:43.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 191 minutes (process ID 1568)]LOG]!><time="17:12:43.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 77% ] Capturing progress: 52:42 mins remaining ]LOG]!><time="17:14:16.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 78% ] Capturing progress: 50:16 mins remaining ]LOG]!><time="17:16:48.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 79% ] Capturing progress: 48:22 mins remaining ]LOG]!><time="17:18:10.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 197 minutes (process ID 1568)]LOG]!><time="17:18:10.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 80% ] Capturing progress: 46:27 mins remaining ]LOG]!><time="17:18:47.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 81% ] Capturing progress: 44:11 mins remaining ]LOG]!><time="17:19:20.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 82% ] Capturing progress: 41:31 mins remaining ]LOG]!><time="17:20:31.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 83% ] Capturing progress: 38:07 mins remaining ]LOG]!><time="17:23:49.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 202 minutes (process ID 1568)]LOG]!><time="17:23:49.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 84% ] Capturing progress: 35:48 mins remaining ]LOG]!><time="17:26:06.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 85% ] Capturing progress: 33:25 mins remaining ]LOG]!><time="17:28:43.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 207 minutes (process ID 1568)]LOG]!><time="17:28:43.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 86% ] Capturing progress: 31:18 mins remaining ]LOG]!><time="17:30:54.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 87% ] Capturing progress: 29:37 mins remaining ]LOG]!><time="17:31:54.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 88% ] Capturing progress: 27:55 mins remaining ]LOG]!><time="17:32:07.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 89% ] Capturing progress: 25:04 mins remaining ]LOG]!><time="17:34:07.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 213 minutes (process ID 1568)]LOG]!><time="17:34:07.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ Console > [ 90% ] Capturing progress: 22:52 mins remaining ]LOG]!><time="17:35:22.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 91% ] Capturing progress: 20:47 mins remaining ]LOG]!><time="17:36:14.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 92% ] Capturing progress: 18:33 mins remaining ]LOG]!><time="17:37:14.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 93% ] Capturing progress: 16:14 mins remaining ]LOG]!><time="17:38:22.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ Console > [ 94% ] Capturing progress: 13:54 mins remaining ]LOG]!><time="17:39:40.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread=""
file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 218 minutes (process ID 1568)]LOG]!><time="17:39:40.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 224 minutes (process ID 1568)]LOG]!><time="17:45:04.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Return code from command = -1073741819]LOG]!><time="17:45:05.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Error creating an image of drive C:, rc = -1073741819]LOG]!><time="17:45:05.000+000" date="08-15-2014" component="ZTIBackup" context="" type="3" thread="" file="ZTIBackup">
<![LOG[ZTIBackup COMPLETED. Return Value = -1073741819]LOG]!><time="17:45:05.000+000" date="08-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ZTI ERROR - Non-zero return code by ZTIBackup, rc = -1073741819 0xC0000005]LOG]!><time="17:45:05.000+000" date="08-15-2014" component="ZTIBackup" context="" type="3" thread=""
file="ZTIBackup">Not sure what's going on here. Possibly a corrupt drive? Or the target drive is full?
Try running the imagex command manually from a F8 cmd window (in WinPE)
"\\OCS-MDT\CCBShare$\Tools\X64\imagex.exe" /capture /compress maximum C: "\\OCS-MDT\CCBShare$\Captures\CCB01-8_15_14.wim" "CCB01CDrive" /flags ENTERPRISE
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com -
MDT 2012 'Failed to save Environment to (80070057) Error during Windows 7 x64 Pro Deployment
Hi There,
I've been using MDT for a little while now, but I'm having problems successfully deploying an image to a batch of new laptops. The laptop HDD's are completely blank, and I am PXE booting using an x64 Litetouch Image via WDS. I have successfully captured
my image from a reference laptop (the same model that I'm trying to image), and I am now trying to deploy it using a standard client task sequence.
The 'Install operating System' phase seems to go ok, but then sits for quite some time at the 'Applying Unattend.xml' stage, then eventually, I get a general error 'Task Sequence Failed - 80004005'. I then exit MDT (it doesn't reboot as it should), and let
the laptop boot, which it does, and logs straight on into Windows, but gives me error along the lines of 'can't find the litetouch script', which I assume means MDT hasn't been able to copy it across. The laptop is however joined to our domain, and I pretty
much just have to tick the 'require a password to log on to this computer' box in user accounts, and all looks ok.
So in summary, the image is applying, but the laptop is not rebooting and running the final cleanup scripts.
I have already changed the SATA mode to IDE, instead of AHCI, having read this sometimes causes problems. I also read that systems with UEFI BIOS can also cause problems with MDT, but I'm not sure if this is the case.
I have edited my customsettings.ini, to copy log files back to my server, which it has done for me. Having looked at the logs (with CM Trace), I can see these errors:
Failed to save environment to (80070057)
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows)
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Failed to persist execution state. Error 0x(80070057)
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Failed to save execution state and environment to local hard disk
TSManager 26/03/2014 15:48:09
1820 (0x071C)
The task sequence execution engine can not reboot the machine because we failed to persist execution environment
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Fatal error is returned in check for reboot request of the action (Restart computer).
Unspecified error (Error: 80004005; Source: Windows)
TSManager 26/03/2014 15:48:09
1820 (0x071C)
An error (0x80004005) is encountered in execution of the task sequence
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Task Sequence Engine failed! Code: 80004005
TSManager 26/03/2014 15:48:09
1820 (0x071C)
Any help you can give me would be great, as I'd like to get this process running properly.
Thanks,
SarahYou don't mention what kind of OS this is (Windows 7 Pro x64?)
This is a known issue/FAQ.
I would recommending using MDT 2012 (update 1) for UEFI machines.
Machines with uEFI 2.3.1 only support Windows 8.x.
http://technet.microsoft.com/en-us/library/hh824898.aspx
Recomendation: Convert the BIOS to CSM and/or upgrade to Windows 8.1 :^)
Keith Garner - keithga.wordpress.com -
MDT 2012 Litetocuh Deployment Failed, Return Code = -2147467259 0x0004005
Here is what I have tried. I have tried recreating the DeploymentShare. Moved my Deployment Test Share to the standard 2008 Server running MDT 2012. I have setup a Win7 x64 box as the Deployment Manager. I am still getting the following error:
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Copy OEM files.
Incorrect function, (Error: 00000001; Source: Windows)
The execution of the group (Install has failed and the execution has been aborted. An action failed.
Operation abourted (Error: 80004004; Source Windows)
Failed to run the last action: Copy OEM files, Execution of task sequence failed.
Incorrect funtion. (Error: 00000001; Source: Windows)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005
Recreated the Image, Task Sequences, CS.ini and Boot.ini) Incorporated all OOB Drivers, Packages. Using
a USB 16Gb flash drive with LiteTouchx86.
List last time we tried to create a separate deployment share. Copy all the preexisting data from a working known good deployment share with images, task
sequence, cs.ini and all image files. Still getting the same issue.
Finally checked some of the Google, technet and forums for any assistance but non seem to do the trick.
I'm new to the process but have been working with a fellow tech who has been working with MDT for six months and he can not find the issue either.
Thanks for all your help up front.Can you post your log files?
IT Support " Scripting Noob " -
I am having trouble trying to capture a new Windows 8 image with WDT 2012.
My Setup -
Server 2012
WDS
MDT 2012
Windows 8 ADK
Hyper-V
I have created a new task and I can get the image to successfully deploy the image to a VM but it seems to fail at the Restore User State task.
Once the install Applications task has finished I added a Suspend task so I could customize the image a little. Upon resuming the task sequence is where the above failure message appears. I can see it gets to the next step (which is 'Restore User State')
but that seems to be where is crashes.
Does anyone have any advice on what I might be doing wrong or what I can do to resolve the above issue?WAIK being installed was probably your issue so I wouldn't bother disabling the restore task. It is used to migrate user data, docs, and settings on refreshes, not new builds. It doesn't affect CopyProfile, just note that data will be migrated on refreshes so
some aspects may change, ie wallpaper, shortcuts, etc but what gets migrated with USMT can also be configured.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ” -
MDT 2012 Errors - Won't Run My Windows 8.1 Activation Script/Task Sequences Fail
Hello all,
I've been using MDT 2012 for a while now to image machines in our environment with success for the most part. Just recently, however, I've been running into issues at the point where the deployment is supposed to be activating Windows where it will just fail the deployment. It outputs a number of errors, including:TextWindows cannot remove Microsoft.VCLibs.120.00_12.0.20812.1_x86__8wekyb3d8bbwe because the current user does not have that package installed. Use Get-AppxPackage to see the list of packages installed.NOTE: For additional information, look for [ActivityId] 5f3738f0-b9a2-0001-0581-375fa2b9d001 in the Event Log or use the command line Get-AppxLog -ActivityID 5f3738f0-b9a2-0001-0581-375fa2b9d001]LOG]!+ Get-AppxPackage -AllUsers | Remove-AppxPackage+ ~~~~~~~~~~~~~~~~~~]Which I'm familiar with because I've seen this...
This topic first appeared in the Spiceworks CommunityHi,
Thanks Again for taking a look.
I checked the sysprep log in the image and they look fine. No errors.
As requested here are some logs. Let me know if I can provide anything else.
BDD.log
litetouch.log
SMSTS.log
Im not actually attempting to provide a recovery image. What I am doing is leveraging MDT to refresh the computer remotely. We can update the MDT media on the hidden data partition,when required and kick it off remotely. Some of the computers are very
remote, and without SCCM DP's, plus a combination of slow links and a lack of deskside techs made this a requirement. This works without incident.
The only issue I have is on a new computer if I run the sequence (offline USB media) it will fail the first time, unless I run a diskpart clean in PE first.. Then it will succeed. Refreshing the computer is fine. -
Deployment Failure - thick image - (5627) dism.exe (MDT 2012 Update 1)
I installed MDT 2012 Update 1 on a new server and was testing it out with our Windows 8 deployment. I captured a thick image which works fine when I boot to Win PE and apply it using dism.
I imported the image into the the deployment share (custom, no setup/sysprep) and created a Custom Task Sequence with just 3 tasks to do a custom format (command line using dism), apply the image (choose specific disk and partition), and restart the computer.
However, when I go through the task sequence, it comes up with some errors and appears that it gets sysprepped again because it prompts me to answer questions that weren't a part of my original sysprep (EULA, adding a new user, etc).
Any idea where I need to look to get this fixed? I've shared the BDD.log and LTIApply.log on my SkyDrive.
https://skydrive.live.com/?cid=0FB4C394CC7A79E1&id=FB4C394CC7A79E1%21105
Here's a snip of the results
<![CDATA[FAILURE (Err): 53: Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml - File not found
FAILURE ( 5627 ): 2: Run DISM.exe
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System.
Unknown error (Error: 000015FB; Source: Unknown)
Failed to run the action: Install Operating System. Execution has been aborted
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015FB; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]]>
Please advise.
Thanks in advance.I installed MDT 2012 Update 1 on a new server and was testing it out with our Windows 8 deployment. I captured a thick image which works fine when I boot to Win PE and apply it using dism.
I imported the image into the the deployment share (custom, no setup/sysprep) and created a Custom Task Sequence with just 3 tasks to do a custom format (command line using dism), apply the image (choose specific disk and partition), and restart the computer.
However, when I go through the task sequence, it comes up with some errors and appears that it gets sysprepped again because it prompts me to answer questions that weren't a part of my original sysprep (EULA, adding a new user, etc).
Any idea where I need to look to get this fixed? I've shared the BDD.log and LTIApply.log on my SkyDrive.
https://skydrive.live.com/?cid=0FB4C394CC7A79E1&id=FB4C394CC7A79E1%21105
Here's a snip of the results
<![CDATA[FAILURE (Err): 53: Copy File: C:\MININT\unattend.xml to C:\Windows\Panther\Unattend.xml - File not found
FAILURE ( 5627 ): 2: Run DISM.exe
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Failed to run the action: Install Operating System.
Unknown error (Error: 000015FB; Source: Unknown)
Failed to run the action: Install Operating System. Execution has been aborted
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015FB; Source: Unknown)
Task Sequence Engine failed! Code: enExecutionFail
Task sequence execution failed with error code 80004005
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005]]>
Please advise.
Thanks in advance.
Hi Mathew,
I have the similar error deploying a image (no sysprep) using the standard client task sequence. There are 2 partitions, one 500MB for boot and the other remaining partition is for OS. Do you have solutions to resolve the errors? Greatly appreciate
any advice given. Thanks.
Regards,
Eng Chai
Eng Chai -
MDT 2012 deploy OS from USB external drive failed - need to unplug and plug it once again
We are using MDT 2012 and deploying Windows 7 using media (USB external hard drive). We can successfully deploy Windows 7 32 bit using this method but there is a problem with deploying Windows 7 64bit. This problem appears only on HP EliteBook 840. We can
boot into WinPE 64 bit and can start proper task sequence, all image is applied then after restart, before logon screen appears there is an error saying that cannot find litetouch.vbs script. After clicking ok, I can logon to Windows and there is no usb external
drive recognized. But when I unplug and plug usb drive once again it is recognized by Windows and can be used. I can see that Windows install some drivers just after plug it again
I checked BIOS looking for some USB power options - there is no such settings. And 32 bit deployment works ok. So this is not a case. Looks for me like a problem with proper usb drivers for 64 bit. I download all drivers from HP website (driver pack and
drivers only for USB 3.0). We are using make and model matching in MDT - works ok for all the rest hardware models. Any idea how to troubleshoot it?Not sure what's going on here. Is this a USB "Flash" drive or a USB "Hard Drive". There *Is* a distinction.
I *thought* that MDT would copy itself to the c:\minint\scripts folder to continue installation.
Next time, when you see this error, Press Shift-F10 to get into a cmd.exe prompt. Can you find litetouch.vbs on any of the drives? Does the USB Drive appear?
IF in fact, the USB Drive is not appearing after the 1st reboot, then you have a problem. Why did the USB 3.0 driver not install. Check the Driver Installation Logs to verify.
Keith Garner - keithga.wordpress.com -
WDS & MDT 2012 Integration Questions: Do I need an install image on WDS if I'm multicasting from MDT
I'm running WDS & MDT 2012 on Server 2012 for my deployment solution. I have a few questions about what happens when you integrate WDS & MDT.
Perhaps this is a simple question, but if WDS multicasts the installation image from MDT, do I need to have an image in the installation folder of WDS? I have the "Enable multicasting" box checked whenever I update my deployment share
Also, my server is running X64 architecture, so I have the x64 WAIK installed. but I'm having issues editing the unattend.xml on my server because my images are all X86. Keeping in mind that I already have the X64 WAIK installed, can i install
the X86 WAIK tools on my server?Sorry, that's two questions you only get one... Just kidding...
FOr MDT, you don't import the images into the WDS console, you just need to add a Multicast namespace.
http://keithga.wordpress.com/2014/04/23/multicasting-with-mdt/
AS for the unattend.xml edit issue, that is known:
http://blogs.technet.com/b/deploymentguys/archive/2009/08/27/windows-7-waik-and-custom-images.aspx
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com -
MDT 2012 Win7 x64 capture fails - boot loop
Hi everyone,
I'm pretty new to MDT and having a problem capturing a Win7 x64 reference image.
It seems to start out fine doing the Sysprep and so on, but then it has to restart the computer and after that it goes into a boot loop. After this, I have been forced to format and reinstall Win7 on the computer. This picture shows what it loops through
in about 20 seconds - and it shows nothing else than what's on these pictures :)
www.jaded.dk/boot_loop.png
I have been Google'ing alot, but can't find any post with the same issue, since most other get an error msg which I dont.
Here is some info about the setup.
I'm deploying the task sequence locally using these commands:
net use * \\mdtserver\DeploymentShare$ /user:domain\username
cscript \\mdtserver\DeploymentShare$\Scripts\LiteTouch.wsf
Server running MDT 2012 U1 - Win server 2008 R2, 64 bit
The laptop on which i'm trying to capture the ref img is a HP Elitebook 8470p. It is fully patched with windows updates and I have installed a few apps like Office 2010, flash player, reader etc.
The "Rules" on my MDT Workbench is like this:
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
SkipTimeZone=YES
SkipLocaleSelection=YES
InputLocale=0406:00000406
KeyboardLocale=0406:00000406
KeyboardLocalePE=0406:00000406
SystemLocale=0406:00000406
UILanguage=0406
UserLocale=0406:00000406
My task sequence looks like this:
www.jaded.dk/task_seq.png
I don't know where to find a log of the capture, to get a hint of what has gone wrong.
Hope you can help me out here :) And please let me know if you need more info.
Thanks
MortenThank you both for answering.
ccatlett_sogeti:
I didn't seem to have Windows Deployment Services installed on my server. I just installed it and added WinPE boot files as bootimage according to this guide: http://blogs.technet.com/b/manojnair/archive/2011/11/23/exploring-mdt-2012-beta-2-part-6-of-10-integrating-mdt-2012-beta-2-with-windows-deployment-services-wds.aspx
Is that correct?
Keep in mind that I don't use PXE at the moment, if that makes any difference :)
David:
I will try to add SLShareDynamicLogging. I set it like this - hope it's correct:
SLShareDynamicLogging =\\MDTSERVER\DeploymentShare$\Logs\%ComputerName% -
Using MDT boot image in SCCM 2012
Hi,
I want to import MDT boot image in SCCM 2012. Please let me know if this is possible.
I have integrated all the driver in it and want to use from SCCM.
Any suggestion on this?
Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"These two blogs explain this process very very well.
http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/
http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson
Maybe you are looking for
-
I am working in text edit and cannot open my file. Error message says it is in the wrong format, truncated or corrupted. what to do?
-
New imac doesn't locate old imac hard drive via usb port
I have an old iMac from ~2006 that recently stopped reading the harddrive. I pulled the HD out and connected it to my new imac via USB port but I can't locate it. The HD spins/powers up so I know the connector is strong enough to supply power. We
-
Can I import 2 sets of photos with the same file name numbers?
I've inadvertantly not had my camera set to "continuous" for file names and now have 2 memory cards with 2 different sets of images with the same file names. Can I still import both into Lightroom 2 without problems? What are the consequences? Thanks
-
When I setup my account for itunes connect I did so with what was my then current LLC and for ebook publishing. But, now I have anewer LLC that I would like to use and I also want to use the account for app publishing. Unfortunately the help systems
-
Hide document or posting date?
in fb50 screen there is a posting date and document date is there any way to hide any one of them coz the users forget to change both of them (change one of them and forget the other)