Master schedule to update multiple outdated software packages?

Comments

4 comments

  • Dave Hoffman

    You can, I've been doing that for a little while.  If you hold the Control key and click on multiple packages, you can nest them all into a single package.  Then schedule that package to run on whatever schedule you'd like.

    If Preferences -> Deployments, you can enable the Retry queue for offline machines.

    0
    Comment actions Permalink
  • kelemvor

    I knew I could group things into a single schedule but can each package in the group have its own target collection?  E.g. I only want to push Firefox to the people who already have it but it's out of date.  I don't want to install it for anyone who doesn't already have it.

    0
    Comment actions Permalink
  • Dave Hoffman

    I got ya now, I was thinking of something a little different.

    Assuming that you also have PDQ Inventory, I believe it can be done with a few tweaks.  Inventory comes with pre-made groups for old versions of FF, Chrome and Flash.  So that part is easy.

    On the Deploy side, you can create new packages just for updating software, since this would only work for updating.  If we look at the Firefox package, in the Conditions tab, I specified that I want it to only run on computers that show up in the Firefox (Old) Inventory collection.  If the computer doesn't have Firefox already installed, or if it's current, then it won't do anything.

    So you could make these update packages for multiple software titles, specify in the Conditions for each one what collection that they're allowed to do anything with, then bundle them all into 1 Deploy package.  I believe that would work.

    0
    Comment actions Permalink
  • kelemvor

    Ah OK.  That would work.  I can point the Deployment at the whole database but use the condition to skip any that don't have it installed.  Hmm.

    0
    Comment actions Permalink

Please sign in to leave a comment.