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
Morten
Thank 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%
Similar Messages
-
Win7 x64 install fails at boot with alternating Mac and Cross-Circle Logo
Thanks for reading.
I have a new late 2009 i7 2.6Ghz Macbook (6.1 model) that I purchased in February this year. I'm having real problem trying to get a Windows 7 DVD to boot on it; whenever I try (either by using the bootcamp assistant to parition my drive then start the boot process, or by holding down the OPTION key, or even using the C key at boot) instead of the normal Windows 7 boot process, the disc spins, then I am left with an alternating Apple logo with a circle with a angled cross line through it, sometimes showing a folder with a ? mark.
I have tried resetting the PRAM, using other Windows 7 media, but I just can't seem to get a disk to boot. I have even tried wiping my Mac parition in case it was a corrupt partition by backing up to a timedesk then reinstalling, but again when I come to install Windows 7 I get the same problem.
I can boot the Mac OS install disks not problems.
Really appreciate if anybody has any guidance or resolutions?Hi - no nothing plugged, except my external DVD drive.
I managed to install TechTool Pro's emergency EDRIVE from DVD, and have managed to reinstall Mac OS X without any problems, so unsure about a hardware problem. All TechTool tests come back ok, so no issues seem visible from that.
You might be thinking why I am using an external DVD; well this is because I've taken out the internal DVD using OWC Datadoubler http://eshop.macsales.com/item/Other%20World%20Computing/DDAMBS0GB/
I have a 512GB SSD in the normal hard drive space, and a 500Gb Hybrid disk where the DVD drive was. The drives are seen perfectly well in Max OSX; indeed when I did a reinstall I used the 2nd internal hard disk as the time machine and then restored from it.
Could it be a problem with partitions or some issue with the EFIboot from the Windows 7 DVD's? I've tried looking at rEFIit http://refit.sourceforge.net/ to see if that would help, but no luck.
The data doubler shows examples of this being used in my mac model for a specific Windows implementation (which is why I bought it) so don't think its that. Anybody have any ideas? -
Thinkpad 10 SCCM 2012 R2 x64 WINPE OSD boot wim
Trying to inject drivers in to my CM12 x64 boot wim (ADK and MDT 2013 integration with CM12) for the new Thinkpad 10 Tablet. The x86 worked flawlessly and touch screen works on the x86 builds even my S1 Yoga. Errors galore with the x64 versions of the drivers from the SCCM pack. Being UEFI boot only both versions are needed and not all my locations will have the dock for using a keyboard so touch just needs to work.
Here is what successfully got added,the 2 display drivers and thats it. I started with all the drivers and worked in reverse by removing each driver after every error.
from SCCM:
Success: Drivers that will be included:
Realtek USB GBE Family Controller
Lenovo USB2.0 Ethernet Adapter
Intel(R) 5 Series 4 Port SATA AHCI Controller
Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
Intel(R) C600 Series Chipset SATA AHCI Controller
Realtek USB GBE Family Controller
VMware Pointing Device
VMware USB Pointing Device
VMware PVSCSI Controller
VMware SVGA 3D
VMware VMCI Bus Device
vmxnet3 Ethernet Adapter
Intel(R) HD Graphics
ThinkPad Display 640x480
Realtek USB GBE Family Controller
Any help is appreciated and parkerj, as usual I am willing to be your huckleberry if needed. On a unrelated item any tips for removing the lenovo scup data from my wsus/scup environment? We had an issue and now i cannot publish the data. Whick makes me sad as I think the Lenovo SCUP catalog shows good progress. Primary issue is knowing what applies to what without publishing everything.Hi,
UEFI BIOS Version: GWET23WW (1.23)
I have managed to implement drivers in a different way. I have created a package containing all drivers and placed it in a part of task sequence running inside installed operating system instead of running in WinPE. There is a script inside a package looking like this:
Start /w .\win\Chipset\setup.exe -s
Start /w pnputil -i -a .\WIN\TXEI\INF\TXEI.inf
Start /w setup.exe -SILENT
Start /w .\WIN\Audio\setup.exe /s
Start /w .\WIN\Bluetooth\setup.exe /s
Start /w .\WIN\Fingerprint\WBF_SPI_DDK_Extended_Setup.exe /s
Start /w .\WIN\GPS\setup.msi /qn
Start /w .\HOTKEY\setup.exe /S /B /H
pnputil -i -a .\WIN\MONITOR\TPLCD.INF
Start /w .\WIN\NFC\setup.exe /s
Start /w .\WIN\PMDriver\setup.exe -S -SMS
Start /w .\WIN\WLAN\setup.exe -s
reg import .\OSFIXES\ALSOR\ALSOR_Apply.reg
For anyone interested just make sure you follow correct paths to executables as presented in this script.
After running it I am left with Security Device unrecognized in Device Manager so I have to add another task sequence for Restart and than another one with a line with a package for Security Device and runing this as a command: pnputil -i -a TXEI.inf
Using regular pre-driver deploy task sequence commands in WinPE enviorenment unfortunately didn't helped so I have ended with workarounds presented here.
If anyone can add something to this I will be more than glad to hear. -
MacbookPro 5,4 - Failure(s) installing Win7 x64 using Bootcamp (aka help!)
I'm running a Macbook Pro 5,4 and am having a hard time figuring out why Win7 x64 keeps failing during the install process. I'll start with the failures, then add what I've attempted to fix the problem.
Following the Bootcamp guide exactly, I get through the initial copying, expanding and updating process just fine. The system reboots but never makes it into windows. Instead I get the, "Windows failed to start. A recent hardware or software change might be the cause." Sometimes it lists a driver (the list is long and seemingly random). Sometimes it lists the kernel (ntoskrnl.exe).
My attempts at a solution:
1. The recommendation from MS is to boot to the install disk and run a start-up repair. When I do this, it returns the message, "Startup Repair cannot repair this computer automatically". Dead End.
2. Because it looks like a possible corruption issue I first tried the cheap route of installing from another disk - in fact I've borrowed two other Win7 Pro x64 disks (all 3 disks I've used are legitimate) and have had the same problem, so I'm ruling out the media.
3. The system is less than two months old but it could still be the HDD so I ran a check in OS X and it finds no problems. I've replaced the drive twice and the problems with installation remain consistent.
I've run a check on the memory as well - again, no problems detected.
So far I've completed 9 attempts, with fresh partitioning and formatting and have yet to successfully install Windows 7 on this system. In contrast, it was a simple process to install the 32 bit version on my wifes MacBook Air. Am I missing something obvious?Found a workaround, to sum it up, it's pretty much my dead internal superdrive (as for unbootable USB, that's still a mistery). What I did was moving the HDD to my 2012 MBP and install from there. The problem is now that since I installed it on another machine (with ofc all different hardwares) I got blue screen whenever I tried to start Windows7 (in 2007 MBP after moving the HDD back there).
Next step will be replacing the superdrive on 2007 MBP with 2012's. Or if someone got a suggestion like installing the drivers via target disk mode etc, please advice -
Mdt 2012 + WDS service on the same server. DHCP question
Hi,
I am using MDT 2012 on Server 2008.
Boot images are placed on 6 years old WDS server running on 2003.
I need to remove WDS server (2003).
Cannot find exact instructions for enabling PXE for MDT2012.
I don't need introduction guides. But clear few lines of instructions.
From quickly checking web I understand that I need:
1. install WDS services on the same MDT2012 server 2008.
2. import Lite Touch boot images from Deployment Share
The only point I am missing is DHCP question. In Microsoft prerequisites for WDS services, DHCP should be present on the same server were WDS is...
I watched one video on web and the guy just installs WDS on the MDT server and not mentioning DHCP at all.
Sure that there is DHCP server serving multiple subnets on the network.
My confusion about DHCP on WDS prerequisite comes from not having DHCP services installed on old WDS 2003 machine.
So why it is required on WDS service in server 2008/2012?
Can somebody confirm that DCHP must exist on the same server were MDT and WDS services are enabled.
And is it a valid option to have all 3 on one Server machine if DHCP is really needed for enabling PXE in MDT environment?
I saw the info about ports 67 (should be disabled) and 60 for PXE enabled.
Will appreciate DHCP part explanation and how to...
Thanks.
"When you hit a wrong note it's the next note that makes it good or bad". Miles DavisRL69,
in my environment DHCP serves multiple subnets. For now no need to serve client machines on different subnets. The Deployments will be done on subnet were MDT resides. If necessary PXE relay could be enabled on Core switch (or where necessary).
So if I understand correctly for a scenario above all what I need to do for PXE enabled MDT is:
to add WDS role/service on the same MDT server and import boot images.
Right?
Will do it right after your confirmation :)
"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis -
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 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: -
MDT 2012 Update 1 - Attempting to capture Windows Thin PC but it keeps looping after reboot.
I have been trying to capture a master image of Windows Thin PC we have prepared using MDT 2012 Update 1 but to no avail. When attempting the capture process using LiteTouch.vbs it syspreps and then reboots as it normally would and then it simply keeps rebooting
over and over in a loop.
I am unsure of how to bypass this and correctly capture Windows Thin PC using MDT 2012 Update 1. If anyone has any advice or feedback they can offer I would greatly appreciate it. Thank you.Logs suggest that the script is most likely crashing early on.
I suspect that the reason for this is that the deployment share was *updated* from a previous version of MDT, and some files are out of date.
Can you update the share (full update, regenerate from scratch?)
Otherwise we may need to run Litetouch.wsf manually from within WinPE:
When WinPE Boots and you have a mouse, press F8.
Run TaskMgr.exe and verify that wscript.exe is no longer running (wait 2 minutes).
Then run the following command:
"cscript.exe x:\deploy\scripts\litetouch.wsf /debug:true /debugcapture"
That should run the litetouch.wsf script and it should display any errors if found.
Keith Garner - keithga.wordpress.com -
Win7 capture failing at WinPE 0xc000000d
Hello
I currently have multiple Win7 x64 virtual machines that I use for capturing at the start of each year. I currently have an issue where no of them will capture, giving the same error.
I run the litetouch.vbs on the virtual machine like I have always done. I complete the wizard, choose the Capture task sequence I've set up and used previously, fill in my credentials and name the .wim that will be created. The wizard then finishes and the
lite touch process starts. It gets to the point where the system restarts and goes to boot into WinPE for the image to capture. It's a black screen with a white bar with a message above saying "Windows is loading files..."The issue appears once the
system has completed the loading phase and is about to boot into the WinPE environment.
The error that occurs is below:
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1.Insert your windows installation disc and restart your computer.
2.Choose you language settings, and then click "next"
3. Click "Repair your computer."
If you do not have this disc, contact your system administrator or computer manufacturer for assistance.
Status:0xc000000d
Info: The boot selection failed because a required device is inaccessible.
I can't recall any changes I've made on my server that could relate to this. I have made sure permissions are correct and that the share is configured correctly. This message comes up on all VM's I have so it is a server side issue and not a individual VM
issue.
If I select enter, I'm prompted to choose between 2 operating systems, a "Ramdisk Device Options" and a "Windows 7" option. The Ramdisk just loops me back to the white bar and loading of files and the Windows 7 option starts to boot back
into the operating system.
Any help would be appreciated as I'm out of ideas.
Thanks
BeauThanks for the reply DiWuNewFolder
I'm currently running my WDS setup from a Server 2012 R2 VM. I've increased the memory for the VM I'm trying to capture to 8GB but it still produces the same error.
I've had a look at the LiteTouchPE_x64.iso file and it is "2.08 GB (2,243,663,872 bytes)". Once I have updated the boot image inside the WDS server, the expanded size is 7941MB. If this is an issue, how do I reduce the PE image size?
I had been looking through this forum for a solution and in another thread someone mentioned mounting the LiteTouchPE_x64.iso directly to the VM from Hyper-V, which I did and I was able to complete the capture of the VM this way. After the VM sysprep'ed,
it would restart and boot off the CD I mounted. It looked like it normally does so I'm not sure what this points to exactly. -
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 " -
User State Migration Data Capture Failure MDT 2012 Update 1
Hello All
Trying to capture data on a Win7 x64 machine so that I can keep the data and restore once the computer is done re-imaging. This is an offline MDT deployment on the same computer. See the error below:
CNAME loop detected. (Error: 000025EB; Source: Windows)
Using MDT 2012 Update 1Lots of good information out there. Even stuff that says it's for MDT 2010 also applies to MDT 2012 Update 1 for the most part. Here's a few to get you started:
http://deployment.xtremeconsulting.com/2009/11/20/understanding-usmt-with-mdt-2010/
http://technet.microsoft.com/en-us/magazine/jj127984.aspx
http://blogs.technet.com/b/mniehaus/archive/2009/07/01/mdt-2010-new-feature-12-usmt-4-0-hardlink-support.aspx
http://www.windows-noob.com/forums/index.php?/topic/3758-usmt-mdt/
http://channel9.msdn.com/Events/MMS/2013/DC-B301 (great video with Johan presenting, focused on USMT 5.0)
You should create a default Standard Client Task Sequence and look at the State Capture and State Restore groups to see what MDT sets up for you by default that you may have removed from your current Task Sequence. But the direct answer to your question,
is that ScanState (part of USMT) is the part that creates a backup. LoadState is the piece that restores it to a machine.
David Coulter | http://DCtheGeek.blogspot.com |
@DCtheGeek -
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 -
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 -
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×80004005Thank 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. -
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. ”
Maybe you are looking for
-
Mail for Exchange System Error, try again later. F...
my E71 running S60 Mail For Exchange works fine for email, but as soon as we start syncing calendar, we get this error "System Error. Try again later" i have researched further. The phone log shows the sync falls over on outlook recurring appointment
-
Acrobat 9 Pro requires admin password every time it opens?
Ever since a recent upgrade, my Acrobat Pro wants a password "to make changes" just to open. I don't want to make changes, I want to open the app. A similar question elsewhere in this group has not been answered. thanks
-
Issue with characters like u0151 in maintaining text
Hi, When characters are entered as per HU language, we face trouble with characters like ő Ő into text fields like in sales order. As soon as this letter is entered, it is changed to 'O' as in EN language. changing -> Options-> Character set -> Centr
-
Configuring wireless card Cisco Aironet 350 PCI
I'm not a newbie in linux but now faced with a trouble. I could not manage to set up the card properly. I just installed Arch 0.8 and it's not quite clear to me how to do this with Arch. I've read all available Arch's docs on this topic. So my situat
-
Dear All, This below program will generate a list of PR with a check-box beside it. User can select the PRs and then click on the Create PO/Create RFQ button. The contents in the PR will be transferred to the PO/RFQ. The user will check the contents