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.
Give user ability to plan restart within a maximum of 24 hours since the first popup and if he didn't set any date then restart ill be done.
I prefer a column for boundary group name or boundary description
or just have a column with the boundary description
I suggest application instead of package and to have its content updated after each upgrade or hotfix installation, also has the console update created and downloadable like any other update or app to be installed through software center
1 voteNoted · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, System Center Configuration Manager) responded
Thanks for the feedback Henri, what do you have in mind? Elaborate please :)
I suggest to create a built-in application when installing SCCM CB in the primary site then update it each time a new console is available upon an upgrade or a hotfix.
11 votesNoted · AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, System Center Configuration Manager) responded
Scott – How would you like it streamlined? What would you do if you could have anything?
I suggest to create an update/package/app to be downloaded to the client via DP and not via UNC like is the case now, Or even, the local SCCM client will detect the existence of the console and checks every 24H if there is any update then download it to the software center and asks user to install it from the console.
I suggest to create an update/package/app to be downloaded to the client via DP and not via UNC like is the case now,
I would suggest the following, since the creation of the deployment, set the option to download one or multiple updates directly from MS sites instead of downloading them first to a package and distribute it. I don' need to download less required updates like SQL ones but it is critical to install them.
I exactly noted this is missed in 1810, it is already done for devices node but not for devices list upon double click of a deployment status