Include the Right Click tools kit as part of the Console, not as a seperate download addon
Include the Right Click tools adon as part of the Console install, not as a seperate download addon
Phase 1 of these feature is in 1602 production
As Tony Peters calls out, the 'Show Collections - Advanced' is basically a killer feature. No ConfigMgr admin should be without it.
Beyond that, I would love to see some content routines. For example: redistribute content to failed DPs for either a specific piece of content or globally.
Any update on this?
Tony Peters commented
'Show Collections - Advanced', both Collections and Maintenance Windows. I don't know how any Enterprise SCCM administrator lives without it.
Steve Carneol commented
Since we are starting to see some Right Click Tools integrated into the console (Client Notifications), it would be nice to have a Wake-On-Lan option for both a collection and the computer object. SCCM already has WOL capabilities for Deployments but it would be nice to have it integrated as a Right Click Tool. We created our own internal WOL service that we integrated into our SCCM consoles but think others could benefit from this if it was built-in.
Appreciate seeing the client notifications making it in as of 1602. As Ricky points out, the collection membership and the associated data (specifically maintenance windows) would be a great next step. The bulk add to collection being a close second.
Ricky kollberg commented
What am missing is Show Collections meberships and Maintenance Windows for my servers
I can't see Right click tools built in so far in SCCM console in 1602 / 1606 as well.
Why not my account security is bad?
John Grotz commented
Ryan's Right Click Tools are very useful in managing a collection of computers and individual systems. It would be nice to have more frequently used right click options available without needing to run another installer. It is a pain when the console has an update and once that is applied, the Right Click Tools addon need to be re-installed.
Qasim Mashwani commented
Integration of the Right Click Tools should be an optional feature in the Admin Console and preferably restricted by policy even if feature is selected as the potential for mass havoc caused by one errant click on certain tools is quite significant.
Michael Chelone commented
What is the Security role to turn these features on and off for my help desk techs?
Phase 3: Profit
Is there any update to Phase 2? I am dying to be able to restart on the fly or schedule restarts on collections.
David Stein commented
"Started"! Heck yeah! Thank you!
Seems like 'right click tools' should have been a part of SCCM years ago. Microsoft is asleep at the wheel. I'd also like to see a separate tool like "SCCM Client Center" so you don't have to wait until you track down the device inside SCCM console till you're able troubleshoot it.
What is Phase 1 ?
Garrett Marsh commented
• Branch Distribution Point Maintenance Task
• Discovery Data Collection Cycle
• Hardware Inventory Cycle
• Machine Policy Retrieval and Evaluation Cycle
• Software Inventory Cycle
• Software Metering Usage Report Cycle
• Software Updates Deployment Evaluation Cycle
• Software Updates Scan Cycle
• Windows Installer Source List Update Cycle
• Restart SMS Agent Host Service
• Generate new SCCM GUID
• Rerun Advertisement
• Open Client Log File Folder
• Open Client Installation Log File Folder
• Assign Client to Another Site
• Change Cache Size
• Uninstall SCCM Client
• Manage Computer
• Ping System
• Wake On LAN
• RDP to Console
• System Info
• Show Collections
• Running Processes
• Computer Management
• Connect to C$
• Interactive Command Prompt
• Reboot System
• Schedule Reboot
• AD Groups PC is a member of
• Interactive PowerShell
• Group Policy Update
• Open Regedit
José Vasconcelos commented
Great idea!! :)
Ryan Ephgrave commented
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.
Richard Archer commented
Regarding the talk of using PS remoting, I think I'd rather see this kind of functionality, if built into the console, use the existing communication channels (Fast Channel notification and standard policy items). I do see the value of PowerShell based commands (we use Ryan's tools), but it introduces yet another dependency. If you've got working communication between client and server, that should be enough.
It's actually a feature I really miss from LANDesk. There could be a firewall blocking all communication between server and client except the LANDesk channel, and even if I had no administrative rights on the client, I could still kick off a hardware inventory or a variety of other commands, and get real-time feedback on the results.