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. Show Powershell equivalent command(s) at any wizard completion

    At wizard completion for anything, show the Powershell cmdlet equivalent like in other System Center products.

    1,362 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    24 comments  ·  Admin Console  ·  Flag idea as inappropriateā€¦  ·  Admin →
  2. Prompt users for reboot, but NEVER force it

    The reboot settings only allow for the user to postpone a reboot for up to 24 hours. Why can't we expand that time or just keep reminding them forever until they reboot themselves? The longer that they have been pending a reboot, remind (pester) them more frequently. Or auto reboot if nobody is logged on.

    1,268 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    36 comments  ·  Compliance Settings  ·  Flag idea as inappropriateā€¦  ·  Admin →
  3. Install Servicing Stack Updates Before Other Updates

    Currently, when servicing stack updates and regular updates are deployed in the same software update group, the patches do not apply in a determinant order. This leads to cases where a cumulative update that requires a new servicing stack is installed before the servicing stack itself.

    While this can be worked around by separately deploying the servicing stack update before updates that require said servicing stack, it would be much more convenient if the update installation process checked if there are any servicing stack updates to be deployed and automatically installed them first

    1,029 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  17 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  4. Make ConfigMgr work with Autopilot and Enrollment Status Page (ESP)

    When deploying a device using Autopilot, the Enrollment Status Page (ESP) is used to prevent access to the desktop until the device provisioning tasks are complete. But ConfigMgr doesn't integrate with the ESP, so there's no way to wait for packages, apps, or task sequences - the user doesn't know when the process is done. Add that integration.

    810 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  19 comments  ·  Operating System Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  5. Revamp ConfigMgr's cluster patching, and remove it from PreRelease

    Cluster patching feature was added in #SCCM CB 1602, but has been in prelease for a long time. It needs to:
    1) Have improved/revamped UI
    2) Remove dependency on collections
    3) Orchestrate patching for any machines, not just servers/clusters
    4) Remove the feature from prerelease

    623 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  30 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  6. Software Center: Add categories to maching targetted deployments.

    The new Software Center in 1511 should also categorize Applications using the user category even if it is not deployed to users but systems instead. It should reflect the user category no matter what.

    372 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  36 comments  ·  Software Center  ·  Flag idea as inappropriateā€¦  ·  Admin →
  7. Software Center "Sort by" default view

    Change default "sort by" order from "Most recent" to Alphabetic list (Application name A-Z). Or remember the setting for the client. Or allow a SysAdmin setting for site-wide default setting. It always resets back to Most recent.

    346 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    14 comments  ·  Software Center  ·  Flag idea as inappropriateā€¦  ·  Admin →
  8. Stop unnecessary "New software is available" pop-up on each logon after a user has uninstalled an available application.

    After a user installs an application that was deployed as "Available", but later uninstalls the application, the user gets a balloon pop-up every time they logon saying "New software is available".

    There is NO way to prevent this from happening apart from removing the user from the collection where the application was deployed, and adding them back. This has been the case since CM12 was released but this is not a desirable behavior especially when there's no "valid" way of preventing this.

    335 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  16 comments  ·  Software Center  ·  Flag idea as inappropriateā€¦  ·  Admin →
  9. Automatically Publish Full Content for Third Party Software Updates

    With the release of CB 1806 we are now able to publish third party updates using custom catalogs. Ideally, third party patches would function exactly like first party patches from an administration and automation perspective. Currently there's two main areas where this is not the case.

    Synchronization Schedule:
    I could be wrong on this but I believe that subscribed catalogs sync automatically every 24-hours. While that's nice, it would be great to simply integrate with the existing sync schedule. Sync the catalogs, publish relevant metadata to WSUS, then sync the SUP(s).

    Automatic Deployment Rules:
    Currently, only update metadata is publishedā€¦

    280 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  14 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  10. Have the ability to remove a CAS when only one primary site is left

    Beginning with 2012SP1, we have the ability to add a CAS to an autonomous primary site. It could be interesting to reverse the proposition by having the ability to remove a CAS above a Primary when a CAS is no longer needed or has been set for a wrong reason.
    I know that it could be done through creating another hierarchy and using migration tasks by this is quite difficult for it requires additional hardware.

    251 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  16 comments  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
  11. ADR New Search Criteria, Deployed = yes/no

    I propose a new search criteria for ADR, to avoid multiple deployments for a single update. This is a pain to clean up afterwards.

    224 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  12 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  12. 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.

    219 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    19 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  13. F8 Troubleshooting Environment Steroids (F8TES)

    Replace the OSD Boot Image "Enable CMD Support (testing only)" feature with something that is more robust, helpful, and useful outside of testing like the F8 Troubleshooting Environment Steroids (F8TES).

    Info: Display full name of task sequence and its ID
    Info: Display full name of TS Deployment and its ID
    Info: Display full name and type of error step
    Info: Display error code
    Info: (Stretch Goal) Display useful error message for top 10 errors

    Button: ā€œOpen Command Promptā€
    - Launches the command prompt
    - Defaults to Insert instead of Overwrite (it currently defaults to overwrite in the WinPE phase)

    Button:ā€¦

    188 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    13 comments  ·  Operating System Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →

    Updating status to planned.

    We shipped our 1905 Technical Preview today.

    Doc: https://docs.microsoft.com/sccm/core/get-started/2019/technical-preview-1905
    Blog: https://techcommunity.microsoft.com/t5/Configuration-Manager-Blog/Group-applications-into-a-single-deployment-in-ConfigMgr/ba-p/624318

    This preview contains the first release of the task sequence debugger. We’ll continue working on it to address more of the asks in this item.

  14. DSC to replace or compliment basline feature

    DSC is a wonderful framework for handling baseline configurations across Windows and Linux machines, but it's completely unsupported in SCCM directly. While a Pull server is certainly more simplistic than an SCCM hierarchy, it would still be very beneficial to have some integration in a couple of areas:

    Management Points can easily be configured to host mof configurations for clients, and a new client policy class for allowing the SCCM agent to configure the pull server settings on a host would be great. Alternatively a new role could be made ... not sure that would feel as elegant.

    The baselineā€¦

    166 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Compliance Settings  ·  Flag idea as inappropriateā€¦  ·  Admin →
  15. Task Sequence Editor Search

    We have over 300 Groups/Steps in a couple of our task sequences. It would be really helpful to be able to search with the Task Sequence Editor. Either by step name or group name. In a perfect world it would be helpful to search descriptions or other text content within each group or step.

    163 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    10 comments  ·  Operating System Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  16. Emergency/Immediate halt or pause of a software deployment then resume a software deployment when needed.

    In SCCM, there should be a way to stop or discontinue a software deployment should there be an emergency or issue and then resume the deployment when desired. For example, if software has been deployed to the environment and in an event of an emergency or major issue, SCCM should allow the administrator to stop or pause the software deployment in real time, resolve the issue then restart the software deployment again. Ideally, this would accomplish in one push of a button. Unlike now, the administrator goes and deletes the deployment and recreates the deployment again leaving the inability toā€¦

    118 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  7 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  17. 104 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    8 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →

    Updating status to planned, see https://docs.microsoft.com/en-us/sccm/core/understand/find-help#send-a-suggestion for an explanation of each status value.

    Weā€™ve shipped fixes for a few scenarios that can cause this in 1902 but know there are some scenarios left.
    May we ask anyone still experiencing it on 1902 to gather verbose logs from the client and send a frown so we can troubleshoot additional scenarios that cause the error.

  18. 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ā€¦

    69 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  9 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  19. Client Settings - Computer Restart - Allow longer than 1440 minutes, show friendly time

    Currently, the maximum an administrator can give users to reboot their systems is 1440 minutes (24 hours). Please let us specify up to 7 days. The goal of the delay is to allow a reasonable amount of time for an end user to save their work and reboot without losing anything. The 24 hour limit means that if a user is gone for a day, there is a strong chance they could lose their work. Allowing up to 7 days seems like a better compromise between end user control and respecting admin intent/organizational need.

    57 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  8 comments  ·  Admin Console  ·  Flag idea as inappropriateā€¦  ·  Admin →
  20. Ability to enable/disable any deployment (like you can with software update deployments)

    You should be able to enable or disable any deployment (for applications, packages, software updates, etc) by right-clicking and selecting enable or disable.
    Currently to disable an application deployment you either have to delete the deployment or retire the application and for packages you need to disable the program.
    Software update deployments already have this feature.
    You should also be able to enable/disable a deployment from the Monitoring workspace.

    52 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  1 comment  ·  Admin Console  ·  Flag idea as inappropriateā€¦  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base