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. The ability to tell an SCCM client to IGNORE specific NICS for site determination or SCCM Client communications

    The ability to tell an SCCM client to IGNORE specific NICS for site determination or SCCM Client communications.

    We have a number of clients that are multi-homed, the SCCM client is often choosing interface that cannot communication with the SCCM infrastructure to determine site membership.

    Our clusters fall into this category. 'secure web application servers' that have a "Client Network", "Admin Network", "Backup Network" and "Management Network" connections.

    May something similar to the NOSMS file, that will tell the client to not use specific interfaces but continue to inventory, configure, etc.

    113 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  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  2. More Intelligent Client Cache

    With SCCM 2012 we got the single instance store on the back end which reduces the need for storage significantly on the server side but on the client side there's no optimization whatsoever.
    If you for example have 2 applications or deployment types which are using the same or almost the same content they are downloaded both separately. This has a negatively impact on the disk space you need to reserve for the client cache but also on the bandwidth used to download almost twice the same content. I believe this can be done better.
    Many folks had to configureā€¦

    95 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  4 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  3. Remove Custom Discovery Data

    When creating custom discovery data using the smsresgen class there is no way to remove this from the discovery related tables in ConfigMgr. Since there is a supported way to add this data, there should be a supported way to remove it. This is necessary as a rollback option, to return ConfigMgr to its default state, before the custom discovery data was added.

    63 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  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  4. Wake-up proxy support for 802.1X networks

    In our enterprise we have quite a few locations where 802.1X is impelemented, e.g. networks port-based network access control and/or VLANs. Some locations even use DHCP snooping.

    We would like to implement SCCMs wake-up proxy feature in these locations but it is not currently supported. Also, network administrators are concerned about the IP-to-MAC mapping (MAC flapping) feature used in wake-up proxy.

    Please provide us with wake-up proxy support that will work on any type of network.

    54 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  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  5. AD Group Discovery should not write DDR for invalid records

    When System Discovery finds an object that seems invalid, currently it won`t be imported (which is good).
    ERROR: System <systemname> is a unsupported operating system, unsupported version, or malformed AD entry. Reported system type is: ().
    However if the same object has an AD Group Membership and AD Group Discovery finds it, it won't check if it is valid, but write the DDR and create the object record in SCCM DB.

    Please change AD Group Discovery so it validates new objects too.

    35 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  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  6. Full support for ECC Certificates

    Machines with an EEC client certificate can connect to the DP to download the content and install the agent but the client never registers with the site.

    once i suspected the ECC certs I was able to find thread on technet which confirms the same issue I was seeing
    https://social.technet.microsoft.com/Forums/en-US/cc9ec0ff-5998-4225-9ce1-2c7b5fe5677d/sccm-and-ecc-certificates-not-supported?forum=ConfigMgrDeployment

    32 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  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  7. Client Push by OU

    Having the ability to use Client Push more granularly would be awesome. We have about 6 domains, and multiple OUs are defined in System Discovery, yet I don't want Client Push enabled on them all, so it is currently disabled. Maybe having an option in the Discovery area, for an OU that is added (right where it says "Search AD Groups and Search Child containers") that enabled Client Push on that discovered OU. Or More granular settings on Client Push itself, maybe a small GUI attached to it

    28 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  4 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  8. Combine ClientPatch and Patch property

    The outdated ClientPatch folder in the 'Configuration Manager Client Package' is unsupported, however it is a great combination for retrieving from a local DP (leveraging the /mp-option to retrieve content based on boundaries) and getting the patch installed.
    Considering that CCMEval also reruns with the last command-line used the availability of a ConfigMgr patch is vital (otherwise a 1635 error is generated if the new installation attempt can't access the MSP-file) perhaps the supported Patch-property and the ClientPatch-concept can be combined into a new supported way of deploying patches?

    The scenario would be as follows;
    CCMSetup detects that there isā€¦

    27 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  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  9. Include seperate client push settings for workstations and servers

    We would like the ability to have seperate client push settings for Workstations vs Servers, specifically the ability to have seperate installation properties.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    4 comments  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  10. Support Mac OS 11

    Hello

    can you please support Mac OS 11.

    Thanks.

    4 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  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  11. Ability to Control/Limit Wake-Up Proxy Candidates

    The nomination for Wake-Up proxies is fully automated.
    From testing, up to three devices per subnet will remain switched on (or in some cases start back up if a user shuts them down). This is not appropriate in cases where a small office may contain only 4 or 5 machines.
    Additionally, if a server is located at a particular site (DP for example), this should be the sole wake up candidate, due to the fact that the likelihood of that device shutting down is minimal.
    I propose changes to achieve the following:
    1) The ability to designate specific Wake-Up proxiesā€¦

    4 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  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  12. ccmeval fails to correct missing or renamed ccmexec.exe

    If the ccmexec.exe is missing (ie Malware) the ccmeval is not able to remediate and it does not trigger a repair of the SMS Agent Host client

    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  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  13. Sccm reads windows security logs at startup

    The sccm client startup process is very heavy. On our machines we have a very demanding security baseline which gives us a huge windows security eventlog. Reading out this eventlog alone takes over 30 seconds at 25% CPU which makes the startup process of the computers even slower than it is. As we understand it SCCM reads pretty much the entire security log every time the service is started. Even if it's started twice in 30 minutes for whatever reason. We aren't sure what the point is of reading out 100MB of security logs, but it seems a waste. We'dā€¦

    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  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →

    Thank you for your feedback. Do you have user device affinity enabled in your environment? If you do, is it configured to automatically determine affinity? Changing user device affinity configuration may reduce this overhead.

    For more information, see: https://docs.microsoft.com/en-us/mem/configmgr/apps/deploy-use/link-users-and-devices-with-user-device-affinity

    We will consider looking into ways to improve this in the future.

  14. Exclude certain operating systems from discovery

    It would be great if we could exclude certain OS's from discovery. I have over 5500 machines in my DB that I couldn't care less about but they reside in an OU where I have machines I do care about.

    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  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  15. ccmsetup <specific/latest> client

    Create a new Parameter for the ccmsetup to use the latest Client Version. Currently there is no Opportunity to install the newest Client Version by Script. So in Cases of Troubleshooting the Client will be installed/updated two times within an short period.

    2 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  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  16. Show Client Version in HELP-ABOUT from ConfigMgr console

    While working with boot images, I need to click UPDATE DISTRIBUTION POINTS and see if the client within the boot image is the same as the client on the site server. It would be nice if I can see the current (latest) ConfigMgr agent shown in HELP-ABOUT from ConfigMgr console as a all-in-one screen so I would spare some time checking and updating the boot images

    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  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →

    Updating status to noted.

    Thanks for your feedback.

    Not sure what I’m missing here…
    The ‘About Microsoft Endpoint Configuration Manager’ shows ‘Site version:5.0.9012.1000’ – that’s an example from our 2006 release. The same is shown in the Boot Images view, the Client version column.

    The update Distribution Points wizard shows the current ADK version, the current production client version and in the table below the reload option we show the OS version of the boot image and the version of the client binaries.

    Could you let me what I’m missing? The information present in the wizard covers everything you’d need to know – in my opinion anyway.

    Thanks

  17. Overview pane to monitor automatic client upgrades to new service pack

    With R2SP1 automatic client upgrades will now function for the first time in an R2 environment.

    It would be nice if that deployment wasn't hidden though so we could actually see the progress of the clients being upgraded.

    1 vote
    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  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  18. Merge two resources with the same MAC Address

    If I import a new computer using its MAC Address but later I install manually the client in the actual computer, two resources with the same name end up in the SCCM Database.
    An option to make the default action merging both resources or just associating the client DDR to the manual import.

    0 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  ·  Client deployment and discovery  ·  Flag idea as inappropriateā€¦  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base