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. Ability to automatically install Windows 10 ADK releases (or rollback or apply hotfix) via Updates and Servicing.

    The windows 10 adk has changed a few times since the original release of Windows 10, there have been two major releases and one hotfix to fix issues with the second release, as a consequence of that many people got jittery about upgrading to ADK 10 1511.

    How are we going to deal with this in a good way, a really good way. Prior to this we didn't have to upgrade our boot images every 6 months or so.

    Here's the suggestion:-

    1. When we update from 1602 to 1607 (or whatever) to support the next generation of Windows, it

    833 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    15 comments  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
    Noted  ·  sangeev responded

    Updated to Noted. We’ve been discussing the same in our planning meetings.

    Thanks,
    BobMN on behalf of SangeeV for SCCM OS Deployment

  2. Improve automatic SQL configuration, tuning, and maintenance of the SCCM DB & SQL Server

    Current architecture around SCCM’s management of SQL configuration and maintenance is old and hard to use. It requires a lot of manual oversight, and manual SQL tasks. And the default SQL settings created by SCCM are non-optimal. SQL is a powerful beast. Rethink ways SCCM can use it better, and keep it more optimally tuned and configured. Rethink how to run maintenance and backup tasks without downtime or impact to the production sites and deployments (this especially becomes more important with features like Conditional Access, that can never really have downtime.)

    150 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  5 comments  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  3. Use SQL Backup with Compression for the backup task

    With CM 1511, SMS Backup task enabled by default. And that does a volume shadow copy of the DB which means full-sized files. For my tiny lab that means I'm backing up 8 GB alone.

    For production it'll mean 850GB per primary site. Under CM12 when we backup just SQL using compression, it's just 160GB per primary site.

    Please allow an option to just invoke a database backup instead so that compression can be used and I don't need to go order terabytes of data just for backups.

    Also the current backup just erases the last backup. But in a…

    126 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  4. Have updates automatically handle MP replicas

    It's a real pain to have to tear down and rebuild the MP replicas every time I want to install a servicing update. It would be great to have the update process automatically save the replica state, point the MPs at the primary DB, tear down the MP replicas, do the update and then put it all back.

    125 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add a check box to Maintenance Tasks to disable all temporariliy

    When doing an upgrade to SCCM, it has been recommended to disable some, or even all of the site maintenance tasks. (per the upgrade checklist) Would be awesome to have a box on the Maintenance Tasks screen to temporarily disable ALL tasks while the upgrade is being performed. (as opposed to manually disabling all of them) An "upgrade/maintenance mode" box essentially!

    59 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  6 comments  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  6. suport Azure PaaS for SQL DB

    Support ConfigMgr to be installed on Azure VM IaaS using SQL Paas as DB.

    42 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  3 comments  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  7. Decouple site component backup service from database server

    Configuration Manager currently installs binaries and configures the SQL backup site component service on the database server, running under LocalSystem authority. Many environments have separate groups that host and manage the SQL Server enterprise environment, and do not allow for services or additional software to be installed on them, creating unnecessary conflict and drama when SCCM needs to be installed. SQL Server is a networked service, there shouldn't be a reason to install software on the database server running under a privileged account in order to leverage backup routines.

    34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add preflight checks and improve documentation for the “Modify SQL Server configuration” option

    1.) When running the SCCM Setup Wizard and choosing “Modify SQL Server configuration” there does not appear to be an adequate preflight check to ensure Config Manager is running with full administrative rights to A) operating systems, B) SQL instances and C) Config Manager itself. These permissions are (obviously) critical to a SQL configuration change. In enterprise environments, setup.exe should be reaching out to check rights to all the things it needs to modify (file system, registry, certificates, etc.) before it executes the changes. Partial modification of the configuration has catastrophic results.

    2.) Execution of the SQL configuration change does…

    23 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  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  9. Multiple Primary Site Servers for Migration of Host Operating System

    Have the ability to add a second Primary Site Server to an environment running as a standalone site to allow migration from an older Operating System to the latest version e.g. Migrate your 2012 R2 SCCM server from 2008 R2 to 2012 R2 by adding a second primary site server, and allowing settings, data etc. to synchronise. Then retire the old 2008 R2 server.

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  3 comments  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  10. better admin experience for troubleshooting site replication

    @JasonSandys: "When it works, it works fine. When it breaks, God help you cause no one else can."

    Add your comments on how we can make this better.

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  3 comments  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  11. Ability to upgrade multiple CM07 secondaries to CM12 distribution points

    CM12 is able to migrate only one secondary at a time.

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  12. Improve the process for using certificates within ConfigMgr

    Setting up and managing the certificates for MPs, DPs and boot media is not straight forward. Could you improve the certificate management process to reduce the complexity and overhead in managing it. So automation with internal CAs for automatic certificate issuing would be good.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  2 comments  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  13. When running the "Modify site database configuration" option, allow support for keeping SQL servername the same

    When going through the process of changing the configuration for the site database (in order to move it to a new SQL server), if you are keeping your SQL server name the same, the wizard will not allow you to input the same SQL server name as the old. We want to get rid of our SQL 2008 R2 servers running on Windows 2008 R2 and replace with Server 2016 and SQL 2016, but also keep the same hostname for the new server. Our only option since the wizard doesn't support this scenario is to do a backup and restore.

    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  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  14. Reduce the number delta mismatch BADMIFS Generated

    We get about 1000 deltamismatch BADMIFs generated each day.

    Here is the case of sccm client Inventoryagent.log says successfully sent but the ccmessaging.log shows the upload failed.
    Why can’t the client inventory agent act on the status back from ccmmessaginglog and if the upload of the inventory fails, don’t increment the delta number.
    This would greatly reduce the number of deltamismatch files generated each day and improvement keeping the inventory up to date without having to force a full inventory sync for this case.

    Here are the details:

    Dataldr.log for computer: CHOSIJ1-L2

    Thread: 6108 will use GUID GUID:c28fa179-d722-4692-be69-a71f5a81e75c SMSINVENTORY

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  15. Service accounts should be domain aware to prevent account lockouts

    Service accounts should be domain aware so that they do not attempt to authenticate against the wrong domain to lock out service accounts with the same username but on another domain.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  16. Upgrade logging improvements

    Upgrade needs to have better logging - for example during an upgrade, the spimportinventory stored procedure was failing on a merge with SQL error 8672:
    The MERGE statement attempted to UPDATE or DELETE the same row more than once. This happens when a target row matches more than one source row.

    Tracking this down was difficult because of the MERGE statement - if each row were being processed separately, the specific problem data could be called out when an error occurs.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  17. Check if Cloud Service name is valid during Cloud Proxy Wizard

    When deploying the new Cloud Proxy Service role in SCCM 1606, the user is asked to provide a Cloud Service Name. However, the UX does not explain that this is needs to be globally unique in all of Azure. I chose the name of 'SCCMCloud' turns out someone else already got that one though, and so the wizard completes and then fails in provisioning.

    This is sloppy. The UX should include instructions for the end-user to validate their name first (which can be done in Azure -> Cloud Service -> New, you're able to test various names until you find…

    5 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  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  18. Show Last Backup Time of Site in Console (SQL / Site Maintenance)

    It would be really useful to have the Last Backup Time of the SQL database and successful site maintenance task listed somewhere against each site. In addition, being able to right-click on a site and selecting "see backup log" would be useful (displaying the smsbkup.log or corresponding status messages for the SMSSITEBACKUP component via the console). This would make checking for successful backups much simpler for admins.

    So far the only screen I can see this being useful on is under Admin > Hierarchy Configuration > Sites, but it obviously fits better under Monitoring. Maybe a new node…

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  19. prerequisite

    If prerequisite checker fails with a warning there should be an option to continue with the upgrade anyway.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →
  20. Do not allow "SMS" as Site Code Name

    I found some customers which has "SMS" as name of SCCM site. This make a lot of problems with normal management. This name should also be make as do not allowed (wizard blocks also other names). And if already named, it should allow one time change.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →

    We do document this, and this has been the case since at least SMS 2003.

    See:
    https://support.microsoft.com/en-us/help/279868/reserved-site-code-names-in-sms-2003-and-configuration-manager
    https://docs.microsoft.com/en-us/sccm/core/servers/deploy/install/prepare-to-install-sites

    I’ve also confirmed that Setup disallows you from using the several “reserved” site code names and has done so since at least 2012 SP2.

    Was unattended setup used? That’s the only way I can think of that may have bypassed this validation.

  • Don't see your idea?

Feedback and Knowledge Base