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. 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…

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

      This feature will evolve from the “run scripts” features that first showed up in ConfigMgr 1706 tech preview. It lets you build a library of powershell, and execute them on demand. We will evolve DSC capabilities into this feature too.

    • 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.

      118 votes
      Vote
      Sign in
      Check!
      (thinking…)
      Reset
      or sign in with
      • facebook
      • google
        Password icon
        Signed in as (Sign out)
        You have left! (?) (thinking…)
        7 comments  ·  Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
      • Remote tools - client setting to change client service to Automatic startup

        One of the biggest issues I hear with the Remote Tools is that when you restart a machine it takes a couple of minutes before you can remote control it again. This is due to the delayed start of the service. I assume that this cannot be changed per default but give us the option using a client setting to change it to Automatic instead of using a GPO would be really sweet!
        This is very similar to the following feedback item. https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/8471107-fix-remote-control-bug-after-client-reboot#comments

        108 votes
        Vote
        Sign in
        Check!
        (thinking…)
        Reset
        or sign in with
        • facebook
        • google
          Password icon
          Signed in as (Sign out)
          You have left! (?) (thinking…)
          2 comments  ·  Remote Control  ·  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…

          57 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  ·  8 comments  ·  Software Updates  ·  Flag idea as inappropriate…  ·  Admin →
          • Peer Cache Options

            Add an option to have Peer Cache to work with boundary groups, subnet broadcast or both. My understanding is that 1607 Peer Cache will broadcast local subnet for peers that have the content, 1610 it's based off of Boundary groups. In environment, using boundary groups for peer cache will not work, like to have the option to tell the clients to use boundary group, subnet broadcast or both?

            55 votes
            Vote
            Sign in
            Check!
            (thinking…)
            Reset
            or sign in with
            • facebook
            • google
              Password icon
              Signed in as (Sign out)
              You have left! (?) (thinking…)
              3 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
            • 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…

              50 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  ·  4 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
              • 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.

                43 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  ·  1 comment  ·  Admin Console  ·  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.

                  42 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 →
                  • delete each collection member from the database

                    The "Delete each collection member from the database" tick box clickable field extends to immediately above the "OK" button, making it extremely easy to select on accident. The field should only exist within the space of the box itself, or slightly outside of it.

                    34 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  ·  4 comments  ·  Admin Console  ·  Flag idea as inappropriate…  ·  Admin →
                    • Integrate the features of the SCCM Client Center into console

                      The third party application SCCM client center provides essential troubleshooting support for the client. Why not integrate the features into the Admin console?

                      10 votes
                      Vote
                      Sign in
                      Check!
                      (thinking…)
                      Reset
                      or sign in with
                      • facebook
                      • google
                        Password icon
                        Signed in as (Sign out)
                        You have left! (?) (thinking…)
                        2 comments  ·  Troubleshooting & Support  ·  Flag idea as inappropriate…  ·  Admin →
                      • Allow Client Notification actions to be triggered from the Devices node.

                        Please allow Client Notification actions to be triggered from the Devices node. You currently can only do this from Device Collections.

                        9 votes
                        Vote
                        Sign in
                        Check!
                        (thinking…)
                        Reset
                        or sign in with
                        • facebook
                        • google
                          Password icon
                          Signed in as (Sign out)
                          You have left! (?) (thinking…)
                          2 comments  ·  Collections  ·  Flag idea as inappropriate…  ·  Admin →
                        • Update CM cmdlet documentation and downloadable help file

                          Running update-help pulls down a help file to an older version of the cmdlets. For instance, do a clean install of the console and cmdlets.
                          Type:

                          Get-Help Add-CMApplicationCatalogWebsitePoint

                          On a machine that has not had the help file updated, you will see 6 parameter sets under Syntax. Run update-help and then try again. You will now see 2 parameter sets under Syntax. In addition, there is no detailed information for the new cmdlets added.

                          7 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  ·  3 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                          • Set-CM<Type>DeploymentType fails with Invalid Property when updating Content Location

                            Since I updated to 1706, any of the Set-CM<Type>DeploymentType cmdlets fail with an error when I try to update the content path/location to another location. Based on the error message, it seems the cmdlets need to have extra parameters added to handle the separate Install and Uninstall content paths/locations. Perhaps you could add -UninstallContentLocation and a switch for -UninstallContentSameAsInstallContent.

                            Set-CMScriptDeploymentType : Invalid property: object Application(ScopeId_8C35D19A-F107-4878-83CC-9E26B213220D:Application_a463d8c5-c106-43ae-993b-f5bcb2f4ae4c:15) property
                            DeploymentTypes.DeploymentTypes[0].Installer.Installer.UninstallContent: Uninstall Content not found in Contents collection
                            At line:54 char:3
                            + Set-CMScriptDeploymentType -ApplicationName $cmApplicationNa ...
                            + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                            + CategoryInfo : NotSpecified: (:) [Set-CMScriptDeploymentType], InvalidPropertyException
                            + FullyQualifiedErrorId : Microsoft.ConfigurationManagement.ApplicationManagement.InvalidPropertyException,Microsoft.ConfigurationManagement.Cmdlets.AppMan.Commands.SetScriptDeploymentTypeCommand

                            7 votes
                            Vote
                            Sign in
                            Check!
                            (thinking…)
                            Reset
                            or sign in with
                            • facebook
                            • google
                              Password icon
                              Signed in as (Sign out)
                              You have left! (?) (thinking…)
                              3 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                            • PowerShell cmdlet "Remove-CMMaintenanceWindow" should accept Window Time as parameter

                              Powershell cmdlet "Remove-CMMaintenanceWindow" should accept StartTime as a parater. Current implementation only accepts limited parmaters of collectionid, and maintenance window name. If you have two windows by the same name, with different start times... you will remove both by using this utility. I suggest it should also accept the StartTime as a paramter for specific window deletion. Maintenance windows are a point in time schedule, and therefore the Point in time should be considered as a parameter for removal. The current implementation of this cmdlet is dangerous, and cannot be used for finite window removal.

                              5 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  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                              • Transaction support for PowerShell cmdlets

                                today when using powershell cmdlet the action is performed direct against the server, as example, if you want to create an application, add couple of deployment types and perform other small changes, you end up with lots of revisions (easily, 10). when you have lots of revisions, this start to impact the performance.

                                it would be nice if we can have the cmdlets transactional, in this case, you create the object and the changes does not apply to the database, you need to "save" the change.

                                on the application example, you could create the application, create the dt's, changes, etc.…

                                5 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  ·  1 comment  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                • Allow use if DeploymentID as identifier in Set-CMPackageDeployment and Set-CMSoftwareUpdateDeployment

                                  Set-CMPackageDeployment and Set-CMSoftwareUpdateDeployment do not allow DeploymentID as unique identifier. Instead you need to use e.g. programname and packageid.

                                  In the case of Set-CMSoftwareUpdateDeployment this requires DeploymentName which is not even possible to retrieve from Get-CMDeployment

                                  Please, allow DeploymentID as an option to identifying the deployment in these cmdlets.

                                  4 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  ·  0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
                                  • Remove the option to deleted the members from a collect when the collection is deleted.

                                    It seem odd that since you multi-select and deleted user / computers that you would need to have a prompt to delete the users / computers when deleting the collection.

                                    The process should be if you need to deleted the users / computers and the collection.
                                    - Multi-select and deleted computers. If there is a large number users / computers blocks deleted if number excesses High-Risk deployment settings.
                                    - Deleted the Collection
                                    - If the collection is limiting another collection. Then prompt if that collection should be deleted too.

                                    3 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  ·  0 comments  ·  Collections  ·  Flag idea as inappropriate…  ·  Admin →
                                    • Select specific WMI classes or Logfiles in SCCM Support Center

                                      It would be nice to have the ability to select specific WMI classes or Logfies easily within the SCCM Support Center. Right now i have to edit the config XML and sometimes the support center crashes. That would Help if you try to pull files or classes for specific Scenario from Clients and you dont Need all of them.

                                      2 votes
                                      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  ·  Tools  ·  Flag idea as inappropriate…  ·  Admin →
                                      • Change temporary unpack path of Support Center Viewer

                                        If i open a "Bundle" in Support Center Viewer all the data gets stored in:
                                        C:\Users\<USER>\AppData\Roaming\Microsoft\ConfigMgrSupportCenter.Common\Temporary

                                        It woul be nice to Change that path or to provide a path during the unpack procedure. Right now i have alsmost 8GB of data in that path and it seems to not clean up by itself.

                                        2 votes
                                        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  ·  Tools  ·  Flag idea as inappropriate…  ·  Admin →
                                        • Fix Support Center on running app deployment eval cycle remotely

                                          When Support Center runs App Deployment Evaluation cycle locally, it uses Schedule 121, which is OK. However, when it’s connected to remote machine, it uses Schedule 123, which was deprecated at some point.

                                          Future release of Support Center should always use schedule 121.

                                          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  ·  Tools  ·  Flag idea as inappropriate…  ·  Admin →
                                          ← Previous 1
                                          • Don't see your idea?

                                          Feedback and Knowledge Base