Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice - Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more

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 Microsoft Endpoint 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 Microsoft Endpoint Configuration Manager feedback site is moderated and is a voluntary participation-based project. Please send only feature suggestions and ideas to improve 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.


  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Reduce the amount of time needed perform a CM upgrade

    For most companies, Configuration Manager is becoming a mission critical service the requires less and less downtime. Upgrading large environments/DBs can take up to 5 hours for the CAS, and 4-5 hours for primary sites. Also, most customers want to get the latest hotfixes installed right after performing an upgrade. In some cases, the hotfixes take just a long to complete as the original upgrade. Overall, this can require long outages (sometimes 2 days) to get current.

    Potential Solutions:

    1. The ability to upgrade directly to the latest hotfix as noted here:
      https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/33166225-upgrade-sccm-directly-to-rollup-version

    2. Reduce the time needed to regenerate DRS sprocsā€¦

    66 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
    completed  ·  djam responded

    We have made optimizations during SCCM upgrade to not do unnecessary SQL tasks. We are not considering upgrade directly to the latest hotfix.

  2. Cloud Management Gateway (as CSP)

    With 1610, the Cloud Management Gateway feature arrived. Although it's a Pre-Release feature, as Cloud Solution Provider we're UNABLE to use/implement this. And so are our customers...!

    When you try to set this up from the ConfigMgr console, a prerequisite is the Azure Management Certificate, which can't be configured as CSP-tenant because this needs the Classic Azure Portal (ASM). This is unacceptable for us, as CSP, as we would have to instruct our customers to get an Azure Subscription separately.

    https://blogs.msdn.microsoft.com/cie/2016/11/28/azure-management-certificates-and-publishing-setting-file-with-csp-subscriptions/

    732 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    38 comments  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
    completed  ·  djam responded

    We have shipped this functionality in #configmgr 2010.

  3. Updates and Servicing does not clean up EasySetupPayload folder once a new version is installed.

    As the final step in Updates and Servicing, remove previous installer files for current branch builds and superseded hotfixes from %ProgramFiles%\Microsoft Configuration Manager\EasySetupPayload or add and enable a scheduled cleanup script/

    Also there are now 3 locations with the full installation source files:
    %ProgramFiles%\Microsoft Configuration Manager\cd.latest
    %ProgramFiles%\Microsoft Configuration Manager\EasySetupPayload
    %ProgramFiles%\Microsoft Configuration Manager\CMUStaging

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    completed  ·  1 comment  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
  4. Download only applicable ConfigMgr upgrade packages with ServiceConnectionTool.exe

    If you have deployed offline Service Connection Point, ServiceConnectionTool.exe now (in ConfigMgr 1511 - 1606) downloads ALL published ConfigMgr update packages when you use -connect parameter. E.g. if your site only requires post 1606 hotfix, ServiceConnectionTool.exe downloads 1602, 1606 installation packages although they are installed! Currently it will download over 7 GB of updates, when you just need about 25 MB update package. This is just waste of time, network traffic & disk space.

    Please improve ServiceConnectionTool.exe, so it would only download the update packages that are applicable for the current installation.

    40 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    5 comments  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
    completed  ·  djam responded

    This should be fixed now. Should only download the latest.

  5. Have custom component thresholds values not reset every time we update to a new build

    We've set some custom values for some component thresholds, but every time we update to a new build of sccm, those custom values are reseted to the original by default values.

    So we have to go ahead and change them back everytime, so it would be appreciated if the upgrade process would not override them.

    0 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    completed  ·  2 comments  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
  6. RBA on the Folder level

    Currently Administrators have the ability to set Role Based Access to Collections but we do not have the ability to block access to specific folders. Currently in my environment we have many different departmental administrators who need to manage only their machines and their collections. each time we add collections we then need to grant them access. if the Role Based Administration gave the ability to grant access on the folder level it would reduce the complexity for area's that have a setup similar to mine.

    I have attached a screenshot of how my setup looks.

    679 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    29 comments  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
  7. Site Server High Availability or Clustering

    Configuration Manager is becoming more mission critical every day. The ability to Cluster the Site Server role (Inboxes & SMS Provider) is more and more important as that is the single point of failure for a Primary Site.

    If the Site Server role goes down the Primary Site is down no matter how many Management Points or SMS Provider etc. exist.

    If we could Cluster the Site Server or at least have 2 systems share that role for High Availability then this would no longer be an issue.

    Even though we can designate multiple SMS Providers, if the site systemā€¦

    439 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    16 comments  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
    completed  ·  djam responded

    We have now added hierarchy support with #sccm 1810. There is still some planned work outstanding (represented by UV items in the comments); but the core work for this is now complete in #sccm 1810.

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

    273 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    18 comments  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
    completed  ·  djam responded

    I will mark this completed for now to raise awareness. This feature is in 1906 and 1910, but hidden. If your company wants to try it, and you have a premier support agreement, have your pfe reach out to the product team and we will partner with you on it.

  9. When viewing Site Status, the disk size and free space columns don't sort correctly

    If you view the columns for Total, Free and Free disk (%) in the Site Status under monitoring they appear to sort alphabetically rather than numerically. e.g. 1,12,19,2,27,276,28,6,78 instead of 1,2,6,12,19,27,28,78,276

    20 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    7 comments  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
  10. Better control of settings like fallback of SUP site, Bandwith limitation, replication priorities of metadata

    better control weather I want a site to fallback to primary or not.
    real bandwith limitation instead of current posibility. Control priority of metadata

    35 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    completed  ·  1 comment  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
  11. site restore

    Add a way to perform a site restore to a system with a different name (but keep the same site code). In the event of a Datacenter Move, often times we are not allowed to retain the same system name (location based naming) and we end up having to stand up and entire new infrastructure and migrate.

    While this is doable, it's tedious work and when operating in a Hybrid scenario with Intune, it means that we have to re-enroll the Intune managed clients to a new management authority. It's a whole lot of pain.

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
    completed  ·  djam responded

    This can be done in #SCCM 1806 with Site Server High Availability – by bring up a new machine with a new name, and making it the passive site server. Then you can fail over to it (making it active), and you can get rid of the original server.

  12. 8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
    completed  ·  djam responded

    We have tested, and now support MBAM with ConfigMgr 1802+

  13. Make the the BranchCache experience more consistent

    Currently, BranchCache can be enabled via client settings, but still has to be enabled on a 'Per Deployment' basis. Applications have it turned on by default - Pkg/Progs do not. I would like to see a similar approach to Peer Cache i.e if enabled in the Client Settings then it should be enabled for all deployments - or at least set to "on" by default across all deployment types. Also, and option to enable BranchCache across all DPs would be useful instead of requiring a checkbox for each one.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    completed  ·  0 comments  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
  14. Support V3 and newer certificate templates for HTTPS mode

    Hi,

    PKI- Make V3 Template compatible with SCCM Current Branch.

    88 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    19 comments  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
    completed  ·  djam responded

    This is completed in #ConfigMgr 1710 for most all client communications. Some of the server<→server coms (i.e. app catalog) will be completed in the next release.

  15. Support for renaming a site server

    Support for renaming a site server. Our stand-alone primary site server is the last server named by our old server naming conventions.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    completed  ·  4 comments  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
  16. Download only the latest Branch \ upgrade of ConfigMgr

    both in online and offline modes of the Service Connection Point, when installing 1511 and then get the updates, ConfigMgr downloads 1602, 1602 hotfixes and 1606 EasySetups (and all of their prerequisites) when in 99% of the cases - we only need the latest release.
    this causes a lot of time waiting and bandwidth usage for nothing and it will probably get worse as there will be more future release.
    we want an option to choose what release to download instead of download them all

    28 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
    completed  ·  djam responded

    This is fixed in ConfigMgr 1702. Beginning with that build, it will more intelligently only download newest updates. It will also do a better job of cleaning up old updates.

  17. Direct Upgrade from SCCM 2012R2 SP1 to 1606 or higher (not via 1511 and then 1606)

    Right now we're having an environment with a CAS and two PRI with 165,000 clients. The hardware is "old" and has to be replaced.
    Everything is running on SCCM 2012 R2 SP1, SQL 2012 and windows server 2008 R2. Now we're planning an upgrade to SCCM 1606 or higher, SQL 2016 and windows server 2016 on different hardware. So far we found some TechNet pages telling us that there are issues with SCCM 1511 and SQL 2016, but SCCM 1606 and SQL 2016 ought to work (There is right now no information about the supportability of windows server 2016 withā€¦

    9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
    completed  ·  djam responded

    ConfigMgr 1606 was a baseline build. There will be future baseline builds from time to time.

  18. Support SQL Always On AG Asynchronous-commit

    Configuration Manager Current Branch (1602) Supports SQL Always On Availability Groups, however it only in a Synchronous-commit replicas.

    From TechNet:
    Asynchronous-commit mode. This availability mode is a disaster-recovery solution that works well when the availability replicas are distributed over considerable distances.

    Synchronous-commit mode. This availability mode emphasizes high availability and data protection over performance, at the cost of increased transaction latency. A given availability group can support up to three synchronous-commit availability replicas, including the current primary replica.

    This means that Configuration Manager can only support 3 secondary replicas in a SQL AO AG and they need to be inā€¦

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
    completed  ·  djam responded

    ConfigMgr now works w/ Assync commit.

  19. automate testdbupgrade

    This may be possible, but I've found no documentation on it. Is it possible to make the testdbupgrade process unattended. I've got 8 primary sites and it takes a considerable amount of time backingup/restoring/testdbupgrade. in preparation for a site upgrade. I'd like to automate it all. The sql part is fine.

    Can testdbupgrade be specified inside the the configmgrautosave.ini ?
    so it could work with a command like this:
    setupwpf.exe /script *configmgrautosave.ini /nouserinput

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
    completed  ·  djam responded

    TestDBUpgrade can be specified on the command line; and is definitely automatable. During our internal testing, we loop through many databases testing their upgrade… and it’s all silent/automated.

  20. updates and servicing

    The Administration > Cloud Services > Updates and Servicing deserves it's own blade in the console. Given that this is how Current Branch updates are delivered, this is an important piece and shouldn't be buried in the UI.

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base