Show Powershell equivalent command(s) at any wizard completion
At wizard completion for anything, show the Powershell cmdlet equivalent like in other System Center products.
Saw a working demo of this recently so updating to planned.
`Been planned for nearly three years.... UPDATES?
Chad Simmons commented
Any progress on this?
David Stein commented
Still "planned" as of January 2021?
Scott Williamson commented
Any update on this?
Well-documented REST API would be probably better than this.
Mohamed El Masri commented
Probably already has been stated, but the console is not using powershell, it is using WMI.
Have a look at smsprov.log to see the underlying WMI call for every action you perform in the Console.
Damien Van Robaeys commented
Shared on tweeter
seb cerazy commented
3 years on and counting...
Markus Koechli commented
This button could save much time
I'd love to have this button... I sometimes look for a way to reproduce what I'm doing with the console and I hardly find the solution.
Tom Wardrop commented
I suspect they'd have to redo the console from scratch to make this happen, because I doubt powershell is actually being run in the background unlike other consoles. I wouldn't want it to show me a best-guess powershell command that the console itself isn't using.
Keith Garner commented
One of the better features of MDT, demystifies automation + management.
Eswar Koneti commented
In MDT ,for each action that we do like application creation or task sequence ,driver creation ,at the end of the GUI ,we have option called view script to see what powershell cmdlets the task used and the same can be utilized to create multiple tasks by changing the basic things in the scripts instead of creating the entire script from beginning. We would like to see the similar option in SCCM when we create collections ,applications,configuration item, task sequence etc .This will help lot of SCCM admins to perform the basic tasks using the powershell cmdlets.
Christian Sedlmair commented
I also would love to have the complete history of equivalent PowerShell commands. Exporting results from the console is not as satisfying as having pure text in objects that can be sorted, filtered and the properties needed could be selected. As well as working around errors I encounter when using the WMI PowerShell cmdlets but is successfully handled by the console. This is especially valuable as the documentation of all WMI classes seems never to be up-to-date or at least I do not find it. Additionally I find the performance of the console could be better some times. So having the PowerShell commands that retrieve only what is needed at the moment speeds up the work with SCCM tremendously
Roth, Chase commented
Been almost 2 years since this was "NOTED". Lets make this happen guys and gals! This would definitely be helpful. I learned so much with the Exchange console, ADAC, MDT, etc. when they do that. Anything to help automate more processes!
Matthias Schneuwly commented
Would be awesome!
This would be great. I thought a few years ago all the 'back office' products were going to do this. For those things I find myself doing more often I could just copy the script, customize it a little and have a new tool.
Richard Archer commented
Agreed this would be a brilliant feature, but I'm assuming it's a little harder to implement in SCCM as unlike, for example, the Exchange Management Console, the ConfigMgr Console is not actually using PowerShell and WinRM in the background - it still relies on WMI to the SMS Provider.
It would be really helpful if the admin console could display the Powershell equivalent of actions executed in the console similar to the way Exchange does. Example: Lets say you created a new device collection using the wizard and instead of just showing a success or failure message on the completion tab, the Powershell command to create the same collection is also shown (New-CMDeviceCollection....). Implementing this would reach every console user and they could see a direct correlation between their actions and Powershell. It would be an easy way for admins who are not Powershell experts to start learning and using it.
Brendan Beetge commented
This feature would surely have my vote!