Packages Not Updating

This article covers three PDQ Deploy package update problems: the Package Library not showing newly published packages, Auto Download Packages not updating to the latest version, and individual Auto Download Packages that can't be approved.

Package Library Not Updating

If the Package Library in PDQ Deploy doesn't show a package version that has been published, refresh the console to force a check-in with the PDQ Library. If refreshing doesn't help, restart the PDQ services, reboot the PDQ server, verify the required external exceptions, and re-apply your license key using the steps below.

The PDQ Deploy console checks in with the PDQ Library for updates to the Package Library every two hours. The PDQ Packaging team publishes most packages within one business day of being released; high priority packages are released on the same business day or, if the vendor released the application update after hours, ASAP the next business day.

To manually refresh the PDQ Deploy console and force a check-in with the PDQ Library, press F5 with the PDQ Deploy console as the active window, or select View > Refresh in the menu. Any Package Library updates published since the last check-in appear on the Package Library page after the refresh.

If the Package Library is still missing published packages after a refresh, work through these steps in order. Refresh the console after each step, and stop when the Package Library updates.

1. Close all open PDQ consoles and restart all running PDQ services.
2. Reboot the PDQ server.
3. Verify that the PDQ server can reach all of the required external exceptions listed in Firewall Ports and External Exceptions.
4. Re-apply your PDQ Deploy license key, then restart all running PDQ services. Package Library access requires an active Enterprise license, so the Package Library can fail to update if PDQ Deploy can't validate your license when it checks in with the PDQ Library.
   • Get your latest license key from the PDQ Portal. Don't use a previously downloaded or emailed license key, because it may be outdated and fail validation. For steps, see Access Your License Keys.
   • In PDQ Deploy, go to Help > License > Enter License Key, and paste the key.

Auto Download Packages Not Updating

If the Package Library shows a newer version of an Auto Download Package but your downloaded copy hasn't updated, first check your Auto Download approval settings and Repository storage space. If those are fine, restart the PDQ services, reboot the PDQ server, verify the required external exceptions, and re-apply your license key. Work through these steps in order, and stop when your Auto Download Packages update.

1. Verify that the packages should be downloaded according to your Auto Download Approval settings, in Options > Preferences > Auto Download > Auto Download Approval Settings.
2. Make sure your Repository location isn't out of available storage space.
3. Close all open PDQ consoles and restart all running PDQ services.
4. Reboot the PDQ server.
5. Verify that the PDQ server can reach all of the required external exceptions listed in Firewall Ports and External Exceptions.
6. Re-apply your PDQ Deploy license key, then restart all running PDQ services. Auto Download Packages require an active Enterprise license, so updated packages can fail to download if PDQ Deploy can't validate your license when it downloads from the PDQ Library.
   • Get your latest license key from the PDQ Portal. Don't use a previously downloaded or emailed license key, because it may be outdated and fail validation. For steps, see Access Your License Keys.
   • In PDQ Deploy, go to Help > License > Enter License Key, and paste the key.

Auto Download Packages Not Approving

If specific Auto Download Packages won't download or approve while other packages update normally, those packages were likely deprecated and removed from the Package Library. Search for the package on the Package Library page. If it isn't listed, convert it to a Standard Package or delete it to clear it from Auto Download Approvals.

If there are individual Auto Download Packages that are not automatically downloading per your Auto Download Approval settings, or when you select Approve Now in the Auto Download Approvals menu, but other packages are successfully updating when expected, those packages may have been deprecated from the Package Library and are no longer available for download. You can verify their availability by searching for the package name in the search field on the Package Library page.

If the package is not available in the Package Library, convert it to a Standard Package (Package Properties > Options tab > Convert to Standard Package) or delete it to remove the package from the Auto Download Approvals menu.

Package Available but Stuck in Auto Download Approvals

In rare cases, a package can be available in the Package Library but stuck in Auto Download Approvals. This happens when the version waiting for approval was deprecated before the PDQ Deploy console checked in with the PDQ Library. If this happens, the only solution is to delete and re-download the Auto Download Package.