ADR Available Deployments
I would like to see ADR's support the creation of Available deployments in addition to Required deployments. We have some business cases where a certain subset of servers are aren't allowed to "push" software updates to until the server/app owners have verified the patches.
The issue is that these servers don't have connectivity to the internet so we have to deliver them via ConfigMgr. By creating an Available update using an ADR, it streamlines our ability to "deliver" the updates to all systems, and allow the Patching Team, or App/Server owner to patch according to their own business schedules.
on our short term radar.
You have in general tab on ADR "enable deployment after this rule is run" option. If you uncheck this, new created updates will wait for enabling them to deployment. Even if you create deployment that is "available" not "required" - it wait max 12 months and reach deadline time and install.
+1 . I created ADR with my schedule. Every time after ADR starts, Deployment is created with new Deploymet Settings. In the Deployment Settings type is set as Required. I'm tired every time to track this, go and change the Required on the Available . It is very bad. I need to be set Available but not Required. I set it to Available, but after the ADR has been triggered, the Required parameter is set again. Is this normal behavior? Please add Available type possible in to ADR.
Andrew Stalker commented
+1 here. Currently working with a customer to migrate patching from WSUS to SCCM. They are not currently in a position to automate scheduled installations so want to use an ADR but only make Software Updates available so individual server admins can control their own update times
Steve Mastroianni commented
I would like to create my ADR deployments for servers as available instead of required. This allows more control over server patching. Currently I create the package as required and then I have to alter it for servers that I do not want unattended installations.
I also miss this function! Then i would not need my workaround:
- ADR with required deployment to dummy collection
- add an available deployment to the software update group (created by adr)
hm, i figured out that i could have 3 deployments for 1 ADR.. but nr2 is still something i would love to see
We are using ADR for a pilot group and then for two different automatic groups, but we cant use it for our manual group.
What i would love to see:
1: Be able to configure multiple deploys within the same ADR. today we are using three ADR just because it deploys to different collections with different maintenance windows.
2: Be able to use the ADR for our manual group, deploy the patches to our collection for manual servers as Available! When we need to go in to CM just to deploy patches already deployed just to get them as available makes us use regualar windows update for our manual servers.