Automation/scheduling question

Follow

Andrew Gresbach

• February 24, 2021 20:09

I'm working on setting up automation schedules for deployments and have a couple questions:

We have a handful of applications that are auto update packages directly out of PDQ and we have individual Inventory groups setup breaking desktops into groups such as "not installed", "old version" & "up to date" which i know we can setup a schedule to run / update any desktop in the "not installed"/"old version" groups and that works fine.  

My main question is if we have multiple applications, how can we setup 1 schedule to run say every night at 8pm and each application apply to only specified Inventory groups? 

For example:

1 schedule that kicks off and:

7zip looks to only the 7zip "old version" group

Google Chrome looks to only the Chrome "old version" group

etc.

Only other thing i could think of is to make individual schedules for each application and have them all run at the same time but doesnt seem like the cleanest way so thought i'd see if i was missing a better way

0

• 

  Andrew Gresbach

  • February 24, 2021 20:21

  maybe smartest to setup a new package and included nested packages of the existing  apps that i want to update, changing the conditions away from nested conditions to only point to the "old versions" maybe? and then attach a schedule to that?

  1

  Comment actions Permalink
• 

  Colby Bouma

  • February 24, 2021 20:23

  My personal recommendation is to create 1 schedule per package. Setting up a large package with a bunch of Nested Package steps works, but you'll get a lot of failed deployments.

  0

  Comment actions Permalink
• 

  Andrew Gresbach

  • February 24, 2021 20:33

  failed deployments due to what? too many going at once or meaning if you setup conditions like only when no one is logged on, etc

  0

  Comment actions Permalink
• 

  Colby Bouma

  • February 24, 2021 20:47

  I was referring to Conditions. If a target fails a Condition, its deployment will show as failed. If you want to build a package that you can deploy to all targets and use Collection Conditions to filter them, you're going to have a lot of targets showing failure in the deployment. It's not going to break anything, but it's inefficient and generates a lot of noise.

  0

  Comment actions Permalink
• 

  Andrew Gresbach

  • February 24, 2021 20:49

  ahh yup i hear ya.....and i just realized even if i DID build 1 big package filled w/ nested packages w/ custom conditions, when you build a schedule you have to pick targets again so that wouldnt work anyways so that kind of sucks

  so if i do them all individually, wouldnt i run into the same thing though w/ flooded w/ possibly failed reports due to conditions?

   

  0

  Comment actions Permalink
• 

  Colby Bouma

  • February 24, 2021 21:01

  No, because each Schedule will have its own targets.

  Schedule 1) 7-Zip, targets the "7-Zip (Old)" collection.

  Schedule 2) Google Chrome, targets the "Google Chrome (Old)" collection.

  You can add the matching "Not installed" collection for any package that you want on every computer.

  0

  Comment actions Permalink
• 

  Andrew Gresbach

  • February 26, 2021 20:36

  cool thats what i was thinking would be needed so i'll roll with that! thanks for the help!

   

  0

  Comment actions Permalink

Please sign in to leave a comment.