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. ADR Available Deployments

    I would like to see ADR's support the creation of Available deployments in addition to Required deployments. We have some business cases where a certain subset of servers are aren't allowed to "push" software updates to until the server/app owners have verified the patches.

    The issue is that these servers don't have connectivity to the internet so we have to deliver them via ConfigMgr. By creating an Available update using an ADR, it streamlines our ability to "deliver" the updates to all systems, and allow the Patching Team, or App/Server owner to patch according to their own business schedules.

    187 votes
    Vote
    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      18 comments  ·  Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
    • Complex scheduling: Enable patch deployments to servers based on SDLC (Dev / QA / Prod / DR)

      Based on Patch Tuesday, allow application / business owners to select appropriate down time for the server as well as a sequenced order (e.g., Development servers during the first week after Patch Tuesday, QA on the second week after Patch Tuesday, Production servers on the third week after Patch Tuesday, et cetera). This allows the business owners to "own their own destiny" and get systems administrators out of the business of coordinating patching maintenance windows. In addition, the ability to insert "change freezes" that force the schedule to increment all downstream targets out by an additional week to compensate for…

      60 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        planned  ·  9 comments  ·  Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
      • Request full control over allow/disallow force closing of Office 365 apps when installing updates instead of force closing Office apps

        In ConfigMgr 1610 Update Rollup 1 provided the change so Office 365 Updates did not force close any office applications when Office 365 patches were installed through ConfigMgr Software Center.
        https://docs.microsoft.com/en-us/sccm/sum/deploy-use/manage-office-365-proplus-updates#restart-behavior-and-client-notifications-for-office-365-updates

        With ConfigMgr 1706 we require the option to disallow force closing of office 365 applications when patches are installed through the ConfigMgr Software Center.

        52 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          planned  ·  2 comments  ·  Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
        • Don't see your idea?

        Feedback and Knowledge Base