1,280 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.
>While we aren’t doing the NEVER reboot
Sounds like you've made a conscious decision. That's too bad.
To me, it's about flexibility and choice for the individual admin. It's relatively little work for you to remove the timer and let the individual user snooze as many times as they want.
So I guess we'll continue to do our dirty methods of either creating a maintenance window in the past/year 2033 or make a second collection for our "never reboot" machines and have two deployments for everything, where one of them suppresses reboots.
At least third party tools still exist that can give us our "nag prompt". IT is not god, policy says no reboots if boss says so and management won't change it - it's a loss of productivity and money.
Please just give us more choice. TP1906 gave us 20160 minutes (2 weeks), why such an arbitrary number? Just let us type anything in the box and give us a warning if it's over 20160, like your "high risk deployment" warning for task sequence deployments!
Why can the user not schedule a reboot straight in the Restart dialog? Either "Outside my business hours" or a time picker dialog is fine. But only "Restart now" or "Snooze and remind me again in"? Why, seriously? You can say "Outside my business hours" when you have a Required deployment but you haven't hit the deadline yet. See https://docs.microsoft.com/en-us/sccm/apps/plan-design/plan-for-software-center#bkmk_impact.
If you won't do the "never reboot" thing, at least allow users to schedule the reboot themselves. Have a little empathy for those of us who are not allowed to automatically reboot machines.
Bumping this one. SNOW, BDNA, Flexera, they're all making dirty money off of data you already have.
Yes, it's slightly easier with Windows Analytics. No, it's not a solution because it's not integrated with System Center Online and its intelligence.
2,016 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.
Updating status to Noted. See https://blogs.technet.microsoft.com/configmgreng/2016/03/11/configmrguv/
This can be done today w/ #SCCM 1802 (and previous versions too). I will mark started… and watch comments for why this doesn’t just work… before I mark this straight up completed…
1) On the CAS (or standalone primary), go to Administration → Hierarchy Configuration → Discovery methods
2) right click on Active Directory System Discovery and bring up the Properties form. Active Directory Attributes tab, and then click on Custom. In the form that appears, type the name of the attribute. Click OK, and make sure you have added it as an attribute to discover. Run discovery after exiting properties form.
3) Now when you go to the Devices view and right click on a device and go to its Properties form, you will see the new attribute showing up there.
@djam This is just my personal opinion, but if you're going to synchronise a single AD attribute into the database, you might as well give us the entire attribute list to choose from.
I'd personally just like to see AD data in the console, the other thing seems to be too out-of-scope for this one uservoice idea.