Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Run Scripts: Add Deploy in the Scripts section in the software library

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

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  2. Run Scripts feature should support other scripting types (VBScript, Perl, etc)

    It would be awesome if more languages were supported for real-time Script deployment in addition to PowerShell. Maybe VBscript, Perl or Javascript, etc.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  3. Run Scripts: Actions for Power Shell scripts in SCCM 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.

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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 = $true

    import-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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  5. Should support "run as" functionality when executing scripts (Applications, Run Scripts, etc.)

    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.

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  6. Run Scripts: Should be able to invoke from Deployment Status Node

    Run scripts brought a brand new model to handle client troubleshooting, but it can run from collections only.
    it would have been super useful to be able to run it on a machine\category from the Deployment Status node and then maintain clients with in progress \ unknown \ active \ inactive state.
    today when we have a list of computers who didn't report their status we need to manually create a collection with these clients to run a scripts and there's not even a built-in way to create a collection from the asset details

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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…

    41 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  10. Run Scripts: Need improved monitoring and reporting on script execution

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

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  11. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  3 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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.

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  4 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  13. PowerShell CmdLets: Improvement for Software Update Maintenance

    Paging Adam Meltzer.
    I’ve spent the last couple of weeks writing a PowerShell script to provide end-to-end maintenance of software updates. My goal was to use the CM cmdlets as much as possible. While I think I have everything working the experience leads me to make the suggestions below. In all honestly; maybe I’m just doing it wrong and there is a way to do the things I couldn’t figure out.
    The documentation for Get-CMSoftwareUpdateDeploymentPackage says that it returns a CMSoftwareUpdateDeploymentPackage object but it’s actually returning WqlResultObjectBase. Maybe I’m just supposed to cast it but I failed trying.

    I could…

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  14. Run Scripts: Need cmdlets to support feature

    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"

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  15. Run Scripts: Need ability to schedule execution

    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.

    80 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add NumberOfDependedDTs property to Get-CMApplication

    Currently, the only place to see NumberOfDependedDTs is from Get-CMDeploymentType. Other properties like NumberOfDependentDTs and NumberOfDependentTS have been propagated to the Application Level, it would be useful to have NumberOfDependedDTs too.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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.

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  18. Remote powershell for SCCM

    Like: Import-PSSession $(New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://server.domain.local/PowerShell/)
    -But for SCCM..

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  19. Export all data option for key nodes

    I would like the ability to right-click various nodes, eg packages, applications, task sequences, etc and export the data for that node to a file, eg csv which could easily be read back in via powershell. This would allow test environments to be set up quickly and might even help provide an a way to restore a production environment if all else fails...

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  20. Issues with Import-ClientConfiguration

    Import-CMComputerInformation is not allowing me the same access via Powershell as the console itself.

    https://www.reddit.com/r/SCCM/comments/6dipv2/permissions_to_importcmcomputerinformation/

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base