I am not doing any of the patches, just the base SP1 client. I hadn't thought about any of the CU patches. I am installing software updates just fine in my B&C so I know the SMSMP switch it working.
SMSCACHESIZE=51200 SMSMP=servername CCMLOGMAXSIZE=5000000 CCMLOGMAXHISTORY=5 If the next build doesn't work, I will try adding the CU3 patch as well. Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Jeremy Sihassen Sent: Friday, March 14, 2014 5:09 PM To: [email protected] Cc: [email protected] Subject: Re: [mssms] RE: File already exists 80070050 capturing .wim in WinPE? What have you set inside the Setup Windows and Configuration Manager? You should add the SMSMP switch and a KB that could help. I can't recall which one. I'll be able to give you the num 2014-03-14 20:34 GMT+01:00 Daniel Ratliff <[email protected]<mailto:[email protected]>>: Well now it appears to be an issue with my build or maybe the VM. All three steps failed with the exact same error. That eliminates an account or network share issue. I used this same exact VM to build an image a few weeks ago and had no issue. I am going to make a fixed disk and try that out. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Daniel Ratliff Sent: Friday, March 14, 2014 10:04 AM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: File already exists 80070050 capturing .wim in WinPE? The VM was using a thin-provisioned disk, so to be safe I bumped it up another 30GB. I still got the same error so I did a test with multiple Capture steps. 1. Capture to same network share, using same account a. Failed, same error 2. Capture to different folder on same share, using same account a. I hadn't created the folder beforehand, failed 3. Capture to different share, using same account a. Same error as #1, BINGO! This tells me it's the account not the share, so I just setup another B&C and its running now. 1. Capture to same network share, same account 2. Capture to same network share, different account 3. Capture to different network share, different account It usually takes about 4 hours to B&C, so I hope to have my answer today! Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jason Sandys Sent: Tuesday, March 11, 2014 5:08 PM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: File already exists 80070050 capturing .wim in WinPE? 0x80070070 = "There is not enough space on the disk." J From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Tuesday, March 11, 2014 3:42 PM To: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: [mssms] File already exists 80070050 capturing .wim in WinPE? I am having a heck of a time with this one. My build and capture task sequence will not capture the .wim to the network. I have double-checked the access account, checked the permissions on the share, verified the variables are set properly, and I continue to get the below error. Searching online didn't give me much to go on. ConfigMgr 2012 SP1 CU3 MDT 2012 U1 integrated WinPE 4.0 .wim is Win7x64 My next steps are to try a different share or different network account. I did this B&C back in October without issue. Any other ideas? Validating system for capture... CaptureSystemImage 3/10/2014 4:29:55 PM 1044 (0x0414) Target OS system root is C:\WINDOWS CaptureSystemImage 3/10/2014 4:29:55 PM 1044 (0x0414) OfflineRegistry::Init("C:\WINDOWS") CaptureSystemImage 3/10/2014 4:29:55 PM 1044 (0x0414) Loading offline registry hive "C:\WINDOWS\system32\config\software" into HKLM\OfflineRegistry1 CaptureSystemImage 3/10/2014 4:29:55 PM 1044 (0x0414) Loading offline registry hive "C:\WINDOWS\system32\config\system" into HKLM\OfflineRegistry2 CaptureSystemImage 3/10/2014 4:29:57 PM 1044 (0x0414) CurrentControlSet is mapped to ControlSet001 CaptureSystemImage 3/10/2014 4:29:57 PM 1044 (0x0414) Sysprep state set to IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE CaptureSystemImage 3/10/2014 4:29:57 PM 1044 (0x0414) Sysprep.exe has marked the OS as generalized for deployment. CaptureSystemImage 3/10/2014 4:29:57 PM 1044 (0x0414) Boot volume is C:\ CaptureSystemImage 3/10/2014 4:30:06 PM 1044 (0x0414) Volume A:\ will not be captured: not a fixed hard drive CaptureSystemImage 3/10/2014 4:30:06 PM 1044 (0x0414) Volume D:\ will not be captured: not a fixed hard drive CaptureSystemImage 3/10/2014 4:30:06 PM 1044 (0x0414) Volume X:\ will not be captured: not a fixed hard drive CaptureSystemImage 3/10/2014 4:30:06 PM 1044 (0x0414) Preparing system for capture... CaptureSystemImage 3/10/2014 4:30:06 PM 1044 (0x0414) Successfully loaded the BCD boot system CaptureSystemImage 3/10/2014 4:30:06 PM 1044 (0x0414) Connection request for "\\server\share\osd\capture" CaptureSystemImage 3/10/2014 4:30:06 PM 1044 (0x0414) Connecting to "\\server\share\osd\capture" CaptureSystemImage 3/10/2014 4:30:06 PM 1044 (0x0414) Successfully connected to "\\server\share\osd\capture" CaptureSystemImage 3/10/2014 4:30:06 PM 1044 (0x0414) Creating image file \\server\share\osd\capture\Win7Base_SQLTools_0114.wim CaptureSystemImage 3/10/2014 4:30:06 PM 1044 (0x0414) Starting system capture... CaptureSystemImage 3/10/2014 4:30:06 PM 1044 (0x0414) Skipping non-local logical drive: A: CaptureSystemImage 3/10/2014 4:30:06 PM 1044 (0x0414) Adding logical drive: C: CaptureSystemImage 3/10/2014 4:30:06 PM 1044 (0x0414) Skipping non-local logical drive: D: CaptureSystemImage 3/10/2014 4:30:06 PM 1044 (0x0414) Skipping non-local logical drive: X: CaptureSystemImage 3/10/2014 4:30:06 PM 1044 (0x0414) Unloading offline SOFTWARE registry hive CaptureSystemImage 3/10/2014 4:30:06 PM 1044 (0x0414) Unloading offline SYSTEM registry hive CaptureSystemImage 3/10/2014 4:30:07 PM 1044 (0x0414) Command line for extension .EXE is "%1" %* CaptureSystemImage 3/10/2014 4:30:07 PM 1044 (0x0414) Set command line: "X:\sms\bin\i386\OSDSETUPHOOK.EXE" "/disable:C:\WINDOWS\system32" /version:6.1 CaptureSystemImage 3/10/2014 4:30:07 PM 1044 (0x0414) Executing command line: "X:\sms\bin\i386\OSDSETUPHOOK.EXE" "/disable:C:\WINDOWS\system32" /version:6.1 CaptureSystemImage 3/10/2014 4:30:07 PM 1044 (0x0414) Disabling OSD setup hook OSDSetupHook 3/10/2014 4:30:07 PM 1116 (0x045C) Process completed with exit code 0 CaptureSystemImage 3/10/2014 4:30:07 PM 1044 (0x0414) Capturing C:\, volume 1 of 1 CaptureSystemImage 3/10/2014 4:30:07 PM 1044 (0x0414) Capturing volume C: CaptureSystemImage 3/10/2014 4:30:07 PM 1044 (0x0414) Skipping \pagefile.sys CaptureSystemImage 3/10/2014 4:30:07 PM 1044 (0x0414) Skipping \System Volume Information CaptureSystemImage 3/10/2014 4:30:46 PM 1044 (0x0414) Skipping \Windows\CSC CaptureSystemImage 3/10/2014 4:30:50 PM 1044 (0x0414) Skipping C:\Windows\Setup\scripts\SetupComplete.cmd CaptureSystemImage 3/10/2014 4:31:06 PM 1044 (0x0414) Skipping C:\Windows\System32\OSDSETUPHOOK.EXE CaptureSystemImage 3/10/2014 4:31:22 PM 1044 (0x0414) Skipping C:\Windows\System32\_SMSOSDSetup CaptureSystemImage 3/10/2014 4:31:26 PM 1044 (0x0414) Skipping C:\_SMSTaskSequence CaptureSystemImage 3/10/2014 4:32:46 PM 1044 (0x0414) WIM has entered capture phase for 103160 items CaptureSystemImage 3/10/2014 4:32:46 PM 1044 (0x0414) WIM retry: C:\_SMSTaskSequence\WIM4062.tmp (0x80070070) CaptureSystemImage 3/10/2014 4:45:09 PM 1460 (0x05B4) WIM error:C:\Windows\Installer\f1af.msp. The file exists. (Error: 80070050; Source: Windows) CaptureSystemImage 3/10/2014 4:45:24 PM 1460 (0x05B4) Failure detected. Aborting WIM operation CaptureSystemImage 3/10/2014 4:45:24 PM 1044 (0x0414) hVolumeImage = WIMCaptureImage( m_hImageFile, const_cast<LPWSTR>(pathTargetVolume.c_str()), WIM_FLAG_VERIFY ), HRESULT=80070050 (e:\qfe\nts\sms\framework\tscore\wimfile.cpp,569) CaptureSystemImage 3/10/2014 4:45:25 PM 1044 (0x0414) Unable to capture the volume image (0x80070050) CaptureSystemImage 3/10/2014 4:45:25 PM 1044 (0x0414) ImageFile.CaptureVolumeImage( (*itr), &saFilesToNotCapture), HRESULT=80070050 (e:\nts_sccm_release\sms\client\osdeployment\capturesystemimage\capturesystemimage.cpp,747) CaptureSystemImage 3/10/2014 4:45:25 PM 1044 (0x0414) CaptureSystemImage( progressUi, slVolumesToCapture, sOfflineSystemRoot, ImageFile), HRESULT=80070050 (e:\nts_sccm_release\sms\client\osdeployment\capturesystemimage\capturesystemimage.cpp,912) CaptureSystemImage 3/10/2014 4:45:25 PM 1044 (0x0414) Failed to capture system image. The file exists. (Error: 80070050; Source: Windows) CaptureSystemImage 3/10/2014 4:45:25 PM 1044 (0x0414) Closing image file \\server\share\osd\capture\Win7Base_SQLTools_0114.wim CaptureSystemImage 3/10/2014 4:45:25 PM 1044 (0x0414) Command line for extension .EXE is "%1" %* CaptureSystemImage 3/10/2014 4:45:25 PM 1044 (0x0414) Set command line: "X:\sms\bin\i386\OSDSETUPHOOK.EXE" "/enable:C:\WINDOWS\system32" /version:6.1 CaptureSystemImage 3/10/2014 4:45:25 PM 1044 (0x0414) Executing command line: "X:\sms\bin\i386\OSDSETUPHOOK.EXE" "/enable:C:\WINDOWS\system32" /version:6.1 CaptureSystemImage 3/10/2014 4:45:25 PM 1044 (0x0414) Enabling OSD setup hook OSDSetupHook 3/10/2014 4:45:25 PM 1028 (0x0404) Process completed with exit code 0 CaptureSystemImage 3/10/2014 4:45:25 PM 1044 (0x0414) Finished with error code 0x80070050 CaptureSystemImage 3/10/2014 4:45:25 PM 1044 (0x0414) Process completed with exit code 2147942480<tel:2147942480> TSManager 3/10/2014 4:45:25 PM 560 (0x0230) !--------------------------------------------------------------------------------------------! TSManager 3/10/2014 4:45:25 PM 560 (0x0230) Failed to run the action: Capture the Reference Machine. The file exists. (Error: 80070050; Source: Windows) TSManager 3/10/2014 4:45:25 PM 560 (0x0230) Daniel Ratliff The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
