I am currently trying to capture a machine for deployment and I can't figure out what is wrong. This is the message I get in the ConfigMgr Status Message Viewer: The task sequence execution engine failed executing the action (Capture the Reference Machine) in the group (Capture the Reference Machine) with the error code 2147942432 Action output: T=80070020 (e:\nts_sms_fre\sms\framework\tscore\wimfile.cpp,430) ImageFile.CaptureVolumeImage( (*itr), &saFilesToNotCapture), HRESULT=80070020 (e:\nts_sms_fre\sms\client\osdeployment\capturesystemimage\capturesystemimage.cpp,747) CaptureSystemImage( progressUi, slVolumesToCapture, sOfflineSystemRoot, ImageFile), HRESULT=80070020 (e:\nts_sms_fre\sms\client\osdeployment\capturesystemimage\capturesystemimage.cpp,909) Closing image file \\sccm\Images\5205_Admin\5205_W5X.wim Command line for extension .EXEis "%1" %* Set command line: "X:\sms\bin\i386\OSDSETUPHOOK.EXE" "/enable:C:\Windows\system32" /version:6.1 Executing command line: "X:\sms\bin\i386\OSDSETUPHOOK.EXE" "/enable:C:\Windows\system32" /version:6.1 Enabling OSD setup hook Unable to capturethe volume image (0x80070020) Failed to capture system image. The process cannot access the file because it is being used by another process. (Error: 80070020; Source: Windows) Process completed with exit code 0 Finished with error code 0x80070020. The operating system reported error 2147942432: The process cannot access the file because it is being used by another process. I have read threw a lot of posts with this message and they all seem to mention system partitions/restore partitions, which doesn't apply to me. I have 2 partitions; the C Drive and a D Drive (the D Drive is just a storage drive for the my documents folder and has been standard practice for us always). Of course the person normally in charge of helping with SCCM is no longer here so I am kind of on my own here. Any help would be awesome. We are using SCCM 2007 R2 The reference machine is running windows 7

Error code 20 (hex) = 32 = "The process cannot access the file because it is being used by another process." Are you directly referencing the captured image in an image package? If so, that's bad joo-joos. A/V is also a possible culprit. No way for me/us to know for sure but you can use one of many tools like Process Explorer or Handle from the SysInternals suite to help find out who has the file locked.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Try puting a restart in just before you capture it. Blair Muller

what type of capture task sequence is it ? did you create a standard build and capture task sequence ? or are you using a custom task sequence My step by step SCCM Guides I'm on Twitter > ncbrady

Capture reference computer is easy. First of all, you'll need to build a capture media from the task sequence. Next, make sure you reference machine got all the software, drivers and updates you needed. Lastly, make sure that your reference machine is not join to any domain. If you are capturing Windows 7, Insert the capture media cd and autorun will begin Enter the information required. For example, reference image name, destination path, and account to the network path. The capture task will then begin to sysprep and capture your machine including the second partition D Drive. Hopes its helps you. Regards, Hau.

Hi, As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered" as the previous steps should be helpful for many similar scenarios. In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks,Yog Li -- Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.