PDQ.com mobilePDQ.com desktop

Automatically Deploying Java, Flash, and other Patches

Shawn AndersonShawn Anderson

PDQ Deploy introduces a commonly requested feature for Enterprise mode users; Auto Deployment. As the name implies, PDQ Deploy will now have the ability to “set it and forget it” when it comes to packages that we host in the Package Library.

Admins familiar with our Package Library will notice a few interface changes.

Import vs. Auto Deployment

From the Package Library you have two options for pulling down packages: Import and Auto Deployment.

Import replaces the “Download” button in earlier versions of PDQ Deploy. Importing a package does the same thing; it copies the package from our Package Library into your PDQ Console where you can deploy the package. All of the same features still exist.

The big change is the Auto Deployment feature. You can now select one or more packages and click the Set Auto Deployment button (or link) and you will be presented with a dialog about setting up your auto deployment.

Auto Deployment Options


By default you will be auto deploying the latest version of the selected package(s). If you select only a single package you can change the version to be auto deployed to an older version if you choose.

Approval Policy for future versions

This setting is all about the future. When a new release of the respective packages becomes available you are telling Auto Deployment how long to wait before approving the new version. You can select to automatic approval and set the duration in days and hours for the deployment. You can also set the manual option, which will require future action on your part to specify to PDQ Deploy’s Auto Deployment when to approve the new version. This option is handy if you want to double (or triple) check that a patch will not break your environment.


You then have the option to create a new schedule for your auto deployment, or you can attach the package(s) to an existing schedule, if one exists. When a new version of a scheduled Auto Deployment package is approved the older package is replaced in the schedule. This means you won’t have to create or modify a schedule when a new version is approved.

You are then able to select the target computers for your future deployments. The video below demonstrates this by Shane and Lex linking to PDQ Inventory

Don't miss the next post!

(CVE-2020-1472) 'ZeroLogon' Vulnerability

The Zerologon Vulnerability Allows Attackers To Completely Take Over Your Domain Controller Without Credentials.

© 2020 PDQ.com Corporation


  • PDQ Deploy
  • PDQ Inventory
  • PDQ Link
  • Enterprise SL
  • Pricing
  • Downloads
  • Licensing
  • Buy