PDQ Deploy automated software deployments: Part 2

Josh Mackelprang headshot
Josh Mackelprang|Updated January 26, 2021
Generic blog header
Generic blog header

In Part 1 of this blog series, “PDQ Automated Software Deployments,” you created and set up schedules, and now you’re patching your machines. But, what if you didn’t want to patch all of your machines at the same time? Maybe you want to set up a pilot group to test patches before rolling them out to production? In Part 2 we’ll cover how to create some inventory collections and duplicate your auto-download packages to do just that.

Getting started

First things first, we need to setup our collections so we can effectively target our test group. For my test group I’m going to use five machines:



  3. WS-JAKE01-DEV


  5. WS-JOSH01-DEV

The first thing I’m going to do is create a static collection of these machines called “Testers,” (this could also be a dynamic collection, but getting our test machines into a single collection is the goal):

creating a static collection

Duplicating a collection

Duplicating a collection using automated software deployments

Modifying the default auto-approval for our automated software deployments

Next, we’ll modify the default auto-approval window on our “testers” package, so it immediately updates after there is a new version in the library while leaving the production package set to our default approval window:

Modifying the Default Auto Approval

At this point we have two packages for Mozilla Firefox ESR, one that will immediately update itself for our testers, the next will update based on your preferences. All that is left to do now is set up a schedule for your production package (see Part 1) and set up the second schedule for your testers. To set up a schedule for our testers, we’ll get a bit aggressive with our triggers to make sure that it gets quickly deployed. Then, we can start to get feedback from our pilot group. If something should go horribly wrong you have some time to disable the schedule targeted at your production.

Setting up a schedule
Mozilla Firefox ERS (Test Group)
Mozilla Firefox ERS (Test Group) - Scan After Deployment
Mozilla Firefox ERS (Test Group) - Testers

In conclusion

That’s it! You’re done. You now have two packages, two schedules, and two collections to target. Computers in your test group will get updates for ESR immediately, and you have some time to make sure that everything goes off without a hitch. Wash, rinse and repeat this process for as many other packages as you wish. You can now rest easy pushing out packages using PDQ’s automated software deployments. Check out this video too, if you missed it in my first post. 

Josh Mackelprang headshot
Josh Mackelprang

Ever since becoming the Solutions Manager at PDQ, Josh has other people do work for him, including writing this bio. We're pretty sure he eats food, has ~10+ years of IT experience, and would be quite content to never see another Intel IMS ever again. Josh is proud he maintains his CompTIA A+ certification.

Related Articles