This would be cool with the cloud management gateway and remote machines. We could still manage software without having to manage content. A new application type of OneGet package where we select the provider and package would be ideal.
Phase 1 of these feature is in 1602 productionRyan Ephgrave supported this idea ·
Some additional ideas for incorporating common console extensions into the console. All the things I'm suggesting are in multiple tool sets so they are very popular:
1) Cache tools: The cache is very hard to manage on a case by case basis. Adding the ability to change the cache size, clear the cache, change cache location, and see individual information on everything in the cache (the info stored in CacheInfoEx in root\ccm\SoftMgmtAgent)
2) Client control panel information: It would be amazing to make the client control panel tool (what lets you view client information, components, run configurations, etc) available through the console.
3) Show what boundaries a SCCM client happens to fall in to be able to troubleshoot overlapping boundaries.
4) What's been run on the device? Finding out historical information about what has been run on the device should be much easier than going to the registry for execution history and the logs for application information.
5) Install or uninstall applications and other things that show up in Software Center
6) We should be able to see all Collection Variables, Maintenance Windows, and Power Plans that are deployed to a specific device. Also, some information on what the next maintenance window will be would be amazing.
1) Show who is currently logged onto a computer. When people are troubleshooting application install problems, they usually want to find a computer that has the problem and has no one logged into it.
2) Mark if a device has a pending reboot or not
3) Wake On Lan on demand! Send a WOL packet through the SCCM server to the device!
4) Manage running processes
5) Manage services
6) Restart computer
There's a ton of other tools out there, but these are probably the most useful and most popular.
I'm the author of the right click tools and I can say some of them make sense to put in the console and some don't.
The ones that I think make the most sense are:
Client Actions (At least make all actions in the control panel on the client available to trigger from the console, but some others are useful, like send unsent state messages)
New Site Code - For some reason a lot of people requested this even after you allowed switching between sites in the console. They like to manually put in the 3 character code.
Add a list of computers to a collection. Either import through CSV or just copy and paste the list in
Clear cache - Like the option on the client
Run client check - Just execute the client check exe to run a new one on demand and send it to the server
Uninstall client - I know you can reinstall, but sometimes the client gets on a computer or group of computers that shouldn't have it.
There are a lot of others that simply deal with troubleshooting computers outside of problems in Configuration Manager (user profile, installs, stuff like that) so I don't think it makes sense to put those in.
I just saw the WMI class SMS_CI_ComplianceHistory which seems to have some of the information, but it'd be nice if we could see this from the console and if the name of the CI was recorded so we know what App/Baseline is run (if the App is removed, it doesn't look like there is a way to match the scope ID to the app)
A quick workaround now is to create a folder and move the updates you don't want to deploy to that folder. Then, they will only show up if you search all sub folders.