Updated to Noted. We’ve been discussing the same in our planning meetings.
BobMN on behalf of SangeeV for SCCM OS Deployment
1,808 votesstarted · Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
Phase 1 of these feature is in 1602 production
This would be very useful
Would be very useful!
Updated by bobmn for sangeev/OSD
This would be good to have with the driver updates that are required for Windows 10 feature updates, looking at you 1809 Intel Display Audio!
Also, how about Microsoft has a page specifically for notifying us on any issues with updates and their resolution. So come patch Tuesday, or a few days after, you can check the website to see if any of the patches had issues. If there are issues you can pull the patch out before it does any damage rather than having to rely on your pilot deployment and google to find out if there are any issues that month.
This would be nice
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.
This and the 'SCCM updates: User Experience - Reboot notifications' suggestion should probably be combined. The whole of the user notification and reboot process needs some changes made.
Not missing anything, its not an option to migrate for some reason. It would be useful for sure