Jump to content


anyweb

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

Recommended Posts

@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


Could not find CCM install folder. Don't use ccmerrors.dll

 

is the configmgr client installed ?

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

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.

 

 

Anyone had a crack at this one yet?

 

Today I'm going to try booting from "Legacy" mode on the Alienware, installing the OS and try the capture again.

Share this post


Link to post
Share on other sites
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.

 

Apparently it is bad idea to install and capture an OS with client on it because of it's unique identifier...but sure it is going to get overwritten with a new client at OSD time anyway at the setup configuration time!!

 

When exactly does it bomb out on you??

 

Have you tried to push out an OS to this alienware machine to see if it is successful...rather than trying to capture it unsucessfully....see if it works and if not then it is a driver issue!!

 

And also could you not install the OS on a VM with custom software if needed and capture this.....package your drivers for your alienware machine and attach to TS...same outcome you'll find as trying to capture the alienware OS...and redeploying it!!

 

One driver has to be injected into the boot.wim in order for a connection to be made to the share at PXE enviornment time but also in some cases you need to pump in the driver into the OS via a driver package after the OS is installed at apply driver time....I had an awful time with a particular model until I actually added the NIC driver to the boot.wim and also injected it into the OS at apply driver time!!

 

Edit: Once you injected the drivers into the boot.wim....you have created a new capture ISO and specifying to use the new updated boot.wim I gather???

If not then this could be your problem if you are using a pre-created capture ISO before you injected the driver into the boot.wim!!

 

Rocket Man

Share this post


Link to post
Share on other sites

I have tried to push the image to it. It fails, not sure when though.

 

The VM build up is a good idea and I might try that if my experiment today doesn't work.

 

I have the NIC drivers as well as the storage drivers in this boot image. I thought you needed both. If I'm capturing don't I already have the drivers for the OS? I'm doing the capture from media, not sure how or why I would need to add drivers to a reference image I am capturing.

 

I have created so many capture ISOs it's hilarious. I have done what your talking about before though. Now I make sure to create a new one right after I update the DP. I tried to use the USB version, but it won't autorun and I didn't feel like negotiating another bug. So, I've just been burning discs.

 

In the log it mentions the issue with the BIOS settings. So, I'm hoping changing that from UEFI to Legacy will be the solution.

Share this post


Link to post
Share on other sites

In the log it mentions the issue with the BIOS settings. So, I'm hoping changing that from UEFI to Legacy will be the solution.

 

Have you run into this issue before?

Share this post


Link to post
Share on other sites

For those of you following my little saga (palpable silence) the BIOS setting on the alienware was the key. Once I changed the bios setting from UEFI to Legacy and re-built the OS on top, everything else remaining the same, the capture media worked. I have successfully captured the image.

 

Now...if I can deploy it to another machine....

 

Thanks for all the comments. They did help. Once again, Niall's most often posted comment "what does the smsts.log say" paid off.

 

It's been a long frustrating week. All you admins out there have a beer on me.

Share this post


Link to post
Share on other sites

For those of you following my little saga (palpable silence) the BIOS setting on the alienware was the key. Once I changed the bios setting from UEFI to Legacy and re-built the OS on top, everything else remaining the same, the capture media worked. I have successfully captured the image.

 

Now...if I can deploy it to another machine....

 

Thanks for all the comments. They did help. Once again, Niall's most often posted comment "what does the smsts.log say" paid off.

 

It's been a long frustrating week. All you admins out there have a beer on me.

 

Can i ask you why you are making the golden image on physical hardware? its mutch easyer, and mutch less hassle to get it to work on a VM. And you really get the minimal ammount of drivers in that golden image.

  • Like 1

Share this post


Link to post
Share on other sites

When trying to create my Capture Media I am unable to select a Distribution Point. What would this be the case and how would I fix that? Thanks.

 

Ok, I figured it out. I needed to distrubute the boot images to the ditribution point first. in the book System Center 2012 Configuration Manager Unleashed on page 1043 it should tell/remind you to do this but it doesn't.

Share this post


Link to post
Share on other sites

Hi - Just wondering if this is the process I would use to create a wim file of a fully patched Windows 8 machine in order to use it to create Windows to Go devices on USB? Currently the wim file we get from the WIndows 8 Enterprise install is the base image, and I would like to be able to patch up a Windows 8 machine fully, create a wim file and then use that wim file to create the Windows to Go devices.

Share this post


Link to post
Share on other sites

I have a question to this guide:

 

I followed it and everything works fine when I implement the captured image in a Task Sequence in ConfigMgr 2012, but which step in my Task Sequence must I modify/add to get the device in ConfigMgr2012 to stay with the same name in ConfigMgr after I have deployed my captured image with the Task Sequence?

Share this post


Link to post
Share on other sites

So I imagine that this can be done using PXE boot instead of a capture media. So how would I do that?

 

Love your posts. They have been a godsend in my efforts to learn SCCM

 

WD

Share this post


Link to post
Share on other sites

Thanks so much for supplying this info. Your site is invaluable!!

 

Here's my problem. I have a build put together on a source PC. I have no problem capturing a .wim of this build with capure media created with SCCM2012 until the final step of the build. My last step is to install the config man client. I stop the SMSAgentHost service and try to capture the .wim but just get an error. This machine has never been domain joined. Other documentation I've found states it is necessary to delete certificates to enable image capture but isn't specific about which certs to remove etc.

 

Any help would be appreciated.

Thanks in advance,

Rif

Share this post


Link to post
Share on other sites

so you are not using capture media, but instead manually installing and configuring a computer and then trying to capture it ? I would recommend using the build and capture process for that instead

Share this post


Link to post
Share on other sites

There is a method to my madness and it is geared towards a specific project. We have a large rollout of approximately 4,000 PCs. I am simply supplying a Wim to our hardware vendor for offsite, offline imaging. I have no issues capturing the wim until I add the sccm client to the build. I have found some info regarding this method but nothing specific. I'm just looking for some guidance.

 

Normally we would be imaging in-house via task sequence but again this is for offsite, pre-imaging of vendor supplied hardware of one specific model.

 

Thanks again,

Rif

Share this post


Link to post
Share on other sites

ok so why are you stopping the service ? after installing the client are you trying to capture it using the capture media or another way ?

Share this post


Link to post
Share on other sites

Once the Configman client is installed the capture task sequence fails. Apparently this is known and expected behavior. One recommendation I found stated to stop the SMSAgentHost service and to delete the associated certificates and then the capture sequence would complete without issue. It is the deletion of these certs that I'm looking for guidance with. Which certs etc.

 

Thanks again!!

Share this post


Link to post
Share on other sites

Why is it required that the machine have the ConfigMgr Client Agent installed on it?

 

see below

Share this post


Link to post
Share on other sites

I am having what I believe is an issue with the capture image portion of sccm 2012. I started the capture 2 days ago and it is working, but on a capture that is probably going to be 3GB+, it is on 25MB. Any ideas?

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...