Thursday, April 10, 2014

Configuration Manager Client Upgrade Package Distribution Failed

Whenever you setup a new distribution point, the system will automatically distribute 2 packages to the distribution point.
1. Configuration Manager Client Package
2. Configuration Manager Client Upgrade Package

But somehow the Configuration Manager Client Upgrade Package failed to distribute to the distribution point. The upgrade package is hidden, hence unable to redistribute the upgrade package like normal package. Therefore, we have to trick the system to redistribute the packages.

1. Open an empty notepad and save it as client.acu
2. Copy the client.acu to the inboxes\ folder at the top-level site
3. Monitor the hman.log to check whether the Client Upgrade package gets updated


  1. I have been looking for an answer to this issue for weeks. I attempted picking this out of WMI, removed manually from the SCCMContentLib, and everything else I could find on the internet. This solved the problem in about 1 second.

    Thanks a million for this very simple fix!


  2. Thank you. I was having an issue with one DP (and this package) and this solved it quickly. Much appreciated.

  3. Awesome - this resolved the issue for our environment.

    Huge Thanks
    Paul K

  4. Thanks for this. This also solved my issue.

  5. One IMPORTANT fact about doing this.... it also update the Client Package! Not only the upgrade package...

  6. Thank you so much! this solved our problem too!

  7. help me a lot!
    Bless you!

  8. Excellent fix - thanks very much for sharing it!

  9. My Cm client package still says INVALID in the Content Library Explorer. Any idea to fix that?

  10. Creating task sequence media was failing on an incorrect hash value, which turned out to be the Client Package.

    Followed this guide and now the logs show that package succesfully verifying and copying to media - happy days! Thanks for posting this.

  11. I am getting this error, i cannot find the inboxes\ locations to drop the file in.
    Because of special circumstances I was unable to use the primary site as my SUP role. I have a second server with WSUS installed and I have successfully (I think) set up the SUP role on that server. I have found the the message saying that the SUP role was successfully installed, and when I create a Client update package I can see the signatures get installed into the share. But I get the above noted error and no updates get released. This has been happening for over a month now and I just found this site. Is this referring to something other then what i'm trying to do I'm relatively new to SCCM.

    1. I found it here
      C:\Program Files\Microsoft Configuration Manager\inboxes\

  12. For me its still failing. I am using sccm 2106 in mu lab

  13. Thank you. This resolved the issue.

  14. I don't know what the fuck is this file. But this works like a magic. Thanks a lot!!

  15. Should the client.acu file get deleted after it successfully updates the packages?

  16. Did not work for me, Still stuck on in progress. the .acu file disappears, but no rebuild on either default package.
    thanks anyhwho

  17. Are you Looking for loan lender?Apply for a Personal or business loans,Visit us today!

  18. yes it wored like a charm. I Placed file in this location and i observed that it also quickly deletes that file from this location but now i can't see any error on this service.

    Path: C:\Program Files\Microsoft Configuration Manager\inboxes\