Since version 1707 it's now possible to run Powershell scripts for a collection, but these scripts cannot be scheduled. It would be of real value if these Powershell scripts could be scheduled.

Provide ability to rename scripts. We'd like ability to differentiate between test and production scripts or rename if the functionality changes. Or, just have the ability to fix typos without recreating the script/approvals.

It would be nice to be able to make folders and apply security to each folder for the new scripts feature.

Currently, CMPivot uses Get-Item in PowerShell to gather Registry() information. By default, only HKLM and HKCU exist as a PSdrive. CMPivot could work around this by creating a HKU on the fly during a query.

New-PSDrive -Name HKU -PSProvider Registry -Root HKEY_USERS

This would allow greater capabilities in querying the registry and searching for profile/user based registry keys.

Futher explanation here: https://twitter.com/PotentEngineer/status/1327354096932827138?s=20

Allow the Invoke-CMScript to pass script parameters. This could be done with a ScriptParameter hashtable similar to how Invoke-CMReport functions.

Currently the script seem to sort by 'Type' or 'Approval State' and I have to choose 'Name' every time I go in to scripts.

I'd like the ability to add a description for the Script I'm adding into "Run Scripts". Right now I try to make the names descriptive, but would like to go into further details about what parameters they can use, what's going to happen, etc.

Run Script: export the results from Script Status to Excel file

SCCM PowerShell scripts running in a corporate environment are hobbled due to the NT AUTHORITY\SYSTEM context. I have multiple cases where I could create an Application that just runs a PowerShell script but the script needs to run as a domain admin to do what it has to. The new Scripts feature also needs run-as functionality for fire & forget type tasks. Including a run-as facility in SCCM would significantly extend the product's flexibility.

The SCCM scripts feature is new and so far works very well, however there is no feedback on systems offline or failed. The lower pie graph shows the numbers offline/failed but you cannot view them. The results tab only shows return codes of systems that actually executed scripts.

Would love to see the ability to right click on a Script in the software library and be able to select Deploy.

Create cmdlets for the new in console Powershell scripts. Some good ones would be new Script Deployment and get script results.

EX:
New-CMPSScriptDeployment -Name "Script Name" -CollectionName "Collection Name"

It would be nice to have the option to add some query based parameters for script (WQL or SQL). So values for parameters could be dynamic based on a query and scope of the user who trigger the script.

i.e. We could have hiding deployments (without any notifications to the end users), then the admin user could select application or updates from the list to enforce deployment.

Make it possible to run powershell scripts directly from CM created "collections" eg when you click on somethig under monitoring to check client problems and it brings you bak to Assets and Compliance whith a collection of the devices with a certein problem.

So that you wont have to make a new collection of these devices and then run the script.

Sometimes you just want to fire & forget, and then later maybe check back in on the monitoring tab.

The scripts feature provides a powerful feature to provide real time information on an enterprise, that hardware inventory may not provide. It would be very helpful if you could create a collection based on the results of Script, or add the machines to an existing collection natively through the CM Console.

We would glad to use opportunity for clearing "Script Status", re-run expired scripts and modify scripts without deleting them. We need to ran Scripts several times, and want to clear not needed statuses.

What if CMPivot changed to a client notification methodology. Send the CMPivot "Question" to each client, and let the client answer with its results with randomization. Afterward, the CMPivot query would record its last run time and cache the results for a period of time, which would be visible in the console. Moving to a notification style procedure would avoid waiting for synchronous CMPivot (Slow) results and allow for distributed processing (Fast).

Allow filtering on Monitoring - Scripts. Filter by time and date, collection, and script name.