Jump to content


anyweb

How can I capture an image using capture media in ConfigMgr 2012

Recommended Posts

Thanks For all the great info on your site..

I am attempting to make a USB key with a Stanalone media on a USB key and I am getting problems. I found a command line

 

"C:\Program Files\Microsoft Configuration Manager\AdminConsole\bin\i386\CreateMedia.exe" /K:full /P:"Server.domain" /S:"A2A" /C:"" /D:"server.domain" /L:"Configuration Manager 2012" /A:"A2A00026" /Z:"False" /T:"CD" /M:"44482" /F:"C:\HP8200x64ADMIN.iso"

 

Which was suggested to get around the issue with large size USB sticks.

 

<![LOG[OS image has a size 18242 Mb exceeding max file size 4095 Mb]LOG]!><time="10:15:54.826+420" date="08-07-2012" component="CreateTsMedia" context="" type="3" thread="11868" file="mediagenerator.cpp:341">

<![LOG[uFD media does not support this file size]LOG]!><time="10:15:54.827+420" date="08-07-2012" component="CreateTsMedia" context="" type="3" thread="11868" file="mediagenerator.cpp:344">

<![LOG[Failed to create media (0x80004005)]LOG]!><time="10:15:54.827+420" date="08-07-2012" component="CreateTsMedia" context="" type="3" thread="11868" file="createtsmedia.cpp:331">

<![LOG[CreateTsMedia failed with error 0x80004005, details='']LOG]!><time="10:15:54.827+420" date="08-07-2012" component="CreateTsMedia" context="" type="1" thread="11868" file="createtsmedia.cpp:341">

<![LOG[MediaGenerator::~MediaGenerator()]LOG]!><time="10:15:54.827+420" date="08-07-2012" component="CreateTsMedia" context="" type="1" thread="11868" file="mediagenerator.cpp:214">

<![LOG[Media creation process that was started from Admin Console completed.

]LOG]!><time="10:15:54.867+420" date="08-07-2012" component="CreateTsMedia" context="" type="1" thread="1208" file="createmedia.cpp:1188">

<![LOG[CreateMedia.exe finished with error code 80004005]LOG]!><time="10:15:54.867+420" date="08-07-2012" component="CreateTsMedia" context="" type="2" thread="1208" file="createmedia.cpp:1239">

 

I am new to SCCM 2012 but was familar with 2003. Has this issue been resolved where I can create a stand alone on a 32-64 gig USB key? What should be straight forward is getting very convoluted....

Any insights woul be greatly appreciated.

Share this post


Link to post
Share on other sites

Hi All,

 

I've had an awful experience with SCCM Capture today. I created capture media without problems, then I unjoined the target machine from domain and joined to workgroup.

I then ran the USB and it eventually triggered a restart, but then failed almost instantly, capture failed error 0x80070032.

 

I had no choice but to restart the machine, but then my nightmare began.

The machine wouldn't boot into Windows, stating that the C:\Windows\System32\Config\System was missing or corrupt.

 

I tried several things to recover:

 

1) Tried copying the missing system file from C:\Windows\Repair to C:\Windows\System32\Config\System

2) Tried copying ALL files from C:\Windows\Repair to C:\Windows\System32\Config

 

Ultimately, all these steps introduced more problems, including errors relating to LSASS.EXE, Windows Activation, etc.

 

I think that ultimately my issue is that the contents of C:\sysprep I placed on the target machine must have been the wrong version or something, because it seems the sysprepping failed and left the machine in this bizarre state.

 

I've resorted to building a replacement machine, but for the time being I'm going to very much shy away from using the SCCM capture until I learn to be less of a noob and more confident in what I'm doing!

 

Let this be a lesson to others :)

 

Daniel

Share this post


Link to post
Share on other sites

@dverbern, had a similar problem today whilst trying to capture a W7 64b SP1 machine, yesterday we had no problem capturing a W7 32b machine

 

didn't get your error 0x80070032 though...

 

these are the last lines of the log:

<![LOG[Adding BCD entry for C:\_SMSTaskSequence\WinPE\sources\boot.wim]LOG]!><time="16:57:18.377-120" date="09-13-2012" component="TSManager" context="" type="1" thread="1420" file="bootconfigimplbcd.cpp:162">

<![LOG[Mounting \Device\HarddiskVolume1 at Z:]LOG]!><time="16:57:23.306-120" date="09-13-2012" component="TSManager" context="" type="1" thread="1420" file="mountpoint.cpp:49">

<![LOG[retValue == true, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\bcdhandler.cpp,490)]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="0" thread="1420" file="bcdhandler.cpp:490">

<![LOG[bcdSystemStore.ImportStore(sSourceStorePath), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\bootconfigimplbcd.cpp,771)]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="0" thread="1420" file="bootconfigimplbcd.cpp:771">

<![LOG[m_pBootConfig->saveStore(pBootVolume), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\bootsystem.cpp,474)]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="0" thread="1420" file="bootsystem.cpp:474">

<![LOG[unmounting volume Z:\]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="1" thread="1420" file="mountpoint.cpp:104">

<![LOG[bootSystem::import(), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\bootsystem.cpp,1019)]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="0" thread="1420" file="bootsystem.cpp:1019">

<![LOG[pNewBootSystem->import(), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\bootimage.cpp,637)]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="0" thread="1420" file="bootimage.cpp:637">

<![LOG[Could not find CCM install folder. Don't use ccmerrors.dll]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="0" thread="1420" file="string.cpp:1278">

<![LOG[Failed to install boot image.

Unknown error (Error: 80004005; Source: Unknown)]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="3" thread="1420" file="bootimage.cpp:646">

<![LOG[TS::Boot::BootImage::InstallStagedImageToHdd(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\engine.cxx,826)]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="0" thread="1420" file="engine.cxx:826">

<![LOG[Could not find CCM install folder. Don't use ccmerrors.dll]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="0" thread="1420" file="string.cpp:1278">

<![LOG[Failed to install boot image ZOL00004.

Unknown error (Error: 80004005; Source: Unknown)]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="3" thread="1420" file="engine.cxx:826">

<![LOG[Failed to reboot the system. Error 0x(80004005)]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="3" thread="1420" file="engine.cxx:939">

<![LOG[RebootSystem(pwszRebootMessage, dwRebootTimeout, dwRebootReason, bRebootWinPE), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\engine.cxx,575)]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="0" thread="1420" file="engine.cxx:575">

<![LOG[Could not find CCM install folder. Don't use ccmerrors.dll]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="0" thread="1420" file="string.cpp:1278">

<![LOG[Failed to initialize a system reboot.

Unknown error (Error: 80004005; Source: Unknown)]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="3" thread="1420" file="engine.cxx:575">

<![LOG[CheckForRebootRequest(&bRebootInitiated), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\engine.cxx,274)]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="0" thread="1420" file="engine.cxx:274">

<![LOG[Could not find CCM install folder. Don't use ccmerrors.dll]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="0" thread="1420" file="string.cpp:1278">

<![LOG[Fatal error is returned in check for reboot request of the action (Prepare Operating System).

Unknown error (Error: 80004005; Source: Unknown)]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="3" thread="1420" file="engine.cxx:274">

<![LOG[An error (0x80004005) is encountered in execution of the task sequence]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="3" thread="1420" file="engine.cxx:349">

<![LOG[Do not send status message in full media case]LOG]!><time="16:57:24.367-120" date="09-13-2012" component="TSManager" context="" type="1" thread="1420" file="utils.cpp:4736">

 

 

have to go to the customer again tomorrow, hope it runs then...

Share this post


Link to post
Share on other sites

I'm having this exact issue with an Alienware R4. The capture media runs fine until the end of the sysprep routine. At some point it dumps the NIC completely and results in a 0x80004005. I have created a boot image specifically for this PC which has the realtek 64 bit driver for the NIC and the storage drivers, Intel C600 series chipset SATA AHCI Controller driver (iaAHCI.inf and iaStorA.inf). I have tried everything, been working on it for three days now. All aspects of OSD are working properly for other PCs (HP elitebook 8560w). I'm at a complete loss.

 

Everything I have read to this point had said DO NOT install the ccm client, but these instructions say you should. So, I am going to try that now. We'll see, I guess.

Share this post


Link to post
Share on other sites

So this has been just a real treat. I'm attaching the log for the failed capture, but here is an interesting bit.

 

 

 

 

 

<![LOG[Failed to install boot sector. C:\_SMSTaskSequence\WinPE\SMS\bin\i386\bootsect.exe /NT60 SYS /MBR failed (1)

stdout:

This tool can only be run on systems booted using a PC/AT BIOS. This systemwas booted using EFI or some other firmware type.

stderr:

]LOG]!><time="17:41:25.149+360" date="09-13-2012" component="TSManager" context="" type="3" thread="2596" file="bootsector.cpp:83">

<![LOG[Failed to install boot image.

Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="17:41:25.149+360" date="09-13-2012" component="TSManager" context="" type="3" thread="2596" file="bootimage.cpp:646">

<![LOG[Failed to install boot image CCM0001A.

Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="17:41:25.149+360" date="09-13-2012" component="TSManager" context="" type="3" thread="2596" file="engine.cxx:826">

<![LOG[Failed to reboot the system. Error 0x(80004005)]LOG]!><time="17:41:25.149+360" date="09-13-2012" component="TSManager" context="" type="3" thread="2596" file="engine.cxx:939">

 

 

This is the part where everything starts to go pear shaped.

 

Any help would be superb.

smsts.log

Share this post


Link to post
Share on other sites

is the configmgr client installed ?

no, it isn't

 

the capture of the 64bit machine failed again today...

same error, so what's next?

 

edit: now I see why I couldn't boot after this failed capture: bcdedit shows nothing!

 

edit2: somehow I got to this http://technet.microsoft.com/en-us/library/cc749510%28WS.10%29.aspx but I did not have duplicate entries

strange thing also is that the disk management console shows only 2 partitions while diskpart reveals three

 

going to use a VM as reference machine

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.