Ideas
What features would you like to see?
All of the feedback that you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building System Center Configuration Manager, though we can’t promise to reply to all posts.
Please do not use UserVoice to report product bugs or for assisted support.
If you believe you have found a product bug, please send us a bug report through the Configuration Manager Console (1806 and newer). To do this, press the 🙂 button in the top right corner and choose “Send a Frown”. For more details, see https://docs.microsoft.com/en-us/sccm/core/understand/find-help.
If you require assisted support, please see https://aka.ms/cmcbsupport for more details.
Standard Disclaimer – our lawyers made us put this here ;-)
We have partnered with UserVoice, a third-party service, so you can give us feedback. Please note that the System Center Configuration Manager feedback site is moderated and is a voluntary participation-based project. Please send only feature suggestions and ideas to improve Microsoft Configuration Manager. Do not send any novel or patentable ideas, copyrighted materials, samples or demos. Your use of the portal and your submission is subject to the UserVoice Terms of Service & Privacy Policy, including the license terms.
-
Add query based parameters for script
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.
8 votes -
Ability to run scripts from the SCCM server, like a built in Web Service
Adding the ability to run powershell scripts on a SCCM site server when called from a Task Sequence or Compliance item.
Some scripts need special rights or modules that are not available to Users or client devices. (ActiveDirectory, ConfigManager actions)
Being able to add these scripts in the SCCM console and have them ran from a call back from the client or Task Sequence would save running multiple Web Services on the server.
1 vote -
Pass script parameters with Invoke-CMScript
Allow the Invoke-CMScript to pass script parameters. This could be done with a ScriptParameter hashtable similar to how Invoke-CMReport functions.
19 votes -
PowerShell Cmdlet for Modifying Nested Task Sequence (Get/Set-CMTSStepRunTaskSequence)
It would be very helpful to have a cmlet that will allow you to modify the "Run Task Sequence" with PowerShell.
I'd like to be able to script replicating an entire task sequence "suite" (including all of the nested sequences) and re-linking the new nested sequences.
My use case is something like this:
I want to start development work on a new build revision. The script would duplicate the production sequences (both parent and children) and repoint the "Run Task Sequence" steps to new "DEV" child sequences.This would automate the process and ensure that none of the production sequences…
6 votes -
Get-CMDetectionClause
Could we have a get-cmdetectionclause command? I'd like to be able to get an existing detection clause for a deployment which would be useful for not only managing existing detection clauses but being able to explore and re-using them for other applications.
As it is right now I use get-cmapplication | get-cmdeploymenttype | select SDMPackageXML in order to view the detection method as XML.
1 vote -
Unify Powershell Functionality
The recent Powershell features like 'Run Script' and allowing them to be added directly to a Task Sequence step are fantastic, but things are beginning to feel somewhat fragmented.
It would be great if SCCM had a central script repository, maybe backed by git, that we could pull scripts from as opposed to adding them.
This would allow us to easily use the same code in a Task Sequence and a 'Run Script' without having to maintain it in multiple places. Perhaps we could even add a special Powershell Script Package Program type that would pull a script from the…
11 votesplanned ·AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
This is something we’re working on — see https://www.microsoft.com/en-us/microsoft-365/blog/2018/07/30/introducing-the-community-hub-in-configuration-manager-technical-preview-1807/ for more details and be sure to try it out in the technical preview releases.
-
Set-CMDiscoveryMethod does not have a parameter to configure the discovery account
Additional context can be found:
https://www.reddit.com/r/SCCM/comments/a0lgdt/powershell_system_discovery_container_account/7 votesstarted ·AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
This functionality is in Technical Preview 1901.
-
CMPivot Eventlog is using Get-Eventlog instead of Get-WinEvent
The current 1806 implementation of CMPivot is using the cmdlet GEt-Eventlog read event log entries. The PowerShell command is:
$events = get-eventlog -LogName $logName -Newest 50 -ErrorAction StopThis limits the logs to be read from to logs like Application, Security, System and only some others. On my client (Get-EventLog -List).Count has only 12 logs.
The better command would be Get-WinEvent. Where I can access all logs. The command (Get-WinEvent -ListLog *).Count returns 463 logs.
3 votes -
set-cmcollection does not terminate on name collisions with errors in -errorvariable and doesn't seem to work with try/catch
If we could get this functionality it would go a long way in automating collection management.
2 votes -
SMS_ConfigurationItemLatest.ObjectPath property is null
Both the iResultObject from Get-CMConfigurationItem and the SMS_ConfigurationItemLatest object returned from a WMI query have a null value as the objectpath property.
Current workaround is to make recursive queries on SMS_ObjectContainerNode to get the ObjectPath of these objects.
1 vote -
Import/Export Cmdlet Parameter aliases
Could we please have a common alias for the file path parameters in the various import/export cmdlets?
For example, currently we have:
1. Export-CMBaseline uses -Path to set output path, and
2. Export-CMTaskSequence uses -ExportFilePath.Then we have:
1. Import-CMBaseline using -FileName to determine location of exported files
2. Import-CMApplication using -FilePath,
3. Import-CMTasksequence using -Path.A common alias like "Path" or "FilePath" for all these parameters will be very handy in reducing complexity of scripts calling your Cmdlets.
1 voteNoted ·AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
Thank you for your feedback. Improving the consistency of the Import/Export cmdlet parameters is definitely something on our list for improving.
-
New-CMSoftwareUpdateAutoDeploymentRuleDeployment missing -RequirePostRebootFullScan option.
The New-CMSoftwareUpdateAutoDeploymentRuleDeployment command is missing the -RequirePostRebootFullScan option. This should be added similar to the New-CMSoftwareUpdateDeployment command.
7 votes -
Run Scripts: scripts results does not show systems offline or failed
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.
13 votes -
Run Scripts: Create Collection based off of results
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.
2 votes -
Run Script: Ability to pass collection variables
I want to run a powershell script with the new Run Script, with the ability to see the collection id, collection variables, collection members that script is being ran against. The script runs on the local system as SYSTEM so it can't reach back to SCCM to obtain this information. I know you can add credentials to allow this, but a simple GET-CMRunScriptCollectionName or GET-CMRunScriptCollectionVariables would be nice.
3 votes -
Provide cmdlet to get deployment status summarization statistics
Need a cmdlet to gather/run a deployment status summarization. Providing the deployment statistics with a list of each device and its current state.
In this way I could automate against which systems are currently in error/unknown. There is no simple way to do this outside of the GUI, and I may have dozens of deployments to verify against.
I've seen some possibilities using SQL queries to join 3-4 tables together to pull this off, but it lacks message state value translations. The data coming back doesn't have meaning.
Its simple... I need to get a list of devices that are…
4 votes -
Add a cmdlet to delete (or at least disable) a Client Settings deployment (cmclientsettingsdeployment)
There is currently no cmdlet to delete or disable a deployment of Client Settings. You can create a deployment by using the Start-CMClientSettingDeployment cmdlet but there is absolutely no way of stopping, deleting, or disabling the deployment. If you run a Get-CMDeployment against a collection, it only returns all deployments except a Client Setting.
4 votes -
Powershell script Collection
After running a script on a collection or set of machines have the ability to automatically create a collection on machines that failed the script or machines that could not be connected to. So that after the machine is online the script can be run against it.
1 vote -
Powershell 6.x support everywhere in SCCM
Explicitly being able to select the option of using PowerShell 6.x in scripts/compliance rules/task sequences would be a good future thinking feature to adopt as soon as possible.
Ideally a version option built in to SCCM like that for x32/64 OS, but for PS 5.1/6.x would make this interesting.
2 votesNoted ·AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
We have no plans to support PowerShell 6 or newer at this time as it requires a completely new runtime and .NET Core. This may change in the future if there’s enough demand for this.
-
Add the ability to add and edit Install Behavior for Application Deployment types with PowerShell cmdlets
Add the ability to add and edit Install Behavior for Application Deployment types with PowerShell cmdlets
1 vote
- Don't see your idea?