Make 'run on offline agents' timeframe customizable for individual profiles
It would be great if the 'Run on offline agents' timeframe setting for IT Automation and Patch Management could be defined for each profile. Currently it can only be defined for all profiles.
For example, it would be great for patching or software updates to be run on offline agents for a week or more. That way they would still get the patches/updates if they were offline at the scheduled push time. However, if I have a separate profile pushing a reboot, I would never want that profile to be pushed to an offline agent when it comes back online. Hope that makes sense.
Ben Merrill
shared this idea
Nice! The feature you requested is being reviewed by our product team. We’ll keep an eye on the number of votes, and let you know if a decision is reached to implement. Thank you for being a partner in our process!
-
Nicholas Hall
commented
We believe it that it would be more flexible and efficient if you could have each automation profile have its on "Run on Offline Agents" range. As of now, it is one option for all of them. There are certain profiles/scripts that you would want to run on offline for longer periods of time than others. And also there might be some profiles that you do not want to run on offline agents at all. Making it so you can individually control that range with each profile would greatly improve efficiently and effectiveness.
-
Neil Owen
commented
We experience this as an issue as we have timed shutdowns for school classrooms. If the PC is off prior to the time, it will shutdown again once switched on - so we have to make the offline agent the absolute minimum time.
We have now seen that our Windows 10/11 build updates are installing immediately, logging staff out, but this could be helped by delaying the offline agent slightly so it install if the computers were off and making the update automation profile be oput of hours rahter than in hours
-
Karl Dobbs
commented
Definitely need this when applied to a shutdown profile. Why would you want to shutdown a device that is already shutdown during the timeframe you set it to run?
As it stands everyone's computer that is offline during a 2am shutdown command (when set 1 day or more) get's their devices shutdown after they come back online. Not straight away either. Could be during a morning meeting.
Needs to be profile specific so you can apply different offline retention settings to different profiles.
-
Assistenza Marnet
commented
It would be great to have the chance to set 'Run on offline agents' settings for specifics IT automation profiles with different frequencies. Actually it's only possible to set the same frequency for all profiles with no exceptions.
-
Jay Ehmke
commented
I third this. Please move the run offline agents time limit to individual automation profiles instead of globally set.
-
Thanet Computer Solutions Ltd
commented
Second this. I have a reboot overnight schedule and any devices that get missed because they are offline end up rebooting on system startup. I would love the ability to set custom timeframes per profile and not overall.