Deploying a Captured Image

I would like to broadcast a image to all machines on the network even those with SCCM clients.  I have some machines that are on the domain that need to be imaged from time to time and I also have some new machines that need to be imaged.  I
also need to prompt the user that starts the image process to enter the computers name.  I know the computer name can be prompted by using the unknown group and prompting for the OSD but how would I do this for a machine name that is already listed
in SCCM? Would the machine fall under the unknown category once the image process starts? 

Here's couple of ways to do it:
http://www.windows-noob.com/forums/index.php?/topic/5542-how-can-i-easily-prompt-for-a-computer-name-in-configuration-manager-2012/
http://t3chn1ck.wordpress.com/2009/04/24/script-to-prompt-for-system-name-in-sccm-osd/

Similar Messages

  • Trouble booting to WDS server to deploy or capture image

    Hello, we have an existing WDS server running Server 2008 R2 with SP1.  I am having trouble getting a Surface Pro 3 to boot to the WDS (even after creating updated deploy and capture boot images).  I can get the Surface to PXE boot, and I am
    able to choose the Deploy or Capture boot image, but then I get the message that an error occurred obtaining an IP address from the DHCP server.  During the PXE boot, the device does obtain an IP address in the correct range.  I tried adding the
    Surface ethernet adapter drivers to the boot wims but since they are not signed I get errors that they cannot be added.  Any suggestions?

    Added drivers to boot images using DISM with the /ForceUnsigned override.

  • Windows Deployment Services - Capturing Image

    To Microsoft Technet,
    I am currently a student and I have setup a fully functioning Windows Server. This Windows Server has AD, DHCP, WDS and MDT installed on to it. This server was setup so that we can re-deploy Windows to any of our computer labs and it will just be a fresh
    install. My problem is that the students also need to upload (capture) an image of the OS to the server every now and then as part of the coursework. When uploading an image they are presented with this option:
    Obviously when you click connect it asks for a username and password so that it can write to the folder. The students are not allowed to know the username and password because if they do then they break the server. They do this because they log on and mess
    around with it. I am currently asking if there is a solution so they can connect to the server and it will automatically log them on as the admin.
    These are solutions however I feel they would be inappropiate:
    - Give them a username that has read / write access but block the logon.
    - Allow "Everyone" to read / write thus no logon screen.
    However I feel that both are a security risk as students can just join the folder from the network and delete other students work.
    Instead I would like the windows server to automatically allow the connection by implementing the logon details. Is there a possible way to do this?
    Thanks,
    Thomas.
    The image is off the internet (I did not make it).

    Hi thomasjcf21,
    Another possible is you can create shared folders for each student and give each student account full control permission, after they finish the OOBE they can upload their
    image to WDS server.
    The related third party article:
    Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step – Part I
    http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-using-windows-deployment-services-wds-step-by-step-part-i/
    I’m glad to be of help to you!
    *** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these
    sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use
    of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
    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.

  • Administrator account is disable when deploying windows 7 x64 captured image

    I’m using MDT 2012 update 1. I create one deployment share with two task sequence.
    The task sequences are: one for windows 7 x86 and the other one is windows 7 x64.
    Both are working fine until I try to sysprep and capture with all the windows updates.
    Sysprep and capture windows 7 x86 with all windows update work fine. I’m able to deploy the captured image without an error.
    My problem is with the windows 7 x64 captured image. I’m able to sysprep and capture the windows7 x64 with all the windows update. Once the capture is completed, I change the .win file in my windows 7 x64 task sequence to point to the new .win file (capture
    image with all the windows update). When I deploy windows 7 x64 on a pc, the OS get install but boot up to the sign on screen. The Task sequence does not complete. No error message. Cannot log in as local or domain administrator, account is disable.
    Why does it work with my windows 7 x86 image and not with my windows 7 x64 image?
    With my windows 7 x86 image the task sequence completed successfully with no error and it logon automatically in windows but not with my windows 7 x64 image.
    Both task sequences are the same.
    Let me know if any info for this please.
    thanks

    They should both work, perhaps you missed a step when creating the x64 image.
    1. Verify that the Windows 7 x64 image was created cleanly, with no errors. Sysprep ran with no errors.
    2. Verify that you created the windows 7 deployment task sequence cleanly. I would do a windiff of the TS.xml and unattend.xml file from both folders in the deployment share.
    3. Try running without a domain. Some domain's have a GP set to disable the local administrator account.
    Keith Garner - keithga.wordpress.com

  • Problem deploying captured image

    I'm testing our new SCCM 2012 and specifically OSD and deploying a captured image. The image is captured on a separate MDT config.
    What I'm seeing with this image deployment is that about 90% of the times it ends with a 80070002 TS error. Examining the smsts.log shows the following:
    Successfully completed the action (Setup Windows and ConfigMgr) with the exit win32 code 0
    So this step seems to go fine and and then the State Restore step starts and the computer reboots to the full OS.
    The group (State Restore) has been successfully started
    But then I don't know what happens, non of the following steps are run, for example there's application install and so forth. It seems to parse through the remaining steps but doesn't run them and then ends with Gather Logs and stateStore on Failure.
    I just can't see from smsts.log what the problem would be, what other logs should I look in to find out what's going on?

    Seen that many times when doing deployments, but not on capture mentioned. In that case the error is a known bug. Workaround is to add 2 Task Sequence Variables. Unfortunately R2 is needed for that.
    -SMSTSDownloadRetryCount = 5
    -SMSTSDownloadRetryDelay = 15
    Just have a look at my blogpost for more information on this:
    http://henkhoogendoorn.blogspot.nl/2014/07/osd-ts-fails-during-package-download.html
    My blogs: Henk's blog and
    Virtuall | Follow Me on:
    Twitter | View My Profile on:
    LinkedIn

  • Deploying captured image of reference computer - WDS & MDT

    Hi, yesterday I set up MDT 2012 Update 1 on Windows 7 computer and WDS on Windows Server 2008 R2. I completed the following tasks:
    Create New Deployment Share
    Import Operating System (Windows 7) into Deployment Share
    Import network drivers for HP Compaq Pro 6300 Small Form Factor into Deployment Share
    Create Sysprep and Capture Task Sequence for capturing image of reference computer
    Update Deployment Share
    Prepare reference computer for imaging - install OS, drivers, apps, patches . . .
    Run Sysprep and Capture Task Sequence from reference computer
    Import captured image of reference computer into Deployment Share
    Create Standard Client Task Sequence for deploying captured image to bare-metal computer
    Use Lite_Touch wim file as WDS boot image
    Run PXE boot on bare-metal computer
    Enter necessary information - computer name, domain name, time zone and so on
    I took more than 2 hours to complete deployment of captured image to bare-metal computer. Everything worked well but after this process finished I noticed that computer name was not the one I entered in TS nor computer was joined to the domain. Time zone
    was not set. It seems that computer name, workgroup membership, time zone can not be altered in TS - they remain the same as they were on sysprepped computer.

    My doubts and yours Keith were right, sysprep was not performed well at all via Sysprep and Capture Task Sequence so I did
    sysprep /generalize /oobe /shutdown on reference machine and then booted it into WinPE with ImageX tool (if I am right in newest ADK dism is main tool for capturing online images instead of ImageX which is deprecated). I captured
    image of Windows 7 OS partition and copied it to MDT technician computer, imported it as operating system in MDT deployment share and selected it as .wim image to deploy to new bare metal machine via Standard Client Task Sequence. During deployment entered
    values for computer name, time zone were applied successfully and computer was joined to a domain. After restart message was shown with info that built in local administator account was disabled with switch user option where I could choose local account that
    existed on sysprepped machine or domain account.
    Conclusion: Sysprep step in Sysprep and Capture TS in MDT does not work at all. I will try this on newest version of MDT (MDT 2013) since I am testing now on MDT 2012 Update 1 version. If sysprep does not work again MDT is useless for capturing images thus
    I have to use sysprep manually and then dism for capturing sysprepped image.
    Thank you very much for your time and patience.

  • WDS capture image on a Windows 2012 R2 server fails with a winload error

    Hello,
    I have been fighting with this problem for days now. I have to install
    30 Win8.1 Pro PC's with  WDS. The WDS service is running on a Win2012 R2
    server. I added the Win 8.1 Pro boot and install images and created a capture image.
    Now when I boot the reference computer I get  a Boot Manager message saying that winload.exe is missing or corrupt. The original boot wim works
    correctly.I removed and added the WDS role a couple of times, I tried the procedure with a 32 bit Win7 boot image, and that worked, But when I added the capture image created from the original Win8.1 boot.wim, that spoiled both capture images.  I tried
    the same thing with a Win2012 R2 Standard server after removing and adding the WDS role again, but the capture image generated the same error as above. .I see that since about mid-April many people has the same problem.Different solutions are suggested, but
    none of them   worked for me.  One of them is to mount and unmount the capture image, that didn't help for me.
    Any help is appreciated.
    Thanks
    Gabor

    Do I understand correctly that if you deploy original wim file to your testPC1 it works all right, but if you deploy an image that you captured on buildPC to testPC1 then you get the winload.exe error ?
     Are you formatting (deleting all the partitions) on testPC1 during the
    deployment of captured image ? Can you check and confirm if the HDD seting for AHCI or IDE (yes, its still around) is the same option on both stations?

  • Captured images missing installed applications

    Greetings,
    I am using MDT 2013 to capture an image of a reference computer that has Windows 8.1 installed, along with several additional applications.  When I deploy the captured image with a new task sequence set up for that purpose, the applications are
    missing.  This is not a matter of the shortcuts being gone; they do not exist in the their respective Program Files folders either, and do not appear in the Programs and Features list.
    I have verified that I'm using the captured image, and captured the reference image again (from a Hyper-V VM) just to be sure.  My understanding was that sysprep & capture did not remove applications, just data that's unique to users and the machine. 
    Thank you in advance for any help.

    Problem solved.  After updating the deployment share, I had forgotten to replace the boot image within WDS. 

  • Windows 7 Professional PC hangs at "Loading files" when trying to boot with custom capture image on Windows Deployment Services.

    I have created a custom capture image in WDS. Now when I try to boot my reference PC into this image the PC hangs at "Loading files". The reference PC is running Windows 7 and I am using Windows Server 2012 Standard on my server.
    I have followed the instructions on how to create the custom capture image on the server to a fault. I PXE boot the PC and it shows the capture images after I hit F12. The problem is that it starts to boot and then hangs about 2/3 way through the progress
    bar.
    Any help would be appreciated.

    Hi Derrick Logan,
    We need know the detail phases your client hang, if it is irregular status, please collect the WDS log then post it. You can refer the following similar thread solution first.
    How to enable logging in Windows Deployment Services (WDS) in Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and in Windows Server 2012
    http://support.microsoft.com/kb/936625/en-us
    Windows is loading files... Hangs on WDS
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/baacadc4-830d-43e1-ace8-3292e886958e/windows-is-loading-files-hangs-on-wds?forum=winserversetup
    WDS hangs at "Windows is loading files..." on a LAM jhl91 laptop
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/3ebb6e0b-9f05-4fee-b3c0-129c34bb879d/wds-hangs-at-windows-is-loading-files-on-a-lam-jhl91-laptop?forum=winserversetup
    I’m glad to be of help to you!
    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.

  • Deploy Captured Image

    Hello,
    We have a server using 2008 R2.  I am new to WDS and I'm trying to deploy an image that we captured, via WDS.  I was able to build a capture boot image and capture the image from an old AlienWare Aurora R4 computer.  I am trying to deploy
    this image to three more AlienWare Aurora R4 computers, same configuration.   After I create the boot image, and install image, I boot the AlienWare computer via PXE and choose the boot image.  I seems to start just fine, but then gives an error
    saying that there is a communication error with the server, make sure that the server is online or that the ports on the firewall are open.  Again it boots fine to the capture image, but not to the boot/install image.  What am I missing????

    Ok, I've tried deleting the unattend.xml file, which I found in another thread.  I've deleted and re-installed my images, and I'm still getting the following error;  WdsClient:  An error occured whild communicating with the windows deployment
    services server.  Please check to ensure that the server is operational and that the necessary ports are open on the server's firewall.  Server Name [servername], Server IP address [serverip]
    I can't seem to get the image to work.  I've attached the proper driver, since if I didn't I would get a different error stating that the driver was not loaded. 
    We are using Symantec Endpoint as per DOD requirements. 
    If we don't find a solution soon, I may be forced to uninstall and reinstall Deployment services.  This project is becomming  time critical.

  • 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

  • Unable to capture images since upgrade to MDT 2013

    I recently updated MDT 2012 to MDT 2013 to enable support for Windows 8.1. Under MDT 2012 I was able to both capture and deploy images without an issue. Since upgrading to MDT 2013 I've had nothing but grief. When I launch my Sysprep and Capture task I am
    returned with the following error:
    Error creating an image of drive D:, rc=2ZTI ERROR -Non-zero return code by ZTIBackup, rc=2Litetouch 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
    Once the machine boots up again I check the BDD log located in C:\Windows\Temp\DeploymentLogs and notice the following error:
    <![LOG[  Console > Error opening file [\\rmh-vm-mdt2012\DeploymentShare$\Captures\WINDOWS.8.1.REF.wim].]LOG]!><time="10:23:55.000+000" date="02-06-2014" component="ZTIBackup" context="" type="1"
    thread="" file="ZTIBackup">
    <![LOG[  Console > Access is denied. ]LOG]!><time="10:23:55.000+000" date="02-06-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
    My issue appears to be a permissions problem.  For troubleshooting purposes I've given Everyone full access to \DeploymentShare$ however the problem continues to persist. 
    I'm not sure where to go from here.  Hoping someone can help. 
    Thanks.

    Additionally, ensure that the share itself is marked R/W access.
    As a test, boot to WinPE and try to create a file, any file on the share.
    However, Lordy86 may have the correct solution :^).
    Keith Garner - keithga.wordpress.com

  • Capturing images from camera and uploading to sharepoint library automatically.

    Hello Everyone,
    My requirement is to capturing images from camera and uploading to sharepoint library automatically. No manual uploading will take place.
    Please suggest me.
    Thanks,
    Rajesh

    Hi,
    From your description, my understanding is that you want to capturing images from camera and uploading to sharepoint library automatically automatically upload images to SharePoint library.
    You will save images in your local computer after capturing visitors’ image. You could develop a custom timer job to periodically get pictures from the local folder in your computer. Please refer to this article:
    Create and Deploy Custom Timer Job Definition in SharePoint Programatically
    http://www.codeproject.com/Tips/634208/Create-and-Deploy-Custom-Timer-Job-Definition-in-S
    you could upload pictures to your SharePoint from the folder with C# code, please refer to this article:
    How to: Upload a File to a SharePoint Site from a Local Folder
    https://msdn.microsoft.com/en-us/library/office/ms454491%28v=office.14%29.aspx?f=255&MSPPError=-2147217396
    Best Regards,
    Vincent Han
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • SCCM 2012 SP1 fails to install OSD of Captured Image

    I installed Windows Server 2012, Visual Studio Pro 2008, 2010, 2012 and SQL Server 2012 onto a machine. Configured the settings on Windows Server 2012 and SQL 2012 to how the Developers requested to be configured. Ran the Capture Media from SCCM 2012 SP1,
    saved to the designated network share. Capture was successful.
    I create a TS to deploy the image to the other Dev Servers but it reboots to say no valid operating system found. I checked Monitoring for the Deployment I see the Task sequence but has the following error: Device - Unknown, MessageID - 11170, Description
    - The task sequence manager could not successfully complete execution of the task sequence.
    I see in the Apply Operation System from a captured image shows 1-1, 2-2, or 3-3. Does it matter which one I select and if so what does the numbers mean?
    Any help is greatly appreciated, thanks!!

    Hi Blacksuit,
    Those numbers of the captured image stand for the indexes that are part of your WIM.  And yes, it does matter which one you select.  In the ConfigMgr console, go to your Software Library > Operating Systems > Operating System Images and select
    the image you imported into ConfigMgr.  Then at the bottom, click the Details tab to display your indexes.  The index that contains your OS will have an OS Version and a description.  The other indexes will be data images and not contain any
    information in the Details tab.  You'll need to choose the index (number) that contains the OS for the Apply OS step.  To apply the data image indexes, use the Apply Data Image task sequence step and specify the partitions to apply the images
    too before the Apply OS step.
    Good luck!
    -Matt 

  • WDS 2012 Black Screen when trying to capture image

    I'm currently having an issue trying to capture windows 8.1 Enterprise image using Server 2012 R2 + WDS for deployment.
    All the usual steps have been followed, images added from the install media used to set up the initial machine, DHCP configured and PXEBoot works fine for the deployment image (it loads, I get an ip, can access reminst share) but when I boot in the capture
    image I get nothing but a black/blank screen.
    Initially when I booted in to the capture image I was receiving an 0xC000000F error but by adding the network driver to the capture image it resolved that issue and it gives the blue windows logo and starts loading but then goes black. I've subsequently
    tried to add all available drives for this machine from the HP site but made no difference.
    WDS server is a hyper-v VM and the box to be capture is physical, both on the same vlan.
    Any one experienced this?

    I did not find any help with this. I was able to get a native boot.wim and install.wim to work from the installation media (with driver injection - which I must say is way easier in W2K12). However the capture did not and will not work. VERY frustrating!
    I wound up doing a WDS basic OS install then I had to manually touch 24 boxes to install the rest of the software (still not quite done after three solid days of work).
    Also, I should point out: I am targeting Dell Optiplex 790s. I'm using the PE 5.0 drivers which work fine. i also downloaded the Dell Optiplex 790 driver set and injected those as well, even though they are targeted for Win 7, not Win 8.1. 
    Interestingly, if I updated the old system bios (A05) to the new (A18) the machine couldn't even contact the WDS server. It was working before at A05 and then completely stopped at A18, requiring me to do a complete full install from installation media.
    Way to go Dell! This is why people are switching to Lenovo.
    Best,
    Bill

Maybe you are looking for

  • Transaction IW32.How to find out the person name.(Last changed By)

    Hi all, When i executed the transaction IW32.Its displays changed by and created by fields. please any body can tell me how to find out the person  name who had made last change with respect to the field changed by. Please tell me the table and field

  • BPM error:Container element in step transformation is not initialized

    Hello Experts, I am new to the concept of BPM. I'm trying to create an integration process in which I'm taking an Idoc and processing it in many ways. The process contains many transformation steps. There two such transformation steps which have been

  • Changes in slide show on DVD

    1.I made a slide show with Photoshop Elements 4 and burn it to a DVD-RW with Premiere Elements. After several try it works.All 750 photos with transitions are there and I saw it on T.V. 2 Back in PE4, I made some changes in the slideshow and save it.

  • Set text on status bar

    Hi all. I need help with Text on status bar. It was working well with IE6. here is the link http://www.aubryaubry.com/index.htm thank you

  • XML parser RT

    Hi all! I need some help: i want to parse an xml file in labview Real Time.  In windows i know you can use a microsoft parser using Windows ActiveX. But i think this method will not work in RT environment .. Am I wrong ??? Does anyone knows how to do