[mdt] MDT Image capture issues

[Harry1980]

Hi Everyone,

 

I am using MDT 2013 on server 2012. I am trying to capture a windows 7 x64 image. I have create a capture task sequence but when I try to capture an image it goes through the whole process then at the end it says it has failed. Below is the message:

 

Deployment Summary

Failure

Operating system deployment did not complete successfully.

Please review the log files to determine the cause of the problem.

During the deployment process, 9 errors, 0 warnings were reported.

 

Details

Error creating an image of drive D; rc = 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 the 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

 

I have successfully managed to deploy an image to a laptop. MDT has been installed recently and this is the first time I am trying to capture an image.

 

I am using the following customer settings ini for Capture:

 

[settings]

Priority=Default

Properties=MyCustomProperty

 

[Default]

OSInstall=Y

SkipAppsOnUpgrade=YES

SkipCapture=NO

SkipAdminPassword=YES

SkipProductKey=YES

 

Thanks in advance.

Edited December 18, 2014 by Harry1980

[bassnote]

I'm getting the identical issues today - using the same config as you as well!

I'm capturing a Win7 64bit with Curriculum Software installed but after I run LiteTouch it seems fine executing Sysprep but when the VM restarts it error

 

I have just editied the task sequence, enabling 'continue on error' on all steps, now when I have re-run I just get :

Error Creating an image of drive D:; rc=2

ZTI ERROR - non-zero return code by ZTIBackup, rc=2

 

I'm continuing to play so please keep me informed if you get any further!

 

Peter

[bassnote]

To report - this step also broke my VM... whoops!

Glad I made a copy of the hard disks vhdx file - researching - a better way of instead of coping this file is to just do a Checkpoint - believe this is the same type of facility!

[sted]

at a guess you dont have the correct permissions to upload the image to the server or missing/incorrect nic driver

[themightymrp]

Did you have an anti-virus program installed on the image before you tried capturing it? I've done that before and it messes things up a lot!!

[Harry1980]

The laptop is not currently joined to the domain, so when navigating to the Deployment Share I use the domain administrator details to get access to the share. Regards to the nic driver I have extracted the drivers from the laptop and uploaded them on to MDT.

[bassnote]

It seems to make a .wim file in the correct place but stops creating it when it gets to 700Mb

Looking into the logs I see:

 

Error opening file [\\STARB-VWDS\DeploymentShare$\Captures\test.wim].]LOG]!>

The process cannot access the file because it is being used by another process.]LOG]!>

 

Could this be antivirus on the server trying to check out the file?

 

Peter

[bassnote]

Unfortunately not

But further digging into the logs, I spot that in actual fact it starts capturing then crashes and restarts the computer when getting to 2%.

Think this is going to turn into a January problem that will get solved with a fresh mind after a break!

Merry Christmas!

[baztech]

Did you have an anti-virus program installed on the image before you tried capturing it? I've done that before and it messes things up a lot!!

+1

 

Microsoft Endpoint screwed my captures.

[yesmarcs]

Did you ever find out what was causing the issue? I'm running into a similar issue.

[Gatt]

Have you dropped the Reference PC to a workgroup?

 

I had similiar issues until I did this

Drop to a workgroup, reboot and login as the local admin

Connect to the UNC share for your MDT (eg \\MDT-Server\Deploymentshare$\Scripts

then run the "LiteTouch.vbs" file to get the usual MDT Screen and select your capture TS and follow the wizard prompts

 

the image should then capture correctly

[free780]

Reference VM should not join the domain or have AV. Ideally all the installs should be scripted. So you can just re run it in 6 months time.

[minimoo]

I had an issue recently that I was only building a x86 boot image ( as x86 boot images can boot both x64+x86 installs), but that creating the reference image needed the x64 boot image to exist.

[free780]

With capture also boot from the same architecture you are capturing.

[Jonah]

I am guessing you are capturing a VM? In which case this is apparently a known issue and we have had it as well (creating a ~700MB wim then failing). What we found was that after running sysprep, when it attempts to restart (before starting the capture) turn off the VM completely, then power on and the image will capture normally. No idea what causes it, but ensuring the VM shuts down instead of rebooting after running sysprep sorted it without issue for us. This was when capturing a VM on Hyper-V.

[EggyTheTech]

I am having the same issue, But i have narrowed it down.

it does the Create WIM and get to 100 %

Then reboots and says that "an existing in-progress deployment was found but is not in an expected state. ...." i can say no here an it will try the capture again but since there is a wim file with the same name it was using before it fails.

But if i rename the Wim before i continue it will make a second wim and finish.

So it seemes that the deploment crashes at 100% the first time and i cant figure out why.

i have MDT 2013 Update 2 with sccm 1511. just did the update when this started happening. i can capture Win 10 with out an issue. but in want Win 7.

 

any tips would be great.

 

GT

[OverWorked]

I've just had the same issue. Creating the WIM would get to about 200MB, then stop with the error and delete the incomplete file.

 

I'd recently installed the Sophos AV client on the MDT server. Though it was set to not scan on access.

 

Uninstalled Sophos from the MDT server and captures working perfectly again.

Edited August 5, 2016 by OverWorked

[free780]

I know dism and image x can be very sensitive to av. During a capture though all winpe sees is a UNC share.

[OverWorked]

I think in my case it was AV on the server interfering with the .wim file as it was being copied to it.

 

AV on the source computer shouldn't make any difference as it wouldn't be running during creating the wim. WinPE just copies it across as an offline D: drive.

[azaloum90]

I am guessing you are capturing a VM? In which case this is apparently a known issue and we have had it as well (creating a ~700MB wim then failing). What we found was that after running sysprep, when it attempts to restart (before starting the capture) turn off the VM completely, then power on and the image will capture normally. No idea what causes it, but ensuring the VM shuts down instead of rebooting after running sysprep sorted it without issue for us. This was when capturing a VM on Hyper-V.

 

Hi,

 

Signed up just to say thank you for this solution. I have an MDT Environment that runs under a Systems Center Virtual Machine Manager Configuration, and for the life of me, couldn't get the capture to proceed beyond 11% without crashing (about 500-1000MB WIM Size).

 

Tried shutting the machine down entirely after the initial sysprep, then tried again, and confirmed the capture is now at 40% and counting! Thanks SO much for this solution.