CCMSetup failed with error code 0x87d0029e

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.

12
Leave a Reply

avatar
3 Comment threads
9 Thread replies
0 Followers
 
Most reacted comment
Hottest comment thread
newest oldest most voted
Fernando the IT
Guest
Fernando the IT

Thanks so much, I was dealing with this issue for days, once I ran these commands it worked like magic, thanks so much once again n 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. 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… Read more »

Hugo Martinez Peregrina
Guest
Hugo Martinez Peregrina

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

Here the CCMsetup.log

<![LOG[]LOG]!>

Zach
Guest
Zach

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

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. AcceptRead More