SCCM 1810, all ADRs now have no deployment package! - greyed out and cannot change


  • So this was an extremely unwelcome surprise yesterday, all my ADRs have now decided not to download updates to the deployment packages, and all the rules are set to "No Deployment Package" in the Package tab of the ADR.

    Nothing has been changed, no one has touched anything, so is something seriously broken here? I cannot even go in and change the ADR to its original package, its greyed out!!

    I really hope someone can help, all the searching on the internet has come up with zilch.

    • Edited by T__16 Thursday, January 10, 2019 10:42 PM
    Thursday, January 10, 2019 10:41 PM

All replies

  • Sounds like a database issue.  I would recommend calling Microsoft Support on this one. :-/
    Thursday, January 10, 2019 11:21 PM
  • I think Im screwed and will have to recreate all the ADRs.

    All the ones that are affected, which is all of them apart from one, I had gone into and removed "superceded" from the updates selection, now I remember, I did this between the december sync and this months, that is the only thing that changed.

    The only one I kept superceded in, was the only one that has not been affected, so I can only assume I have stumbled on some sort of bug in saving the ADRs in the console.

    Is there a powershell command I can use to try and manually change the deployment package like in the old SCCM 2012?, but for Current branch?

    • Edited by T__16 Thursday, January 10, 2019 11:48 PM
    Thursday, January 10, 2019 11:46 PM

    OK, as a test...I removed superseded from the last remaining ADR that was ok, and lo and behold, as SOON as it was saved, its deployment package setting was lost and went grey like the others!

    What the hell I do now, I have no idea, we have an entire organisation now downloading updates to each client via the internet, and also require superceded updates to remain in the SUG for a period of time.

    Thursday, January 10, 2019 11:53 PM
  • Hi,

    Grey out means its having one or many expired updates in it.
    When you deploy a SUG which contains expired updates via console, the wizard will automatic filter out those expired ones. However, when you use PowerShell script to deploy, it won't do, I assume this is the issue here.


    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact

    Friday, January 11, 2019 8:22 AM
  • Hi,

    Appreciate the reply.. but I checked, and there are no expired updates in the SUG, or the update package!

    There are a load of superseded, but I want to keep them to be deployed until the new ones are tested and put out on a later deployment by the ADR.

    If you see above, the one that was not affected, I took superseded "NO" out of the filter parameters, and the second I saved it, it went grey like the others.

    Changing the setting and putting superseded back into the filtering, didnt change the deployment group, still locked out!

    Friday, January 11, 2019 9:04 AM
  • I think I remember seeing a report of this (or something similar) as a bug.

    You should open a case with Microsoft.

    Recreating your ADRs should, of course, work as well. I'd recommend scripting their creation though so if this happens again, it's quite easy to recreate them.

    Jason | | @jasonsandys

    Friday, January 11, 2019 6:57 PM
  • Ahh thanks Jason.

    Im actually running the new ADRs just now, and see that they are creating a load of new SUGs, but fair enough, maybe they are referenced to the ADR, so will delete the old ones and hopefully be back in business.

    Seeing as the ADRs were created ages ago in 1702, im happy to accept its a bug when saved in 1810 console.

    I wish I knew how to export the ADRs with their XML, but have not yet found out how.

    Friday, January 11, 2019 7:18 PM
  • This isn't exactly that, but it may be a start for you: (List-CMADRs.ps1).

    Jason | | @jasonsandys

    Friday, January 11, 2019 10:51 PM

    Your bug is fixed in this patch:

    The No deployment package option is selected after you change the properties of an Automatic Deployment Rule (ADR). After this update rollup is applied, affected ADRs can be re-created and their properties changes without any further issue.

    Vladimir Zelenov |

    Tuesday, February 19, 2019 11:43 AM
  • After installing Rollup update 2, deployment package is still greyed out. Do we really need to recreate all ADRs that have been affected or can we run a command on the database?



    Tuesday, April 2, 2019 9:50 AM
  • My hunch tells me you will have to re-create, but then you won't have the problem again after the hotfix.

    Certainly I re-created all mine, was probably faster than scripting a complete export and import for something you might only need to do once.

    I think I spent 2hrs on the ADRs.

    Wednesday, April 3, 2019 4:06 PM