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.
-
Run Scripts: Ability to Edit Scripts
In 1706, once you create a script and approve it (or deny it) there is no way to alter the script except but to create a new one. Would be great to have the ability to set the script back to waiting for approval, which would unlock the code to be edited.
135 votesNoted ·AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
We have have several work items in our backlog to improve the experience here for future releases.
-
ConfigurationManager PowerShell module should register itself as an Env Variable
Today, when you install the CM Console, the PowerShell module will be placed under the %CMInstallDirectory%\AdminConsole\Bin\ConfigurationManager.psd1
This makes sense given where the user is choosing to install the console, and that's fine. But placing it here off the beaten path means that it is not importable using PowerShell's module autodiscovery features. For instance, if a module is found in any of the standard user or system paths (or registered under the $ENV:PsModulePath) the user can easily import the module without having to specify the full path, a big user quality of life win. This is the way that SQL Serverā¦
90 votes -
Create a PowerShell cmdlet too add/edit/remove duplicate hardware identifiers
New-CMDuplicateHardwareIdentifier
Set-CMDuplicateHardwareIdentifier
Remove-CMDuplicateHardwareIdentifierPlease create cmdlets to add/edit/remove duplicate hardware identifiers. We have a large organization and those pesky Lenovo Yoga's get a USB to Ethernet dongle with each one. We have over 500 dongles currently, and I don't see a way to automate importing those MAC addresses. Thanks!
47 votes -
Powershell cmdlet for adding global conditions as requirements
We are using PowerShell as a frontend for creating applications. As default we create multiple deployment type, each of them intented to run in certain environemts. These environemts are defined in some custom global conditions.
When creating the deployment type we can very easily identify which global contitions shold be set as requirement. But we miss a Powershell cmdlet to automize this task. Instead we rely on the application creator to remember to add these conditions.
So far I have found a PS-script that can add one of the build-in conditions, but it fails when trying to add a customā¦
37 votesNoted ·AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
Thanks for the suggestion. This is something we plan to address in a future release.
-
New-CMApplication rejects icons larger than 250x250
New-CMApplication rejects icons larger than 250x250 and returns the warning and error below, even though the SCCM console allows icons up to 500x500.
WARNING: The maximum size of an icon is 250px X 250px.
New-CMApplication : Validation of input parameters failed. Cannot continue.22 votes -
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 -
Provide a Powershell PackageManagement Repository and perhaps management thereof
PowerShell PackageManagement is a unified interface to package management systems and aims to make Software Discovery, Installation and Inventory (SDII) work via a common set of cmdlets (and eventually a set of APIs). Regardless of the installation technology underneath, users can use these common cmdlets to install/uninstall packages, add/remove/query package repositories, and query a system for the software installed.
Providing a dashboard/portal with the ability to manage the NuGet repository underlying the packagemanagement solution would make SCCM more attractive over phasing it out to go towards Chocolatey Enterprise.
19 votes -
Run Scripts: Need folder support for feature
It would be nice to be able to make folders and apply security to each folder for the new scripts feature.
17 votes -
Save-CMSoftwareUpdate error RPC server unavailable when connecting under a different account
My idea is to have the scenario described below supported.
When running Save-CMSoftwareUpdate command on a CMSite-PSDrive that connects to a ConfigMgr site in a different domain (used Get-Credential to pass credentials in New-PSDrive call) than the user account the PowerShell window is running as, I get error 'The RPC server is unavailable'.
I can successfully change location to the PS drive, and run other ConfigMgr PS cmdlets.
Commands:
New-PSDrive -Name <sitecode> -PSProvider 'CMSite' -Root <siteserverFQDN> -Credential (Get-Credential)
Set-Location <sitecode>:
Save-CMSoftwareUpdate -SoftwareUpdateName <name> -DeploymentPackageName <name> -VerboseVerbose output from Save-CMSoftwareUpdate call:
VERBOSE: Start: Execution of WQL query: Select * fromā¦
12 votesNoted ·AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
Thank you for reporting this. Does the same thing reproduce when downloading software updates through the console?
-
Create a PowerShell cmdlet or cmdlet parameter to add return codes to application deployment types
Add a PowerShell cmdlet or cmdlet parameter to add return codes to application deployment types.
12 votes -
11 votes
-
SCCM module cmdlet creation for folders
The ConfigurationManager module does not have any *-folder cmdlets.
I would like to see some created that allow for more folder manipulation within system centre configuration manager, for example Get-CMFolder -Name "Test" would provide me with the Folder ID, Name, Heirarchical Location in ConfigMgr and more!
As well as New-CMFolder, Move-CMFolder, Remove-CMFolder, etc!
I would also like to see the ability to add -Folder to other cmdlets, such as New-CMDeviceCollection -Name "Test" -Folder "TestFolder" so the collection called Test is made in the folder called TestFolder instead of the Device Collections root.
10 votes -
Save-CMSoftwareUpdate has no option to select the download source
The Admin-Console is capable to download Softwareupdates from WSUS or a Networkshare wsuscontent). But there ist no commandlet for that. Save-CMSoftwareUpdate seems to be the commandlet for that. If so, than the parameters for the source are missing.
7 votes -
Run Scripts: Do not preserve parameters when scripts are re-run, and log parameter usage in Monitoring
When using parameters, the last value used should be blanked out when run again. The value of parameters is the dynamics of it all. You can overwrite the value but seems it would be best servers to not retain the value after running. Would also be great if the parameter used was logged in the Script Status node for ease of tracking.
7 votes -
Incorrect Icon Size When Using New-CMApplication and Set-CMApplication
When using New-CMApplication or Set-CMApplication with the IconLocationFile parameter and an icon at least 128x128 in size, the application is created with a very small icon. I am not certain if smaller icons are effected.
7 votes -
Powershell: get-cmcollection not returning ObjectPath
The PowerShell cmdlets Get-CMCollection and Get-CMDeviceCollection/Get-CMUserCollection) returns an empty value for "ObjectPath".
This is missing in both 1710 and latest TP (currenty 1801).
This works as expected and ObjectPath = "/":
Get-WmiObject -namespace "root\sms\site_$siteCode" -query "select * from SMS_Collection where CollectionID = 'SMS00001'"This returns null/empty ObjectPath:
Get-CMCollection -Id SMS00001/Matt
7 votesNoted ·AdminAdam Meltzer (ConfigMgr Product Team) (Admin, System Center Configuration Manager) responded
This appears to be a bug in the SMS Provider. I’ll file this internally.
You can work around it in the short term by using Invoke-CMWmiQuery to run a query and add -Option Fast.
-
Include verbose information with import-cmpackage cmdlet
The Import-CMPackage cmdlet does not provide much in the way of verbose output with the -verbose flag. This would be useful to identify what the cmdlet is performing in the background to determine if package already exists with the same name or not.
Steps attempted:
$Global:VerbosePreference = "Continue"
$Global:DebugPreference = "Continue"
$Global:CMPSDebugLogging = $trueimport-cmpackage -ImportFilePath "\\localhost\c$\Users\Testing\TestPkg.zip" -Verbose
Output: Verbose: Performing the operation "Import" on target "Package: ".
Trace-Command -Name metadata,parameterbinding,cmdlet -Expression {Import-CMPackage -ImportFilePath "\\localhost\c$\Users\Testing\TestPkg.zip" -WhatIf} -PSHost
DEBUG: ParameterBinding Information: 0 : BIND NAMED cmd line args [Import-CMPackage]
DEBUG: ParameterBinding Information: 0 : BIND arg [\\localhost\c$\Users\Testing\TestPkg.zip] to parameter [ImportFilePath]
DEBUG:ā¦4 votes -
4 votes
-
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.
-
Set-CMSoftwareUpdateDeployment missing SoftDeadlineEnabled parameter
Expose -SoftDeadlineEnable to Set-CMSoftwareUpdateDeployment -SoftDeadlineEnabled
Its on Get-CMSoftwareUpdateDeployment not Set.
2 votes
- Don't see your idea?