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.

How can we improve Configuration Manager?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 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 →
  2. Collection Configure Alerts

    Create a powershell to configure the alerts on a specific collection. like adding collection to EP dashboard and configure thresholds

    1 vote
    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 →
  3. 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 →
  4. Set-CMAutoDeploymentRuleDeployment to include missing AllowWUMU and AllowUseMeteredNetwork

    Although you can now add multiple deployments to a single Automatic Deployment Rule there a couple of options that can be read but not set. These are:

    "If software updates are not available on the distribution point in current, neighbor or site boundary groups, download content from Microsoft Updates."
    and
    "All clients on a metered internet connection to download content after the installation deadline, which might incur additional costs"

    I can successfully retrieve all Deployments associated with an Automatic Deployment Rule via the Get-CMAutoDeploymentRuleDeployment cmdlet and see the current settings for these properties by parsing the DeploymentTemplate XML.

    1 vote
    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 →
  5. 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 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. The cmdlet move-cmobject FolderPath does not reflect name of Applications node

    The folder names are different in the console and the cmdlet Move-CMObject.
    Console: Applications
    Cmdlet: Application
    Since this is a standard folder regardless of site code, the names should be the same.

    1 vote
    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 →
  7. MVP - DCR wanted for server groups

    My customer has +_ 600 maintenance windows using the server grouping feature .

    Feature Request Nr1 : They use the node drain / node resume feature with PowerShell. They are still modifying and changing the script almost every week . That script is used for those 600 collections :

    a) a central repository/place to enter the script details and be able to reuse that for each server group collection like for power management custom templates .
    b) If they make a change in the “central” PowerShell repository , it keeps history ( Like application revisions ) and replaces that automatically…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  8. Included canned powershell scripts

    Include canned scripts for creating collections applications and deployments with the ability to create a template from selections.

    0 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 →
  9. PowerShell Cmdlet to collections & deployments for a computer

    Would be good to have a PowerShell CmdLet to get information on all collections and deployment for a computer is listed for.

    0 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 →
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base