Updated MDT from MDT 2010 Update 1 to MDT 2012 Update 1, uninstalled WAIK, Installed MDT 2013, and then ADK, Upgraded all Deployment shares along the way, and now the extra drive (D:) Wim will not apply to Drive, i have tried two different ways to handle the said action, the first was using the Unattend.xml, adding the  DataImage Action, the other was using an Imagex command from the MDT task sequence. neither is applying the Wim, before the upgrade this worked. has any one else had this issue? 

Thank you, 

Dane Zittritsch

Thinix Support Manager

Hi,

I need to Migrate User Data from Windows XP to Windows 8.1 through MDT.

Can someone provide me the best bay for this ?

Shailendra Dev

We are using the 'total chaos' method of Out-of-box drivers in MDT, and our workstations are mainly Lenovo laptops and Dell desktops.

Recently, we added drivers for a new Dell desktop.  The method was as per previous, (1) download the cab of Win 7 drivers, extract (2) Run the 'unblock-file' powershell on the driver directory to remove the 'downloaded from internet' flag (3) Import into the Windows 7 folder in Out-of-box-drivers (4) Regenerate Boot Images and update the boot images in WDS.

The deployments then started failing, both on the new desktop model and on all the existing models.  We see the image applying, unattend.xml applying, and then we see this error.

Windows failed to start.....

File: \Windows\system32\drivers\amdkmpfd.sys

Status: 0xc0000359

Info: Windows failed to load because a critical system driver is missing, or corrupt.

Since I can't get to a command prompt, I'm not sure where I can find deployment logs.

I recreated the boot image fully, in case it had gotten corrupt, and it reported some errors during the import of drivers.  Perhaps these had also happened the first time, I hadn't been watching the output as closely.

Deployment Image Servicing and Management tool
Version: 6.2.9200.16384

Image Version: 6.2.9200.16384

Found 1 driver package(s) to install.
Installing 1 of 1 - D:\AdminDeploymentShare\Out-of-box Drivers\Net\netwex_15.6.1.6_58FA89356668673D4CCB913FDC4A27CCE0F04A19\netwex.inf: Error - An error occurred. The driver package could not be installed. 

For more information, check for log files in the <windir>\inf folder of the target image.

Error: 2

The system cannot find the file specified.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

Exit code = 2

DISM /Add-Driver failed, rc = 2

The dism.log is massive and I don't know which bits to post. 

I don't know how (or if) I can pull out the drivers for the new model and return things to a working state.

The nuclear option is to restore a version of the deployment server from before when these drivers were added, but that can be awkward.

Another option might be to re-organise all the drivers, away from Total Chaos, and towards Total Control, if indeed that might be the root cause of the problem.  What do you think is the best option?

Hello Forum, I've run into a weird issue. Only one of my images will not deploy. It doesn't boot to the PXE environment, it hangs at the windows screen(see screenshot). I figured, maybe it's a driver thing, so I went to the manufacturer's site and grabbed the latest drivers as well as the Winpe drivers, still no go. Next, I deleted the deployment's boot folder contents and completely regenerated the boot files, still no go. I've also, rebuilt the wim file from scratch, still at a dead end. I'm totally baffled because only one of our models has this problem.

version: MDT 2012 6.1.2373.0

Hosted on Windows Server 2008 R2 VM

WDS: NO 

Since it's not booting to the PXE environment, it's not generating any logs files. Please Help

IT Support " Scripting Noob "

So, long story short, I have a completed reference image that I need to be able to deploy to remote sites via USB.

I've made my media folder and placed the contents on the root of my USB key.  The computer allows me to boot from the key and select either x86 or x64 (either option ends in the same result.)  The computer loads PE and opens up to the greet me with the initial "Solution Accelerators" background.  I would expect that the deployment process should kick off at this point but, after a few moments, the X:\windows\system32\cmd.exe box appears and the party is over.

If I can explore the USB and if I try to manually start the litetouch script I get a prompt detailing the script path and a message stating: "No such interface supported". In the command prompt window, I get a resulting line stating "Access is denied".  I verified that folder permissions should not be causing the problem.

I am new to MDT and this hurdle is leaving me stumped.  Any advice would be more than appreciated.

Have a step in a TS that should install an MDT application (Fingerprint Reader). Have specified the following WMI filter:

Select * From Win32_ComputerSystem WHERE Model LIKE "%840%" OR Model LIKE "%8570%" OR Model LIKE "%8460%"

I suspect that this filter doesn't work, but I can't find any reference in BDD.LOG.

1. Is it possible to detect any WMI filter results in the MDT Logs after deployment?

2. How is the correct synthax for a MDT WMI query that queries for multiple computer models?

3. When using a WMI Filter with only one computer model like <Select * From Win32_ComputerSystem WHERE Model LIKE "%840%">, the filter works. But it's not convenient to have the same TS step for installing an application three times with three different WMI filters when the same SW should be installed on three different computer models. And we have 4 identical TS that install different OS custom images. So, when there is a new fingerprint reader SW, we have to make 12 changes: Three TS steps in four TS.
Is there a better method to archive this described requirement?

Thanks in advance for any help.

Franz

Using MDT 2013 trying to deploy Windows 8.1 with default Taskbar/Desktop icons for every new users...



I have built an image and i use the copyprofile=True settings in my unattended.xml.

The administrator profile has been set with all the icons i need. After sysprep and deployment, all the Start icons are getting copied to new profiles but the taskbar icons are not.

Found out on the web that copyprofile=true will not copy the taskbar icons to new profiles,...

I have used the script here: http://theitbros.com/copy-taskbar-icons-windows-7-sysprep-v2/ and saved it under"C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup" , then sysprep'ed the computer. After deployment, however, looks like the script is executed during the auto logon during the deployment  task sequence and as the script is meant to delete itself, it is not accessible for new users.

How can i get every new user have this script run one time only at first logon as stated on the itbros webpage? (i cannot use GPO) 

I'm not sure if anyone has tried this, but I thought I'd ask. What I'm trying to do is call litetouch.vbs which is sitting on an MDT distribution share from WinPE. I can call litetouch.vbs and pass in my paramaters to run a task sequence, but the task sequence stops before it runs setup to deploy the OS. 

I'm guessing this has to do with some of the info that's being gathered from the scripts and task sequence variables. Has anyone tried this and/or know what would need to be changed to be able to launch MDT from the share instead of from the content on the MDT iso?

Thanks,

Rich

Hello,

My question is related to driver handling. I was thinking that what is the difference between drivergroup and selection profile.

If I use %Make%\%Model% approach to set driver group and install drivers with that vs. selection profile that is set to install all drivers from selection profile X. both will have PnP ID driver detection disabled this way.

Hi All,

I have a MDT/WDS/WSUS services all setup, but have noticed when that a few 'Run Command Line' tasks have not been working during the task sequence deployment.

The first one is to remove the WSUS Registry Keys, we have tried with a VBS Script and reg import. Both do not seem to run to remove the registry settings, but if ran separately they work fine (outside of the task sequence)

The second one is to run two files that are part of Kbox (dell KACE), this fires off an .exe with a switcher. This script is also not running as part of the task sequence, yet once ran separately its fine...

Any idea's? 

We are getting new model ultrabooks here at work and I have been assigned the task of building our golden image.  I got everything configured the way I wanted and when I went to capture the image I got an error after reboot that said Windows failed to start. The file ifm63x64.sys was missing or corrupt.

After banging my head against the wall and searching Google I found a solution, in the driver package on the deployment share there were 2 SCSI drivers that were imported with the NIC driver.  I removed those 2 drivers and updated the share completely regenerating the boot images and was able to get a sucessful capture.  Now when I go to deploy the .WIM file that I captured I'm getting the same error.  It will go through all the motions of installing the OS and goes to reboot the first time and it hangs giving the file ifm63x64.sys is missing or corrupt. 

I have created a new share just for this model machine and only imported LAN drivers from the manufacturer, but still got this error.  I deleted all of those drivers and imported LAN only drivers from Intel and no go.  Go back into the drivers list and see the SCSI drivers are there so I deleted them and still get the error. 

From what I have been reading on the internet it has affected different manufacturers and different model machines, none of which are the Lenovo 20A8 I have.

Any help or insight would be very much appreciated.

Thanks,

Leigh

Everyone,

I am currently attempting to find a work around that will allow me to leverage a single WDS/MDT image for all of my PC hardware. At the moment, my biggest hurdle comes from hardware manufacturers that are not properly labeling their hardware. 

My company has a decent mixture of traditional OEM PCs (Dell, HP, etc.) as well as consumer level PCs with a variety of components (ASUS, Intel, EVGA, etc).  The issue I am faced with is getting the proper identification information from the consumer level hardware using the standard 'wmic csproduct get name' command.  

If I run the 'wmic csproduct get name' command, several of my components return vague identifiers like System Product Name or OEM. Obviously, this is not ideal as it does not uniquely identify the hardware.  In an effort to find a solution, I discovered a suggestion to use the WBEMTEST utility in another thread but sadly, the results are the same - System Product Name or OEM appear in those locations.  However, a thread on superuser.com suggested the use of 'wmic baseboard get product' which actually returns uniquely identifiable data. 

As I understand it, WDS/MDT uses the wmic csproduct get name command to identify hardware during the image deployment process. This leads me to question

• Whether WDS/MDT can be modified to also use the 'wmic baseboard get product' command if the results of 'wmic csproduct get name' return data that is unusable, or
• Whether the results of 'wmic baseboard get product' can be used in lieu of the results of 'wmic csproduct get name' 

Any feedback the community can offer will be greatly appreciated.  I know this is not the first time this issue has come up but thus far, I have not found a single solution or workaround that adequately resolves the problem short of buying hardware from manufacturers that know what they are doing.  

NOTE: I originally included a screenshot and supporting links but the site disallowed their use.  Sorry about that.

Guys - I am new to deploying windows 8.1 as well as using MDT (I'm familiar with SCCM with MDT integration, but have only deployed Windows 7). For this project I am only using MDT 2013 / WDS.

I have a very basic task sequence set up and configured to deploy my Windows 8.1 reference image. All works as expected except a few things.

After the OS is applied MDT stops at the Eula Page. I have to hit "accept" and then it takes me to the "express settings" selection. Once I select express settings I am taken to the logon prompt. I have to enter the administrator password where it takes me to the desktop and THEN the task sequence installs my apps and completes.

How do I bypass the Eula Page and Express settings screens?

Is it normal behavior to have to log in before the task sequence finishes?

Below is a screenshot of the only modification I made to the TS.

thanks for any help

-PD

Hi all !

I have computers run winodows 7 join domain. Because security, I have disconnected internet of computer run windows 7 , never.

But, I want to automatic update win for windows 7. Can i  use Microsoft Deployment Toolkit to do it ?

So, Can you help me ?

Thanks and best regards .

The problem I am about to describe doesn't exist with MDT 2010 update 1, MDT 2012, or MDT 2012 update 1 when using the either WAIK or ADK.  I have not attempted to reproduce this problem with older versions of MDT or pre-release versions of MDT 2013.  The problem definitely exists with MDT 2013 RTM.

This is the same problem as Inconsistent DISM.EXE error when applying unattend.xml during LTI deployment - Possible bug!, but this is more concise and provides details on how to reproduce the problem. 

Status as of 2014-03-30 (Previous workaround deemed unusable - core bug still present)

Keith Garner determined that DISM.EXE was failing while processing the <offlineServicing> section in the unattend.xml file.  Removing this section resolves the issue, but this section is needed to inject drivers into the image during WinPE and is needed  The presence of this section didn't cause any problems with previous releases of MDT/ADK - it is likely an interoperability bug within the DISM.EXE tool.  See replies below for details.

Confirmed the problem applies to deploying Windows 8.1 as well.

Problem:

When deploying Windows 7 Pro x64 w/SP1 and enabling/disabling features using unattend.xml, deployment often (almost 100% of the time) fails with this dialog:

Steps to reproduce ("bare-metal"):

1. Create a new, clean virtual machine (I used VMware Workstation)
2. Boot the VM with the Windows 7 x64 Pro w/SP1 Volume Licensing DVD
3. Install Windows with default options, OOBE choices:
   • User name = Tony
   • Computer name = Tony-PC
   • Password = tony
   • Windows Update = recommend settings
   • Time zone = Eastern
   • Location  = Work network
4. Install VMware Tools and reboot
5. Configure Internet Explorer using express settings
6. Configure Windows Update to get updates for other Microsoft products
7. Apply all available Windows Updates*
8. Install ADK for Windows 8.1 (http://www.microsoft.com/en-us/download/details.aspx?id=39982)
   • Installs .NET Framework 4.5 automatically
   • Accept all default installation choices
9. Install MDT 2013 x64 (http://www.microsoft.com/en-us/download/details.aspx?id=40796)
   • Accept all default installation choices
10. Apply all available Windows Updates again*

*When installing Windows Updates:

• Select all important updates, except Internet Explorer 11
• Select all optional updates, except Bing Bar, Bing Desktop, Security Essentials, and Silverlight.

Launch MDT Workbench:

1. Create a new deployment share
   • Accept all defaults:  C:\DeploymentShare, DeploymentShare$, etc.
2. Import Operating System:
   • Full set of source files
   • Source Directory = CD drive containing the Windows 7 x64 Pro w/SP1 Volume Licensing DVD.
   • Accept remaining defaults
3. Create a new task sequence:
   • ID = Test
   • Name = Test
   • Template = Standard Client Task Sequence
   • OS = Windows 7 Professional
   • Key = Do not specify at this time
   • Settings:
     • Full name = Tony
     • Organization = Tony
     • IE Home Page = about:blank
   • Admin password = tony
4. Update Deployment Share, and completely regenerate the boot images.

From another new, clean virtual machine:

1. Boot from the "C:\DeploymentShare\Boot\LiteTouchPE_x64.iso" file from MDT computer.
2. Run the Deployment Wizard, and enter credentials (tony, tony, . )
3. Launch the created Task Sequence (accept defaults, click keep clicking ‘next’):
   • Computer name = autogenerated
   • Join a workgroup = WORKGROUP
   • Do not move user data and settings
   • Do not restore user data  and settings
   • Locale and time = accept defaults
   • Do not capture an image

At this point, the deployment will succeed every time.

Now, edit the task sequence and edit the unattend.xml:

1. Add the Foundation Package to the answer file
2. Edit the foundation Package:
   • Disable MediaPlayback > MediaCenter
3. Save file and close task sequence.

Deploy the task sequence again using the directions above (for each attempt, I used a new, unused VM), and it will fail nearly every time!

Notes:

• Enabling/Disabling features via unattended.xml is a supported and documented process.
• I suspect a bug with DISM.EXE v6.3 while operating on Windows 6.1 images.
• I realize that adding"Install Roles and Features" and/or "Uninstall Roles and Features" task sequence items may be a workaround for this problem (I haven't tried it), but it is not asolution to the problem.
  

I keep getting the above listed error when trying to update the rules on one of my deployment shares.  I've even gone so far as to remove the read-only flag on everything in the share, it doesn't help.

As a workaround, I've been editing the CustomSettings.ini directly, but I'd really like this to work.  Any ideas?

As an aside, the 'Alert me when someone responds to this post' never seems to work here.  And yes, I've checked my spam folder as well...

Hi,

I am getting below error in Deployment Summary  while Computer backup to network during Refresh from XP to 8.1 through MDT 2013.

1. I followed URL- http://blogs.technet.com/b/mniehaus/archive/2014/01/09/migrating-from-windows-xp-to-windows-8-1-using-mdt-2013.aspx to use USMT for the UserProfile through MDT 2013.

2. For User profile I am using Hardlink USMT through MDT Wizard, that is working fine.

3. My Deployment Share rule is below..

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
DoCapture=YES
ComputerBackupLocation=NETWORK
BackupShare=\\MDT2013\share$
BackupDir=%OSDComputerName%
BackupFile=%OSDComputerName%.wim
BackupDrive=ALL

4. ZTIBAckup Logs below..

  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="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[OriginalPartitionIdentifier is set, find disk: SELECT * FROM Win32_LogicalDisk WHERE Size = '26213933056' and VolumeName = '' and VolumeSerialNumber = '7413DBF4']LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Search for Drive: OriginalPartitionIdentifier  SELECT * FROM Win32_LogicalDisk WHERE Size = '26213933056' and VolumeName = '' and VolumeSerialNumber = '7413DBF4']LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Found Drive: C:]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Property OSDTargetDriveCache is now = C:]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Property OSDisk is now = C:]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Checking to see if we can store the backup locally]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Drive C: 3231300]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Drive D: 272600]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Drive X: 2489]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Local store path = C:\StateStore]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Total used space: 3506389]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Available space at C:\StateStore: 22368244]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Backup can use local path]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Property USMTLocal is now = True]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Network store path set to: \\MDT2013\DeploymentShare$\Tools\X64\imagex.exe"  /capture /compress maximum C: "\\MDT2013\share$\TEST8\TEST8.wim" "001CDrive" /flags EnterpriseN]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Command has been started (process ID 1248)]LOG]!><time="13:16:21.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 1248)]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > ImageX Tool for Windows]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > Copyright (C) Microsoft Corp. All rights reserved.]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > Version: 6.3.9600.16411]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > Files/folders excluded from image capture by default:]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console >  \$windows.~bt]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console >  \$windows.~ls]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console >  \winpepge.sys]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console >  \Windows\CSC]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console >  \Recycled]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console >  \Recycler]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console >  \$Recycle.Bin\*]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console >  \System Volume Information]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console >  \swapfile.sys]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console >  \pagefile.sys]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console >  \hiberfil.sys]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > Turning on VERIFY option for network share]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > Scanning files and directories...]LOG]!><time="13:16:22.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > [   0% ] Capturing progress ]LOG]!><time="13:16:33.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > [   1% ] Capturing progress ]LOG]!><time="13:16:33.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > [   2% ] Capturing progress: 11:04 mins remaining ]LOG]!><time="13:16:47.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > [   3% ] Capturing progress: 9:12 mins remaining ]LOG]!><time="13:16:47.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > [   4% ] Capturing progress: 7:58 mins remaining ]LOG]!><time="13:16:50.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > [   5% ] Capturing progress: 7:20 mins remaining ]LOG]!><time="13:16:55.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > [   6% ] Capturing progress: 7:59 mins remaining ]LOG]!><time="13:17:07.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > [   7% ] Capturing progress: 8:23 mins remaining ]LOG]!><time="13:17:13.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > [   8% ] Capturing progress: 8:20 mins remaining ]LOG]!><time="13:17:17.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > [   9% ] Capturing progress: 8:33 mins remaining ]LOG]!><time="13:17:26.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > [  11% ] Capturing progress: 8:21 mins remaining ]LOG]!><time="13:17:35.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > [  13% ] Capturing progress: 7:37 mins remaining ]LOG]!><time="13:17:35.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > [ RETRY ] Restoring C:\WIMA8B0.tmp again (Error = 1392)]LOG]!><time="13:17:35.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > [ ERROR ] C:\StateStore\USMT\File\C$\MININT\SMSOSD\OSDLOGS\BDD.log (Error = 80)]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > [ ERROR ] C:\StateStore\USMT\File\C$\MININT\SMSOSD\OSDLOGS\BDD.log (Error = 80)]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > Error imaging drive [C:\]]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[  Console > The file exists. ]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Return code from command = 2]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[Error creating an image of drive C:, rc = 2]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="3" thread="" file="ZTIBackup">
<![LOG[ZTIBackup COMPLETED.  Return Value = 2]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="1" thread="" file="ZTIBackup">
<![LOG[ZTI ERROR - Non-zero return code by ZTIBackup, rc = 2]LOG]!><time="13:17:38.000+000" date="04-15-2014" component="ZTIBackup" context="" type="3" thread="" file="ZTIBackup">

5. Computer Backup Dir is accessbaile and permission is ok.

Any idea to resolve this issue

Shailendra Dev