I have just started setting up a new System Center 2012 Configuration Manager server to test in my environment came up against an error that really didn’t make any sense at first.
After running the Automatic Deployment Rule it came up with the Error Code 0x87D20417 further investigation inside the logs in (C:\Program Files\Microsoft Configuration Manager\Logs) found the following entry in the ruleengine.log
Failed to download the update from internet. Error = 5
There was also a status message from SMS_RULE_ENGINE with Severity: Error
Content download failed.
Message: Failed to download one or more content files.
Source: SMS Rule Engine.
When I configured the the new Deployment Package in the “Select deployment package for this automatic deployment rule” section I created a new file share for the package. I set the NTFS permissions as specified in the documentation “Operations and Maintenance for Software Updates in Configuration Manager“.
What I failed to do was allow CHANGE permissions at the share level as I left that at the default READ ONLY setting.
Once I added the CHANGE permission the Automatic Deployment Rule ran and downloaded the software successfully.
7 replies on “Automatic Deployment Rules – Download Failed – System Center 2012 Configuration Manager”
Hi John, Thanks, it is working.
Cheers,
Had the same problem, but for me the permissions were correctly set. The solution for me was the Software Deployment Package source was on the site server. Once I moved the package source to another server, it started working.
HI,
thanks for this, i had to change the rights to the Share of my deployment package. And not the rights on the WSUS content. I’ve added authenticated users and it worked.
thanks !
Thank you!!!!!!!! If only Share Permissions and Folder/Local Permissions were the same thing…… 🙂
Thanks,
Working fine!! 🙂
If your Package source share is on the SCCM server, Go to share permissions and just add the SYSTEM account of SCCM server (not AD). It will solve the problem.
Thanks, Surender. Adding SQL-Server\SYSTEM to the share permissions with full access worked in my case.