locked
Image Captured from Build & Capture Fails during OSD RRS feed

  • Question

  • Good morning!

    We are having an issue with our SCCM 2012 SP1 OSD deployment.  If we build out a Windows 7 WIM outside of SCCM, do all of the updates, and then capture it, the OSD deployment works fine.  If we use a build and capture for Windows 8/8.1, everthing works fine.  If we use a build and capture task sequence from within SCCM 2012 to generate a Windows 7 image, it will successfully image and then capture and to make a WIM, however, that image does not function when we try to deploy it. 

    When we do the build and capture, everything goes like I think it should, the capture piece "parks" the SCCM client, syspreps the machine, reboots, and captures the image.  When the image is deployed, it lays down the image and configures it fine, but when it gets to the client piece, it tries to install, and that's where everything breaks down. 

    The logs we're seeing when we deploy the B&C image are as follows:

    In the smsts.log file, we get error that the Client installation failed, code 1.  Later, it says "Failed to install SMS Client (0x80004005)" - which I'm pretty sure means it's a permission / access denied issue.  Earlier in the log, it has a line reading:

    Unable to read SMS client cert from environment. Not restoring SMS client cert.

    ccmsetup.log - ends with these lines:

    File C:\WINDOWS\ccmsetup\{59A0EA77-D28C-4286-83A6-04BB57B9CDD6}\client.msi installation failed. Error text: ExitCode: 1603
    Action:
    ErrorMessages:
     ccmsetup 10/21/2013 11:18:01 AM 2436 (0x0984)
    Client installation has failed too many times. Ccmsetup will now abort. ccmsetup 10/21/2013 11:18:01 AM 2436 (0x0984)
    A Fallback Status Point has not been specified.  Message with STATEID='313' will not be sent. ccmsetup 10/21/2013 11:18:01 AM 2436 (0x0984)
    InstallFromManifest failed 0x80070643 ccmsetup 10/21/2013 11:18:01 AM 2436 (0x0984)
    Deleted file C:\WINDOWS\ccmsetup\ccmsetup.cab.download ccmsetup 10/21/2013 11:18:01 AM 2436 (0x0984)
    Deleted file C:\WINDOWS\ccmsetup\ccmsetup.xml ccmsetup 10/21/2013 11:18:01 AM 2436 (0x0984)
    CcmSetup failed with error code 0x80070643 ccmsetup 10/21/2013 11:18:01 AM 2436 (0x0984)

    We're sort of at a loss for what may be going on and I think we've run out of places to check.  All of our accounts line up with what they're supposed to and deployment via a non-B&C image work just fine.  Any information or thoughts into what might be going on would be appreciated. 

    Thanks.

    Scott

    Tuesday, October 22, 2013 2:01 PM

Answers

  • (0x80004005)" - which I'm pretty sure means it's a permission / access denied issue.

    Incorrect. The error code in this hresult is actually "4005" and not "5". This error code is specific to ConfigMgr and means "Generic Failure" which means to need to do some digging.

    1603 (= 0x80070643) is Windows Installer's equivalent "Generic Failure" message also.

    Thus, you need to examine the log file Torsten pointed out (client.msi.log) and look for "return value 3". That will indicate where Windows Installer gave up so you need look somewhere above that line to determine what actually failed and caused it to give up.


    Jason | http://blog.configmgrftw.com

    Wednesday, October 23, 2013 2:45 PM

All replies

  • Examine client.msi.log.

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, October 22, 2013 2:41 PM
  • (0x80004005)" - which I'm pretty sure means it's a permission / access denied issue.

    Incorrect. The error code in this hresult is actually "4005" and not "5". This error code is specific to ConfigMgr and means "Generic Failure" which means to need to do some digging.

    1603 (= 0x80070643) is Windows Installer's equivalent "Generic Failure" message also.

    Thus, you need to examine the log file Torsten pointed out (client.msi.log) and look for "return value 3". That will indicate where Windows Installer gave up so you need look somewhere above that line to determine what actually failed and caused it to give up.


    Jason | http://blog.configmgrftw.com

    Wednesday, October 23, 2013 2:45 PM