1,270 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.
I work in a health care environment where we have a lot of shared computers. Think about computers in a patient room or in an exam room. I can't have a decision made by a user 15 minutes ago, who is long gone, affect the next user. So User A says reboot in 15 minutes and then User B gets booted because she happens to be using the computer at the time User A said it was OK to reboot. Once the computer has been scheduled to reboot - it needs to be obvious to anyone using the computer that it is in a reboot pending state, and the user needs to be able to exit or further postpone the reboot pending state potentially indefinitely.
Thanks for the feedback, updating status to Noted – see https://blogs.technet.microsoft.com/configmgreng/2016/03/11/configmrguv/
This is very similar to https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/10625580-dcr-boot-images-provide-an-option-to-prevent-re
so I may merge with that item as both would be solved with the same mechanisms
I would really like this to happen. There is no idea - in the interface - of a particular version. We are specifying only package/program. It would be nice if the package execution engine could gather the version number just prior to executing the package rather than at the start of the TS.
In our organization I have to take all task sequences off line for a couple of hours if I would like to update any package used a task sequence. Either that or let them error out and expect staff will just try again. I am not sure why, when there is no way to specify a particular version of a package, that the version would matter to the TS. Just use the "current" version of the package rather than the version that was current at the moment the TS was initiated.
I would be happy to accept collection based client push, which would allow us to be even more surgical in targeting. That would make an implemented solution cover more circumstances and would only require original suggested to maintain an OU to collection mapping which is pretty easy. I sure wish this would get added . Configmgr "knows" how to deploy clients - so it is a shame we have to do it through GPOs and other means to maintain the control lacking in the Configmgr function.
Updating status to started.
The first iteration/slice of this is available in the 1905 Tech Preview.
6 votesTodd Miller shared this idea ·
Status Messages were much more accessible in ConfigMgr 2007. They really are hidden and hard to use in 2012 and CB.
269 votesstarted · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, System Center Configuration Manager) responded
This is available as the application groups feature in the 1905 technical preview. We’d love it if you installed it and gave us your feedback.