
webaccounts
Comments
-
I found better success putting the file under the repository and then installing with something like - $(Repository)\Files\Help Desk\Apps\CureMD\ieShell.exe $(Repository) is a default variable on d...
-
This post will explain but heartbeat doesn't work on externals. https://community.pdq.com/posts/11112-external-clients-on-a-schedule-never-run What I did was set a schedule for heartbeat and every ...
-
Thank you, that's good work. The unfortunate thing right now is we have to use the PDQ provided packages or our remote people can't get the update. Hopefully PDQ can put yours up on their package l...
-
Last time this happened it was because of an IP mix up. Only seen it once and that was 2 versions ago. I have 100+ computers on PDQ.
-
It might be when it got scanned again. Sometimes mine will take an hour or so before running a full app scan.
-
The interval one seems to be working great. Hopefully the heartbeat gets fixed soon, I would think that one would get these updates pushed out faster. Thanks. Shawn
-
Ok. If I set the schedule to once it works for the external clients. My external clients work random times. Your heartbeat explanation makes sense but I have external clients that are offline right...
-
These are packages from the library. Any or all of them don't deploy to external agents via schedule. "Deploy once" will work, but if I put a heartbeat schedule the external's will not. Thanks, S...
-
Currently using 16.5.0.76 Enterprise Mode for Inventory and 17.1.0.0 Enterprise Mode for Deploy. 5 . That's good then. Thanks for the reply.
-
Thanks for the quick response.