SCCM Console, save your prefered defaults.
Can be frustrating, SCCM console, keeps resetting to default, every time you exit. The odd occasion it will retain settings. IE: folder options, and settings. Would be nice if we could save these to a personal default, so it retains settings.
Chad Simmons commented
+1. Being able to define multiple views and switch between them like on a SharePoint list/doc library would be fantastic.
I agree with everybody's comments, especially when RDP'ing. Very very frustrating now we are mostly 'working from home'.
Please save custom columns setup for all views when updating System Center Configuration Manager (SCCM).
Currently, it's back to default columns setup in all views after each update and it's annoying to setup this again after every update.
+1 on all of this. Particularly weird via RDP...
L U commented
Using SCCM console across different domains/machines, profile not roaming anywhere.
So, also need easy export of settings so I can import them across all instances, and re-import after upgrades.
Bo Kjær commented
Seriously, I'm also very frustrated that I have to adjust columns every time the client gets closed.
1) Just get general columns adjustments working.
2) Get per collection columns adjustments working.
This is very frustating. If the console runs behind a RDP session and it disconnects, settings gets back to default. Please fix this.
Derick Handeg commented
Seriously, this is such a pain.
There should be a way to set a default, or change the default columns in each respective node of SCCM console. Software Updates, Devices, Device Collections, etc.
Having upgraded easily the last 6-8 versions of SCCM CB, I find it VERY annoying that each time my customized layout with columns is getting reset with every console upgrade. It would be great if all user settings on the console would be retained during an upgrade to avoid having to go thru the same customization steps.
Dennis Wieck commented
Oh yes, that would be great. Currently the most time consuming part when creating an application is replacing the system defaults with our defaults. It would be good if you could use references to fields like "product name" or "version".
- The standard installation command for MSIs gets standardised logging settings (/l*v \Logs\<Product>_<Version>.log)
- The maximum runtime gets set to 15 minutes (because in 99% of our cases the installation has failed if it's been going for 15 minutes, so there's no sense in making the user wait for another 1:45 h to get an error message)
- MSIs have no uninstall content
- Software get installed per System
Automatically save columns and width layouts in the console.
Whenever a new software update group is created via an automatic deployment rule, my preferred columns are not there. It is a pain to have to re-add them and put them in the correct order.
Bill Gates commented
I agree with this. There should be a way to save the default dashboard view on picked colums. It is a pain to re-add them every time you re-login to the console. I like by default to be able to see things like operating system and operating system build etc. after I login.
Peter S commented
For me I don't even need to close the console - it resets itself just by disconnecting RDP session where the console runs.
Marek Belan commented
It was be nice when I close console and open it in the same state.
Saving selected columns and great apply columns to all nodes(WSUS console has it).
Now I open console and always must selecting collumns and opening deployment etc etc ...
Many customers want this feature. Please can we have this soon?
Michael W commented
I agree. None of my column selections stay after exiting the console either, so even having that stay would be great. I have to re-add OS and Activity in collections, and Date Released or Superseded in Software Updates and such. Gets frustrating.
Dustin Adam commented
Collections, especially Computer Collections, aggregate differing types of devices, its a common complaint on my team that selecting columns when viewing a specific group doesn't persist to a specific Collection. For example, we have a Collection for onboarding to Windows Defender ATP, and when selecting a Column for Onboarding State, the column then shows up when viewing a Computer Collection that contains iOS Devices, and a different set of columns then has to be selected to view, for example, IMEI. It would be great if Column selection would "stick" with the collection it was selected for, in the form perhaps of a local user preference, so that when viewing a collection you have quick and easy access to relevant columns for that collection
Russell Johnson commented
A persistent filter feature would be helpful. I really miss "Search Folders" from SCCM 2007. For example let us filter out expired and/or superseded updates in "All Software Updates" as a default view.