Anonymous
My feedback
-
54 votes
Option 82 support addressed in our 1903 Technical Preview
Doc: https://docs.microsoft.com/sccm/core/get-started/2019/technical-preview-1903
Blog: https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/Estimating-Cloud-Services-Usage-with-ConfigMgr-Technical-Preview/ba-p/394267Anonymous
supported this idea
·
-
1,958 votesstarted ·
AdminMark Silvey - ConfigMgr Product Team
(Engineering Manager, ConfigMgr, System Center Configuration Manager)
responded
I’m re activating this one based on the fact that we don’t show the intrusive reboot countdown after the software was installed. We still have some work to do here to make this experience meet the requested behavior.
Anonymous
supported this idea
·
Anonymous
commented
Please increase the Maximum reboot countdown to be more like two weeks rather than 24 hours.
We have researchers that run long simulations, and a 24hr countdown risks them losing long simulations. -
1,268 votesplanned ·AdminMark Silvey - ConfigMgr Product Team
(Engineering Manager, ConfigMgr, System Center 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.
Anonymous
commented
I would like to see the maximum reboot countdown increased to at least 2 weeks.
We have many academics running long simulations, and a 24hr maximum reboot schedule means we have to suppress reboots always to prevent substantial loss of work.Anonymous
supported this idea
·
Please increase the maximum reboot countdown. We requrire a countdown in the order of two weeks to allow academics running long simulations time to complete them.