Tag Archives: Automatic Deployment Rule

SCCM Current Branch Automatic Deployment Rule Will Not Run

SCCM Current Branch (1702).


Automatic Deployment Rule was running without error but not doing anything.  Downloading updates manually was working so not a problem with Internet connection etc.


The share/folder on the SCCM Site Server where the software updates were meant to download to (the Package Source folder) needed a tweak to the permissions.

Add the server SYSTEM account to the permissions for the folder and the share with the appropriate rights to be able to write to both.

Amending a SCCM 2012 Automatic Deployment Rule to Create a new Deployment Package


If you use a SCCM 2012 Automatic Deployment Rule (ADR) to deploy software updates, over time the package can become quite large.  This procedure details the steps taken to link a new package to an existing ADR.  A good time to do this is early January (before Patch Tuesday) as this will result in packages/folders for each calendar year.

  • Create a new folder for the package source files, typically under a shared folder containing all your software update source files (needs to be referenced by a UNC later in this procedure).
  • In the SCCM Admin Console, open the Properties dialogue for the relevant ADR.
  • On the General tab select the Create a new Software Update Group.
  • On the Deployment Package tab select Create a new Deployment Package.
  • Give the package a meaningful name.
  • Browse to the package source folder created earlier to set the Package Source.
  • Run the rule so it creates the new software update group and new package.
  • View the RuleEngine log file on the SCCM server to monitor the actions instigated by running the ADR.
After the Running of the Rule is Complete
  • Access the Deployment Packages node, right-click the new package that has just been created by the ADR and select Distribute Content.
  • Access the Software Update Group node.
  • Rename the group the ADR has just created so it reflects the fact it is the software update group created by the ADR, e.g. Server-2012-ADR-SUG.
  • Return the properties page of the ADR just changed.
  • On the General tab select Add to an Existing Software Update Group.  This ensures that next time the rule is run it uses the group just created and does not keep creating a new group every month.

Note:  When editing an ADR the link to the deployment package is not maintained thus the need to distribute the package.  This step will be automated next time the rule is run.

Note:  Be careful if you run an ADR manually as the deadline will be set based on the Specific time setting on the Deployment Schedule tab of the ADR.  The automatic rule probably sets this to the early hours of the morning, e.g. the rule runs at 05:00 and the deadline is 05:00 seven days later.  If the ADR is run manually the deadline will be exactly seven days from when the rule is run and this may be during the working day which you probably don’t want.