none
The execution of the group (Capture Image) has failed and the execution has been aborted.

    Question

  • I am attempting to capture an image of a Dell E4300, x64 architecture.  I created the standard sysprep and capture task sequence in MDT 2010, booted the reference computer to its operating system (it is not domain-joined), mapped a Z drive to \\mis-wdstest\DeploymentShare$ using my credentials, and ran cscript z:\Scripts\LiteTouch.wsf.  The script asks for credentials, shows the normal wizards as to where to put the capture image, syspreps the system, and reboots.  Upon reboot it comes  up into a 64-bit version of Windows PE and attempts to image the drive, whereupon I get the following errors:
    - Failed to run the action: Create WIM. The system cannot find the file specified. (Error: 00000002; Source: Windows) TSManager 2/26/2010 1:13:35 PM 1288 (0x0508)
    - The execution of the group (Capture Image) has failed and the execution has been aborted. An action failed. Operation aborted (Error: 80004004; Source: Windows) TSManager 2/26/2010 1:13:35 PM 1288 (0x0508)
    - Failed to run the last action: Create WIM. Execution of task sequence failed. The system cannot find the file specified. (Error: 00000002; Source: Windows) TSManager 2/26/2010 1:13:35 PM 1288 (0x0508)
    - Task Sequence Engine failed! Code: enExecutionFail TSManager 2/26/2010 1:13:35 PM 1288 (0x0508)
    - Task sequence execution failed with error code 80004005 TSManager 2/26/2010 1:13:35 PM 1288 (0x0508)

    Suggestions?
    Friday, February 26, 2010 6:19 PM

Answers

  • Solved.  The issue was network access.  Upon setting up the windows share for DeploymentShare$ I left the permissions as administrators/full control, Everyone/read.  Even though the credentials I was using were in the administrators group for the server, it had read-only access to the folder structure.  I changed the permissions for the share and it worked.

    Dustin, I only figured that out when I ran imagex and attempted to put the image on the server and it told me "access denied," so thank you for putting me on the right path.
    • Marked as answer by Robert.Becker Friday, February 26, 2010 8:59 PM
    Friday, February 26, 2010 8:59 PM

All replies

  • try running a manual capture with imagex /capture  to see if imagex is failing, or something in your tasksequence.

    D

    -Dustin
    • Marked as answer by Robert.Becker Friday, February 26, 2010 7:35 PM
    • Unmarked as answer by Robert.Becker Friday, February 26, 2010 8:59 PM
    Friday, February 26, 2010 6:55 PM
  • I forgot to mention that the WinPE image does have network access.  I can only imagine that the credentials aren't being transmitted to the resulting boot environment.
    Friday, February 26, 2010 7:34 PM
  • Solved.  The issue was network access.  Upon setting up the windows share for DeploymentShare$ I left the permissions as administrators/full control, Everyone/read.  Even though the credentials I was using were in the administrators group for the server, it had read-only access to the folder structure.  I changed the permissions for the share and it worked.

    Dustin, I only figured that out when I ran imagex and attempted to put the image on the server and it told me "access denied," so thank you for putting me on the right path.
    • Marked as answer by Robert.Becker Friday, February 26, 2010 8:59 PM
    Friday, February 26, 2010 8:59 PM