Any way to add and remove from collection as part of deployment?

Comments

3 comments

  • Luke Nichols

    Craig,

    It seems to me that the more elegant solution is to simply have a series of dynamic collections that filter the computers based on the results of your deployment. For example if you have a two-stage deployment where you need to do task A, wait a while, then do task B to only the computers that successfully completed task A, then just have a dynamic collection for each set of computers. Collection A contains all computers that need task A and task B and Collection B contains all computers that need just task B. This could be a sub-collection of Collection A.

    This would be easy if you are simply installing applications because you could set up filters on the collections to see if they have been installed yet, but it would be more complicated if the steps in your deployment are performing more slight changes.

    What kind of tasks are you performing in the deployment?

    1
    Comment actions Permalink
  • Craig Mohr

    Its an upgrade from 1607 LTSB to 21H1 full. After it finishes I need to run some patches and push some registry keys to reenable the store. It's failing somewhere in the deployment process (the actual installation) though and so far its not actually failing but PDQ thinks it is. I don't want to set a 3-6 hour timeout wait either so I'd rather have it fail and set a 2nd process to check and push when things come back online. This is a slightly different than normal upgrade of Win10 because I am upgrading from LTSB we can't do some of the silent stuff (using the /PKEY switch which converts it from LTSB and keeps all apps and files won't allow it in any of the methods I have tried) so it takes an actual user to push go.

    1
    Comment actions Permalink
  • Luke Nichols

    I would think it would be easy to create a collection containing machines that have had the first step performed, then. You can simply look at the OS version.

    As the first part of your deployment I would perform the upgrade to 21H1, then a sleep step if necessary, then perform a standard scan.

    As the second part of your deployment I would add a collection membership condition for only machines running 21H1. Then perform your patches and registry keys. If you need to be able to tell if the second part has been run you might have to add those reg keys to your scan profile or try to find out if you can scan for the existence of those patches.

    1
    Comment actions Permalink

Please sign in to leave a comment.