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.

If you believe you have found a product bug, please use Feedback Hub. For more details, see: https://docs.microsoft.com/en-us/sccm/core/understand/find-help.

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. add a powershell possibility to add requirements to a deploymenttype of an application

    At the moment it is not easy to add requirements to an application deploymenttype with PowerShell. I think many of us would benefit if this would be simplified.

    86 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      8 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →

      (correction: this change was too late for 1704, it will be in 1705)

      For 1705 TP we have added an initial ability to add detection method clauses to a MSI, Script, or Mac deployment type.

      For more details see: https://blogs.msdn.microsoft.com/ameltzer/2017/04/20/powershell-how-to-add-enhanced-detection-methods-to-deployment-types-1704-tp/

      Please try it out and let us know what you think. We don’t have full UI parity yet but this is something we are working toward.

    • Adjustable Window Sizes within Admin Console

      It would be nice to have the ability to adjust window sizes within the console. As an example, the Membership rule window in the collection properties only has enough room to show 2 lines. Being able to maximize or edit to a custom size and have the console remember these sizes would be great.

      This could be incorporated into the fixes that are being introduced with the High DPI resolutions.

      38 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        6 comments  ·  Admin Console  ·  Flag idea as inappropriate…  ·  Admin →

        Doing this everywhere in the console would be expensive/difficult. Rather than wait to make any improvement until the time we can fix it all… I’m curious what the top 10 most important places to fix are. I’m thinking we fix those first, and then go from there.

      • Include orchestration of software updates especially for tiered solutions

        Today it's only possible to orchestrate software updating based on a membership in collections.
        This is however rarely enough for more complex setups where you might have back-, middle-, and front tiers in your setup.

        Therefore I recommend adding a dependency system between computer objects, so that you can orchestrate at least the following:
        1) Which tier of servers are patched first, second and third etc.
        2) Reboot order between the different tiers which includes an accept of one tier being fully patched and rebooted before the next tier is begun updating.
        3) Ability to choose between warning or rollback…

        30 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          1 comment  ·  Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
        • Give more granular control over the 2 hour SUP failover timeout

          Currently, failover from one SUP to another SUP is always at least 2 hours. Even with the new Boundary Group design, with controllable failovers - the minimum is still 2 hours. Allow admins to control that minimum, and set it smaller than 2 hours.

          6 votes
          Vote
          Sign in
          Check!
          (thinking…)
          Reset
          or sign in with
          • facebook
          • google
            Password icon
            Signed in as (Sign out)
            You have left! (?) (thinking…)
            under review  ·  0 comments  ·  Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
          • SMB1 / SMBv1 (deprecated) is used in Configmgr 1706 to Capture Windows 10 1709. Please update Configmgr to accept SMBv2/3...

            SMB1 / SMBv1 (deprecated) is used in Configmgr 1706 to Capture Windows 10 1709.

            By default, SMB1 / SMBv1 is not installed by default in Windows 10 1709.

            Please update Configmgr to accept SMBv2/3...

            1 vote
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              0 comments  ·  Role Based Access & Security  ·  Flag idea as inappropriate…  ·  Admin →

              Probably need to file a support case, or a connect bug. Looking into this, SCCM 1710, w/ win10 1709 (and that ADK) does not use SMBv1. We are able to successfully capture w/o SMBv1.

              We’ll need support to work with you on your repro.

              Please reply to my email, and we should get that process started.

              Part of our verification was
              Add Powershell support to an RS3 (1709) Boot image (you can do this via boot image properties or with DISM)
              Add Command support
              Create a task sequence with that boot image
              Add a task sequence step to Restart to WinPE
              Open command window (F8)
              Run command Powershell.exe Get-SMBServerConfiguration which shows EnableSMB1Protocol=False meaning we’re not using SMBv1 during capture phase

            • Don't see your idea?

            Feedback and Knowledge Base