What is a one sentence summary of your feature request?
Weekly/Monthly triggers are rightfully set for a specific reoccurring schedule. Please add an option to run at the set time and ASAP after missing said scheduled time.
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
A specific, hard set, schedule serves its purpose. I do not want to change that. However, I would like to add an option to also run ASAP if an endpoint misses said scheduled time. We try to impact users as little as possible during the day, and we have many scripted checks and resets already scheduled overnight or early morning. This catches most users unless their endpoint is offline. ConfigMgr already takes this into account and runs said scripts next time the endpoint is online.
How do you currently solve the challenges you have by not having this feature?
We have not migrated the majority of our scripts and settings because of this. The few that we have tested still remain in both solutions (EPM and ConfigMgr). We have also tested using other triggers like at logon, but there’s already a lot happening during logon. Also, some of the specific vendor settings and checks work better once the user session is past all of the login steps.
100% agreed on this. As designed, since it doesn’t specifically call it out (and we had to open a case to verify), the inability to ‘catch up’ or ‘do it at a different time’ prevents us from moving a bunch over .ConfigMgr, FWIW, had a more generic ‘every 7 days’, and through the power of ConfigMgr would ‘do it’ at some random, proprietary interval if it missed it.