Configure multiple deployments in an Automatic Deployment Rule
When creating Automatic Deployment rules, it would be useful to be able to configure multiple deployments.
You may for example want test, pilot and live deployments to different collections and possibly with different settings. It doesn't make sense to have to create different rules with the same updates criteria just for additional deployments.
The CM administrator may choose to have the additional deployments disabled to allow for testing, but enabling a deployment leaves less room for error, and is less administrative overhead than creating these additional deployments manually each time for pilot/live.
It would also be useful to have the option to set deployments as available rather than required too (as far as I remember you can't do this from an ADR).
Thank you all for your comments and feedback!
This is complete and available in our 1511 release.
Brian Purdy commented
I like the idea of being able to use rules for more than just creating deployments. Perhaps, there could be rules that tag updates, download to specific packages, use variables, prioritize update distribution, create custom severity, generate/export reports, run scripts, or send emails. All of these things could be done independently in a specific order, whether or not a deployment is created or updated. Perhaps a rule could even trigger some sort of package/update cleanup process.
Ryan Steele commented
It would also be wonderful to be able to configure an ADR to add updates to an update group which is not deployed to any collections (i.e. the compliance group described in http://blogs.technet.com/b/server-cloud/archive/2012/02/20/managing-software-updates-in-configuration-manager-2012.aspx ).