1 voteCAS Computing shared this idea ·
1,335 votesplanned · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, Microsoft Endpoint Configuration Manager) responded
Updating this one to planned. We have work in this area that should address the general set of comments that are in this suggestion. While we aren’t doing the NEVER reboot, we definitely hear you that you need more than a 24 hour window. We should have more details to share in the next TP so stay tuned for updates soon.CAS Computing commented
I don't know if NEVER force is necessary, but it does need to be much more flexible. The 24 hour limit prompted me to write a fairly complicated scripted method (https://github.com/teknowledgist/TeknowTools/tree/master/AutoReboot) using scheduled tasks that won't reboot on a user without their acknowledgement and lots of warning.
1,790 votesstarted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
Phase 1 of these feature is in 1602 production