More PDQ Deploy Woes. Target lists not loading. Schedules not running.
I have a package in PDQ deploy that is setup with a "heartbeat" scheduled (start date/time was days ago), with a Target list "Link to" a PDQ Inventory Collection. The collection is a list of computers that are actually considered "online" (Online is True) as I thought this would even more ensure they get detected for needing the package (heartbeat AND Online). The list of computers in the collection sit there for days and PDQ never deploys to them. No deployments ever show up for this package and i have no idea why. I have to resort to "starting" the schedule. Then it sits there gathering targets indefinitely like so:
Clicking cancel here does nothing I have to restart the application.
Then I have to resort to restarting and deploying manually. Then I can't even bring up a list of computers it just sits there loading indefinitely trying to pull from Inventory:
Am I misunderstanding heartbeat? What's the way to make sure they get the package deployed as soon as they're online.
Tech info: PDQ Deploy 17 (Release 1 Build 98) Enterprise Mode PDQ Inventory 16 (Release 6) Enterprise Mode
-
Close. The Heartbeat Trigger fires for a given computer when its Online state goes from No to Yes. If a computer reboots before Inventory sees that it was offline (Heartbeat Interval checks it at 1:00, it goes offline at 1:01, comes back at 1:03, Heartbeat Interval checks at 1:05), the Heartbeat Trigger won't fire. Heartbeat Triggers are most useful for computers that are frequently offline, like laptops that are usually outside of the office.
Please sign in to leave a comment.
Comments
7 comments