Allow Automatic Deployment Rules to create a new package each time it runs
Allow an ADR to create a new deployment package each time it runs to prevent packages from becoming too large.
Levi Stevens commented
Agreed. I ended up writing my own patch automation for this reason, and because you cannot specify a template for the names of objects.
David Baur commented
I am kind of surprised that an ADR would not remove unnecessary patches once not needed every time it runs. It make sense that it would remove packages on each re-run if not required. Is this a fact? If so, we will be forced to stop using it, makes it a Bear that just keeps getting fatter. Not Sustainable.
Russ Rimmerman commented
This would help
Tyler Ng commented
I agree with this. it should be similar to the way windows 10 servicing creates the SUG.
Benno Rummens commented
Since we have cumulative update the update packages are growing exponentially. If a Software Update package gets to big the client is having issues downloading the update from the package. I would like to create a Software Update Package each time an Automatic Deployment Rule runs just the same as we create a new Software Update Group.
Yes, with the larger than ever cumulative MS updates, admins will shift more and more towards monthly SUS packages. Would be great if ADR would incorporate an automatic package creation (with month prefix or some way to manage the names)
Steve Nowowiejski commented
I would like to see this too.
This could come in handy for packages that have expired updates. If the package deployment is 100%, you can just deleted the package altogether, instead of just removing the expired updates.