Blog on Microsoft and Other Technologies.

CCMSetup failed with error code 0x87d0029e

11 282

CCMSetup failed with error code 0x87d0029e – I was working on a new SCCM deployment for a customer. After a week the SCCM deployment was done successfully. I handed it over to the customer after doing some basic configuration specified by customer. However after few days the I got an issue from customer end. The customer reported that client push installation is not working. During the client push installation the error found was ccmsetup failed with error code 0x87d0029e. The client agent installation failed with same error even with manual installation. So digging up the error from log file and error screenshot looked something like this.

Site version ‘5.00.7958.1000’ is compatible. Client deployment will continue.
Successfully downloaded client files via BITS.
Validated file ‘C:\Windows\ccmsetup\vcredist_x86.exe’
A Fallback Status Point has not been specified.
CcmSetup failed with error code 0x87d0029e

CCMSetup failed with error code 0x87d0029eTroubleshooting CCMSetup failed with error code 0x87d0029e

To fix this error you could try the below steps.

  1. In most cases deleting the ccmsetup folder and installing the client agent resolves this issue. The errors comes up due to corrupt components inside the ccmsetup folder. The ccmsetup folder is located under C:\Windows. Therefore delete the ccmsetup folder and try pushing the client agent.
  2. Launch command prompt as Administrator. Type net stop winmgmt /y and press enter. Change the path to C:\windows\system32\wbem and rename the folder repository to repository.old. To do this use the command: rename repository repository.old. Next start the winmgmt process using net start winmgmt command. Winmgmt is WMI service within the SVCHOST process running under the LocalSystem account. Close the command prompt. Now try pushing the SCCM client agent and it should work well.

If the above solution did not help you, let me know it via comments. If you have any other client agent installation issue, feel free to create support thread at community forums.

11 Comments
  1. Zach says

    After updating to 1610 ALL of our deployments with fresh images are having this issue. Basically it will fail as soon as it get to the install step of the “Config. Manager Client Package” it will download but then goes straight into windows.
    (Log File if needed or curious)
    https://drive.google.com/file/d/0B46x9gWC8DQHMHpqMlRBMzFMcEE/view?usp=sharing

    1. Prajwal Desai says

      Thanks for sending the log files. I see the files required to install client agent are downloaded but the issue occurs during the installation. Can you confirm if you have deleted the ccmsetup folder and tried it ?.

      1. Zach says

        Sorry for the late response. We actually ended setting up a new SCCM server since our 2008 server was going to be no longer supported.

  2. Hugo Martinez Peregrina says

    after Rebuild WMI I am still getting the same error on the machine

    Here the CCMsetup.log

    <![LOG[]LOG]!>

    1. Prajwal Desai says

      I don’t see the error code, I need full log file. What’s in ccm.log file ?.

      1. Hugo Martinez Peregrina says

        Hi Prajwal,
        Thanks for take a look, here the CCMSETUP.log on onedrive

        https://1drv.ms/u/s!AqreJoZuWPbtgY4E393wI_ko5xeeww

        component=”ccmsetup” context=”” type=”0″ thread=”11940″ file=”util.cpp:2690″>

        <![LOG[
        ]LOG]!>

      2. Hugo Martinez Peregrina says
      3. Hugo Martinez Peregrina says
      4. Hugo Martinez Peregrina says

        Hi Prajwal

        Thanks for take a look on it
        I am updating the ccmsetup.log

        https://1drv.ms/u/s!AqreJoZuWPbtgY4E393wI_ko5xeeww

        but somehow my post is disappearing

      5. Hugo Martinez Peregrina says

        I am sharing the log on a onedrive link but look like is being erased
        Are onedrive links not allowed?

      6. Hugo Martinez Peregrina says

        well I finally solve issue copying source client installation files from a different repository so looks to be a corruption issue with one of those files

Leave A Reply

Your email address will not be published.