Auto Download Packages Replacing Auto Deployment Packages

4/26/2018 2416 Contributors

Purpose:
Starting in PDQ Deploy 15, Auto Deployment Packages will be converted to Auto Download Packages. This document describes what you can expect when migrating to PDQ Deploy version 15.

IMPORTANT: It is possible that the conversion to Auto Download packages will result in duplicate packages once PDQ Deploy has been upgraded. This is by design and is explained here.

Wait… What?
For those using Auto Deployment Packages, the change to Auto Download Packages will be familiar.

Auto Deployment was a feature that allowed packages to be attached to a schedule so new versions of packages could be deployed as they were made available in the Package Library. However, the way the feature worked proved to be non-intuitive, under utilized, and required too much planning out of the box. It was only noticeable from within the Package Library or in the Tree after it had already been set up.

While Auto Download is replacing Auto Deployment, it is not getting rid of the functionality. We’ve simply taken the approval process and put it at the package level. Auto Downloads offers a streamlined setup and upkeep of downloaded packages which allows for the set-it-and-forget-it ease of Auto Deployment with fewer requirements of the initial configuration. Also, you can now have packages stay up-to-date without having to use a schedule.

Resolution:
When migrating to PDQ Deploy version 15+ from a version < 15, Auto Deployment Packages will be moved from the Auto Deployment Packages folder, now deprecated, to their own folder where they will be upgraded to the newer Auto Download packages.

Here we have a mixture of Auto Deployment Packages and normal imported packages. This is in PDQ Deploy version 14.2.

01.png

And after the upgrade to PDQ Deploy 15, all Auto Deployments are moved to the Upgraded Auto Deployments folder in the tree:
02.png

For additional information on Auto Download Packages, please see the PDQ Deploy product documentation.