MDT 2012 bypass choosing image to deploy
hello
is there any parameter in customsetting.ini or anywhere else where we can specify image we want to deploy to avoiding it in the MDT console
thanks
In CustomSettings.ini:
SkipTaskSequence=YES
TaskSequenceID=%tasksequenceID%
This will skip the task sequence selection pane in the wizard and deploy whatever image is associated with the task sequence ID you've specified. Please note this will automatically choose a task sequence and not an image, per se.
-Nick O.
Similar Messages
-
MDT 2012 - Some Batches Break During Deployment
I've been using MDT 2012 for a while now and I have my list of applications to choose from. All my apps and just a batch file that does the installation/configuration. Nearly everything works just as expected with the expection of two batches. The first
one activates Windows. The second uses the HP System Software Manager to under the BIOS and drives. If I manually run these batches after MDT in finished deploying windows then everything works just fine. But if I try to run them with MDT, they batches
just sit there and hang.
Has anyone experienced an issue like this? I would think that running a .bat via MDT would be the same as running it as administrator, but the reality seems to be different.There are several things that can cause a batch script to appear to work in one scenario, and fail in another.
I do recommend adding some logging to ensure that you understand the root cause here.
Add some logging to the start of your batch script.
@echo Hello World, I am running. YEA! %~f0 %date% %time% >> %temp%\Testing.log
This should tell you if MDT successfully passed control over to the *.cmd batch script program.
Then you can look to see if you are calling the script correctly, or if your batch script has a bug.
Keith Garner - keithga.wordpress.com -
MDT Capturing an new image after deployment
Hi
I have captured a reference image and deployed it. I edited the custom.ini file and bootstrap to have practically zero touch deployment. I did find that I had to connect to the mdt server and run litetouch.vbs to capture the image from the reference
machine. My question is once the deployment was done I wanted to capture a new image from a new reference machine and wasn't able to do it when running litetouch.vbs. It would through out an error of cant find ini. I uninstalled mdt and reinstalled it with
adk and can now capture again. Is there another way? I don't want to have to uninstall mdt each time. Is this because I edited the custom.ini file ?
ThanksHi Bronty12,
Base on my experience, your issue may caused by need to clean MDT, please refer the following thread solution first and there have a specific form to support the MDT issue,
you can ask in that forum there will more MDT expert to support you.
Dirty Environment found
https://social.technet.microsoft.com/Forums/en-US/36ed037b-51b1-4053-a248-46bd3ac9ecda/dirty-environment-found
MDT support
forum:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
Thanks for your understanding and support.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
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% -
MDT 2012 with Database do not use the OSD* properties
Greetings,
I use MDT 2012 Update1 with Database to deploy clients. without use SCCM, and without DHCP.
I find that the all the properties in the details settings begin with OSD**, such as "OSDComputerName", "OSDAdapter0Gateways", "OSDAdapter0IPAddressList"
etc. cannot be used.
for example, if I set the "ComputerName" as "Client1" and set "OSDComputerName" as "Client01" in the database, after the client installed, the client's Computer Name
is set to Client1 but not Client01.
and the client's IP address is not use the value in OSDAdapter0IPAddressList, but use the IP address that in the Boot WinPE begining screen I inputed.
would you please help me in this case.
Thanks
Frank@Hiweb 冯立超@瀚博资讯Thank you Michael,
Glad to get help from you!
I have according to you guide "Manipulating the Microsoft Deployment Toolkit database using PowerShell" created
a script to bulk input clients settings just now. thank you!
I have a question about IP address, as following:
I use MDT 2012 with Database, without SCCM, without DHCP.
so I must set IP address at the beginning of the WinPE.
thus, the final IP address on the clients is the IP address I set at WinPE boot time, but not the IP address in the Database
OSDAdapter0AddressList, even I set OSDAdapterCount to 1.
would you please guide me how to correct it.
Thank you and best regards.
Frank@Hiweb 冯立超@瀚博资讯 -
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 -
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- Can no longer deploy images: Unattend Answer file-for pass specialize....
Hello again.
I've got a recently captured Win7 Pro x64 image (successfully captured) via MDT 2012. It has baked in: IE11 and Office 2013 /sp1 and a few misc small prg's, like CCleaner and MWB for example.
I created a new TS to deploy it and ONLY unchecked the "Apply local GPO".. and just before it completes, I'm greeted with the following error: (Hope I can link)- if not: It's the "WIndows could not parse... c win\panther\unattend..for pass
[specialize] error....
http://img.photobucket.com/albums/v211/Marginjoey/ParseError_zps2d9d2105.jpg
I know I caused this. When my original image wouldn't capture with IE 11, I was advised that IE 11 was likely the issue (and maybe still is?) So, I believe my issue still sits in this possibly ill-advised change I made ..
Edited the UNATTEND.XML.. under ‘Specialize’, ‘amd64..ie-InternetExplorer_neutral’, then went into ‘IE WELCOME MESSAGE’ and Right-clicked to uncheck ‘Write Image Value’, then altered TRUE to FALSE on the same line. Even though I’ve been back to the default
settings more than once (and right now, back to default) I continue to have this PARSE/Specialize error. All of my settings files are default at the moment. I was using the SKIPPBDD-WELCOME for a bit, but it didn't help, so I removed it.
So, even though I'm back to default in this SPECIALIZE step, is there something else I can do to get around this? Time is of the essence like never before. (Frankly, I'm losing it.. I've been imaging/capturing/ and deploying numbering easily in the
30's and 40's...More info:
What just happened: I went into my DS$, and into my newest DEPLOY MARCH5 TS, and checked the UNATTEND.XML, did it take so long to open? Did it just create a new one? Is it based off the settings I chose in the TS? Is it a NEW default
copy?
Please help Obi-Wan Kenobi, you're my only hope. ;) -
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 -
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 -
Dell Laptops E7440 & E7240 - Issues with connecting to MDT 2012 deployment share
Hi,
Good afternoon.Need help on this please
-Test laptops Iam using are 2 * E7440 and 1*E7240. One laptop of model E7440 has our image installed and other two (1*E7440 & 1*E7240) are shipped from Dell with default Win 7 64 bit OS.
-Test desktops Iam using are Dell Optiplex 3020 & Dell 3010 . Both models have our own images of Win 7 64 Bit.
-Laptops and desktops are on same network .
-For OS deployments we have MDT 2012.
-While there are no issues with desktops, all the laptops mentioned above don’t connect to MDT deployments share . The detailed error message I get when I run a litetouch ISO is ‘A connection to the deployment share could not be made. Connection OJ.Possible
cause:invalid credentials. Retry : Try again to connect to the deployment share.’
-Have injected all possible network & storage drivers mentioned by Dell & Intel into MDT boot image but the problem still persists. Still WinPE doesn’t detect network adapter wherein IPaddresses are not picked in WinPE mode.
-Have been testing each and every driver by manually loading them into Winpe mode to see if they pick up the IP addresses and I finally found one driver by name ‘e1d63x64.inf ‘ which I downloaded directly from Intel website. This one is picking IP Address
in WinPE mode when loaded manually. Also have tested the connectivity to MDT server in WinPE mode with net use command and it was successful.
Have injected this driver into MDT Laptop deployment share, regenerated the ISO and tried again however Iam still unable to connect to the deployment share with litetouch ISO.
The above driver is very much part of set of network drivers on Dell website too.But it doesn’t work.
-Have also tried combination of network & storage drivers from Dell website (along with the above one mentioned ) injecting them into the MDT laptop boot image but no luck.
-Every time I make changes to drivers in boot image,I update deployment share & recreate boot image .
-This very litetouch iso connects to MDT deployments share for Dell desktop models 3010 & 3020 but have issues with laptop models E7440 & E7240. This means any connectivity or access issues can be ruled out. Also no problem with our image cause
this happens even with brand new shipped laptops with your inbuild win 7 OS.
-Have tried all options suggested on internet,tested all the drivers suggested but no luck.
-For example I tried latest E7440 netwrok & storage drivers ,Dell Win PE drivers,drivers from Intel website,etc individually as well as in combinations but the issue persists.
-If you google many express similar issues with these laptop models.
Though I used the drivers suggested by various bloggers,nothing worked for me.
Any help on this is appreciated.Thanks in advance.Hi,
I have several E6420, O3010 and since a week also some E7440 and E7240 on site.
I never had issues using the current Dell PE package for MDT.
At the moment my PE contains only the drivers from the Dell PE 3.0 package (WinPE3.0-Drivers-A13-D67JC)
and all my systems mentioned abobe have no issues connecting to the deployment share.
(btw: I have also some older E6400, E6410 and O390 I do no longer support, they
are supported by the pack Dell-WinPE-Drivers-A05.CAB according
to the Dell site, but I just started a deplymenst on a E6410 and is is also workign with just the latest PE pack)
I'd
suggest you start over with your deplyoment share using at least MDT2012 Update 1.
Create a folder "PE" under "Out-of-Box Drivers" and extract latest Dell PE pack and import he drivers there
Create a selection profile e.g. "PE Drivers" and include just the "PE" folder created above
When configuring the Windows PE settings of your deployment share select "PE
Drivers" selection profile for the driver injection in the "Drivers and Patches" to keep the PE image free of not needed drives. -
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 -
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 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 measuring amount and deployment time
I'm on beginning of MDT's Adventure. For our Client we have to prepare in a monthly basis image load reports that contain amount of images deployed in requested period of time with information how many each OS installation took time. If it's possible to
collect those information from MDT 2012/WDS logs and if it is possible to automation of preparation image load report process.You could always do a .count of your logging directory on the MDT DS. The other option would be a Powershell script that runs at the end of the deployment. It could be something as simple as --
#TS Variables
$tsenv = New-Object -COMObject Microsoft.SMS.TSEnvironment
$scriptroot = $tsenv.Value("Scriptroot")
#Machine Log Path
$machineLog = machinelog.txt
#WMI Variables
$os = get-wmiobject win32_operatingsystem
$computer = get-wmiboject win32_computersystem
#VALIDATE MACHINE LOG EXISTS.
if (!(test-path $scriptroot\$machinelog)){
new-item -path $scriptroot\$machinelog}
#ADD CONTENT TO MACHINE LOG.
add-content -path $scriptroot\$machinelog -value "Machine built - $(Get-Date) - Machine Name : $computer.name OS : $os.version"
#DONE
exit 0
This is really basic but you get the idea. Have it shoot data to a file. Usually you would want this into an xls file, but that takes a bit more work. I take no responsibility for this script and it has not been tested, it's more to give
you the idea of the construct for what you would need. Good luck.
Maybe you are looking for
-
A year ago I bought an Imac to replace my broken Laptop. I have two Ipod touches. They both shared the same Library of CD and Itunes music. Until I synced the Ipod to my Itunes account on my Imac. And it wiped the CD songs from that Ipod, and just up
-
Tool Button Not Working in Adobe Reader 9
Hello, I have a custom tool button - folder level script (with a trusted function) to digitally sign a drawing template. The tool button works in Reader 8 and Reader X, but is not working in Reader 9. The error message is shown "Not Allowed Error: Se
-
SQL not working in Multiselect prompt
Hi all, I have restricted the results in Multiselect Prompt by giving the sql query.It is working fine but when i try to search for particular record in Multiselect it is not filtering the results by applying the query instead it is using the base qu
-
Making a Photo Slide show with Final Cut Express
Hello, I am trying to incorporate pictures into my timeline mixed with video, how do I add movement to the pictures similar to how a photo slide show would look ?...Thanks in advance for your help!
-
Longstanding problem with Sleep causing Bomb
Hello, iMac Intel Core 2 Duo running X v10.4.11 all updates applied whenever system says they're available no peripherals The problem is a simple one to describe: if I put the iMac to sleep manually all is well. If I leave the iMac to its own devices