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. Synchronize additional tables with the Data Warehouse Service point

    In the 1612 technical preview, the Data Warehouse Service point was introduced, and at that time it included the ability to specify additional tables for synchronization. This capability is outlined in the release notes (https://docs.microsoft.com/en-us/sccm/core/get-started/capabilities-in-technical-preview-1612).

    The latest release of ConfigMgr (1710 as of this posting) does not include this capability.

    Re-introducing this capability would expand the use cases for the Data Warehouse Service point. Many customers have custom hardware inventory classes that are not included by default with the existing feature. There are also native tables, such as task sequence execution status, that would be helpful for trendā€¦

    27 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 →
  2. When running the "Modify site database configuration" option, do a sql server collation test

    When running the "Modify site database configuration" option, do a sql server collation test to the remote SQL servers . We had the case that we overlooked the CP1CIAS requirements as the DB admin just configured CI_AS. When not the right Server Collation Instance , just stop the migration

    1 vote
    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 →
  3. Allow Slash (/) Character in Organizational Units for Group Discovery

    When Group Discovery for the whole Domain is activated and there are Organizational Units containing the Slash Character in the Name, you get "failed to bind to Container" Errors in SCCM.

    As long a Slash is an allowed character in LDAP, SCCM should be able to process these OUs correctly.

    6 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 →
  4. Upgrade SCCM directly to rollup version

    Be able to upgrade SCCM directly to a rollup version or hotfix versions. Not everyone upgrades SCCM the moment a new version is released and by the time we have tested and are ready to upgrade there is often a rollup or hotfix available. Due to change management procedures, we are forced to upgrade to a version that has potential known issues before we can start a new change process to upgrade again to the update version. Being able to upgrade direct to the rollups would prevent installing a broken version for weeks prior to upgrading again.

    91 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    6 comments  ·  Site deployment and infrastructure  ·  Flag idea as inappropriateā€¦  ·  Admin →
  5. Add support for Disaster Recovery into SCCM

    SCCM should have built-in functionality for the setup, automation and triggering of a disaster recovery solution. Typically this would involve additional servers operating at a different physical location with replication of data between the active site and the DR site. Upon a DR event, you would transfer or seize functionality at the DR site to transfer control to the DR server(s). SQL Server has multiple DR tools available (mirroring, failover clustering, transaction replication, log shipping, etc.) so there is no need to reinvent that wheel, but SCCM should give similar functionality.

    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 →
  6. Component status should be more stateful (status should automatically clear once an issue has resolved itself)

    I often repeat the following actions:

    • Verify Component Status (Monitoring - System Status - Component Status)
    • Open any Component with Status Warning or Error.
    • Verify the Warning or Error is Solved
    • Reset All Counts for this Component.

    A Typical example: Restart the Site Server.
    All Management Points complain that the Site Server is unavailable.
    But in they also report the System is Online again.

    MP File Dispatch Manager running on the management point "mp.company.com" cannot connect to site server "SiteServer.company.com". The operating system reported error 53: The network path was not found.

    Component Status Summarizer detected that the availability ofā€¦

    0 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 →
  7. "Scale-Out" Primary Server

    It would be really great if there was an easy way to decouple components that run on one large Primary Site Server and transfer them on to a number of smaller machines and be able to migrate those roles across machines quickly (similarly to how this is done in SCOM with Management Servers and Resource Pools). That would allow the following:
    1. Simplify Maintenance - currently, every time we need to patch SCCM Primary Site Server, we need to agree upon the outage window with all the teams that rely on SCCM. If we could move the workload, we'd beā€¦

    4 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 →
  8. Allow unicode passwords in ConfigMgr

    With Windows OS you can use unicode characters in passwords. Unfortunately, ConfigMgr doesn't support unicode passwords. If you have unicode characters in your password, ConfigMgr shows a message that password is not correct.

    2 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 →
  9. SCCM CB recovery Options for Hierarchy if a single PS fails

    beginning with SCCM CB (Console servicing model), there are 2 Options if a single PS failed during a hierarchy update (e.g. from SCCM 1702 to 1710) if the CAS is already on a newer version:
    1: Recover the whole hierarchy to a previous version
    2: Setup/Reinstall the failed PS as new Child Site
    Option 1 is, if you have an infrastructure with more then 2 Sites (and CAS), not really an option to consider about. Option 2 forces you to setup all prior installed and configured Site Systems again (DP/Client etc.)

    Possible options for implementation of a single PS ā€œrecovery/upgradeā€ā€¦

    39 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 →
  10. Add Database Checking to pre-req check

    It would be great if functionality were added to the pre-req check to include an option to do some of the features of the testdbupgrade option of setup. For example, adding an option to check for foreign key constraint issues or other problems that would prevent an upgrade would be a great addition and would prevent issues where the upgrade fails in the middle of the DB upgrade portion of setup.

    3 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 →
  11. Add Support for MSA/gMSA for Standard Roles

    I would like the ability to assign managed service accounts or group managed service accounts to the standard roles for SCCM (i.e. Network Access Account, Domain Join account, Client Push account, etc.) so that those accounts can be secured without the need for knowing or managing the password.

    185 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 →
  12. 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  ·  Site deployment and 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.

  13. Integrate an Distribution Sender Interpreter

    Please integrate an Log Interpreter for easier Log Control
    Such as http://www.danrichings.com/?page_id=12 for Sender Log.

    This makes the Life for Package Distribution and Server Control easier in an Enterprise Enviroment.

    3 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 →
  14. Removes the Inboxes engine and replace by a web service

    Re building this inner process would improve the general performances and ensure SCCM long term use against new rival softwares.

    19 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 →
  15. Have templates for Windows Server Roles that Site Systems use when deploying

    When installing site systems like SUP I want to have specified an template for how Windows Server should be configured like IIS, WSUS Application Pool etc. in addition to installing the WinSrv Roles. This can bed slightly different from customer to customer and would make it easier for them to deploy new Site Systems with a consistency. Stability would go up and troubleshooting would be easier. Thinking about all Site System roles, not only SUP.

    1 vote
    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 →
  16. Make it easier to use HTTPS DP as a pull DP source

    It should be much easier to use HTTPS DP as a pull DP source. Now you need to have a special script to define HTTPS DP as source (= complicated) and pull DP needs to have a ConfigMgr client (= licensing issue). I see increasing number of customers who want to use HTTPS in all their internal IIS servers, including ConfigMgr.

    11 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 →
  17. Document SCCM site from Console

    We do a lot of projects and due diligence reports.
    It would be nice to be able to document the site from the SCCM console - it can be written to a word-pad document and later just be saved to a word format

    1 vote
    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 →
  18. Allow clients under branch offices to get proxy MP information from assigned secondary site

    By default (that am seeing) , clients under branch offices will not get proxy management info unless you add the boundaries of branches into boundary group with mp defined .
    Lets take ex: I have lot of branch offices in location that has secondary site with MP,DP,SUP (a.ak. proxy MP) .So when i create boundary group for these branch office boundaries ,i do not specific the MP info in site system tab ,because i do not want my branch office clients to download the content from sec site which is DP and also MP. In this case ,i have notā€¦

    1 vote
    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 →
  19. DB gets into single user mode

    Where certain database settings got changed on ConfigMgr database.
    We should have a bug to have a prereq check to give error that ConfigMgr admin to validate the database settings before upgrade.

    1 vote
    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 →
  20. multisubnetfailoer

    Allow Configuration Manager to support the site DB with multisubnetfailover option enabled.

    4 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 →
1 2 5 7 9 13 14
  • Don't see your idea?

Feedback and Knowledge Base