Creating a interval schedule vs retry queue
I've seen another topic regarding "catching offline computers," but that was using the heartbeat as the interval type which requires PDQ Inventory. When we're leveraging with our customers only PDQ Deploy, we're attempting to deploy a single package to all machines over the course of a few weeks. Our current method is that we:
- Discover a target list of machines and link that to the package to be deployed
- Create and set a schedule for the package to deploy with a "Type" of "Interval" (typically 2-4 hours). With this we have the option set to "Stop deploying to computers once they succeed"
We typically let this schedule run for 1-2 weeks until we've deployed to all machines.
Could explain how this process might be a bit different than leveraging the new "Retry Queue" with similar "Retry Queue Interval" of 2-4 hours? Is there any difference rather?
Thanks for the clarifications and any suggestions.