Webcast: Auto Download Best Practices

4/26/2018 3353 Contributors

How Auto Download is different than the old Auto Deployments: 0:51

Approval settings and scheduling best practices: 3:50

Question: Now that I have upgraded to PDQ Deploy 15, is it a good idea to create new “Auto Download” Packages to replace the old “Upgraded Auto Deployments”? 10:09

Question: What is the best way to handle apps with full packages & patch packages (such as Adobe Reader) now that we have Auto Download? Do I nest the full package in my baseline package (always up to date!) and use schedules to update test/update via the patch packages? 11:32

Question: I linked an Inventory collection with old s/w version to a PDQ deployment to automatically update software as it becomes available. I also use an approval delay of a week for apps. So if a new version becomes available clients will become a member of the “old version” collection and Deploy will try to upgrade them. But in fact, there’s nothing to upgrade because the new version is not approved yet so it will end up doing a reinstall of the version they already had over and over. How to handle this? 15:32

Question: For an automatic deployment schedule, if we select the “Stop Deploying to targets once they succeed” flag, will a client still get newly released and approved packages since the package has changed even though the schedule remains the same? 19:40

Question: Is there a way to get an email alert if/when an application has a new version? 23:07

Question: We currently implement messages in both Pre and Post-Steps to notify our end users before an Auto Deployment is pushed. Do you have some general recommendations for Pre and Post-Steps? 27:05

Set conditions at the package level: 29:26