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. Maintenance window recurrence pattern offset from a base day

    Allow the recurrence pattern for maintenance windows to be scheduled with an offset from a base day.

    Meaning, if we want a maintenance window on the Wednesday following the Second Tuesday of every month, we could configure a maintenance window for the Second Tuesday with a +1 offset.

    (This would be similar to the offset option added to ADRs in 1802.)

    432 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  19 comments  ·  Collections  ·  Flag idea as inappropriate…  ·  Admin →
  2. Collection Expiration

    Provide an option to "expire" a collection where it gets removed (or at lease collection evaluations are disabled) on a specified date. This would help with the collection evaluator from becoming overloaded with processing Pilot/Test collections that were "forgotten".

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Collections  ·  Flag idea as inappropriate…  ·  Admin →
  3. Option to prevent Deployment on specific Collections

    I would like to see the ability to prevent Deployments on specific Collections. (f.e. All Systems)

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Collections  ·  Flag idea as inappropriate…  ·  Admin →
  4. Security: Prevent or prompt for modifications to collection rules with existing deployments

    We now have deployment verification to prevent damaging deployments from being created, but that doesn't stop existing deployments from being deployed accidentally.

    It would be great to prevent or atleast prompt for any modifications to collection membership rules (large number of direct adds, include, query) when the collection already has an existing deployment.

    Originally mentioned:
    https://www.reddit.com/r/SCCM/comments/4qhcwg/amawe_are_the_configmgr_team_here_to_talk_about/d4tb5qv

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  4 comments  ·  Collections  ·  Flag idea as inappropriate…  ·  Admin →
  5. Ability to assign pre/post tasks to maintenance window

    Ability to assign pre/post tasks to maintenance window and prioritize content application within the window.

    Example:
    1. patches
    2. appilication deployment A has higher priority than application deployment B
    3. packages
    4. task sequences
    5. settings mgmt remediation

    34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  Collections  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base