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. 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
    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. 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 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 →
  3. 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
    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 →
  4. MVP-Set-CMClientSettingSoftwareUpdate

    add option to manage express updates via Set-CMClientSettingSoftwareUpdate (Enable/Disable and Port used)

    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 →
  5. MVP- Set-CMClientPushInstallation NTLM

    the Set-CMClientPushInstallation should have an option to set the Allow connection fallback to ntlm

    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 →
  6. MVP-Powershell client settings for software center

    add a new Set-CMClientSetting to customise software center. today the only way is to use the props SettingsXml for SMS_SCI_ClientComp (SoftwareCenter) WMI and create a xml to configure it.

    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. Run Scripts: Ability to run unapproved scripts on a test collection

    The "run script" feature is fantastic, but somewhat clunky when multiple lower level admins are adding scripts, as they can't be tested before approval.

    It would be great if we could designate a "development" collection for running scripts that have not been approved yet.

    2 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 →
  8. 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> -Verbose

    Verbose output from Save-CMSoftwareUpdate call:

    VERBOSE: Start: Execution of WQL query: Select * from…

    12 votes
    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 →
  9. New-CMAppliccationDeployment available updatesupersedence deadlinedatetime SCCM 1802

    Please enable the deadlinedatetime parameter in the CMDLet for available Packages, so that we can autoupdate available software again without needing the user to take Action.

    3 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 →
  10. Run Scripts: Prevent Script feature from sending all (i.e. optional) parameters

    What I've noticed when using the new "Scripts" feature is that SCCM runs scripts with a very specific command format/syntax when calling a PowerShell script. Part of that is explicitly specifying every individual script parameter, regardless of whether it is mandatory.

    I suppose that normally, this shouldn't be a problem, but besides being unnecessary and against the spirit of optional parameters, I've also been running into what I assume is a bug, where SCCM fails to properly pass all parameters. There seems to be a parameter limit, or more likely, a character limit to the command line SCCM runs on…

    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 →
  11. Run Scripts: Allow parameters to be marked as passwords so it's hidden when entering

    Run Scripts: Allow parameters to be marked as passwords, so scripts can be executed by passing on passwords but the password isn't displayed while being typed.

    Real life example: Using PowerShell scripts to run Deep Freeze tasks such as freezing or thawing computer. The Deep Freeze command line tool requires entering the passwords to be able to execute the commands.

    2 votes
    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 →
  12. Predeclare devices with powershell

    It's could be great to add a powershell cmdlet to import devices, like Import-predeclaredDeivces -Type Android -EMEI 000000 -Description "User A"
    Or by importing a CSV :
    Import-predeclaredDeivces -Csv c:\import.csv

    3 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 →
  13. Run Scripts: Option to be integrated with Application / Packages deployment

    Running Script : option to be integrated with Application / Packages deployment. On going into deployment type or in package program we should have option to use approved scripts from console.

    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 →
  14. 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 →
  15. 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 →
  16. Powershell - Return TopConsoleUser

    Get-CMTopConsoleUser -Computer MyPC

    6 votes
    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 →
  17. 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 →
  18. 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 →
  19. 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 →
  20. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  2 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base