Excluding collections from deployments



  • Luke Nichols


    Most of your issues can be resolved by simply creating one dynamic collection that meets all of your deployment criteria. You can create a dynamic collection based on membership in other collections as well, e.g. make a collection that contains computers that are in those two other collections, then use the new collection to exclude both in your package.

    Also what do you mean by groups? As far as I know PDQ does not use that terminology anywhere. Do you mean collections or perhaps filters?

    Comment actions Permalink
  • Alex Saad

    Sorry about the terminology, I replaced group with collection which is what I originally meant.

    As for creating a dynamic collection that excludes certain other collections, I think I just figured it out. I just create the following value filter, and set the group filter to 'not any'.

    Member of Collection >> Name >> Equals >> Admins

    I think I'm all set here.


    Comment actions Permalink
  • Colby Bouma

    I personally recommend using:

    Computer | Collection | Is Member | Admins

    It ties it to the CollectionId in the background. This method is faster and allows for collections to be renamed.

    Comment actions Permalink

Please sign in to leave a comment.