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.

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 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. Boundary Priority

    Please make available we can set a Priority on Boundary, for example:

    Standard Boundary ist a AD-Site and use DP1 and a Boundary with special IP Subnet for staging clients in the same AD-Site, use a override for use DP2 only.

    7 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  2. client issues in 1610

    We are facing issues with the new client in 1610. mainly it is very slow to load and returns errors at time. The service does not respond to restart calls. Finally, Sorting by status for installations does not work as expected.

    1 vote
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  3. SMS Agent Host Startup Type - Client Setting

    There should be an option in the Client Settings to select the Startup Type for the SMS Agent Host. It takes a couple minutes for the agent to start by default since it's set to Automatic (Delayed Start).

    While I think that this should remain the default, it should be an option in client settings to switch this to a regular Automatic startup type.

    1 vote
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  4. Limit Client Push Accounts by Collection

    To maintain consistency with Microsoft's Securing Privileged Access guidelines, an option to limit client push accounts to a specific collection would be ideal. This collection can further be limited to specific machines, specific domains, etc. For example, a client push account that is intended for Tier1 systems should not be used for Tier2 systems. By having the option to limit to a collection, a Tier1 client push account can only be used when performing client push on Tier1 systems. The same example applies for Tier0 versus Tier1 and Tier2.

    Reference: https://technet.microsoft.com/en-us/windows-server-docs/security/securing-privileged-access/securing-privileged-access-reference-material

    37 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  5. ACP functionality with Automatic Client Upgrade

    ACP functionality with Automatic Client Upgrade - it would be nice if the automatic client upgrade would utilize the deployment methods available to alternate content providers to reduce WAN impact

    12 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  6. Delegate Promote Pre-production Client

    In addition to the Modify and Read permissions on Update Packages class, add a third permission "Promote Pre-production Client" which can be delegated to a non-infra administrator.

    4 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  7. Option to throttle content to computers without a local DP at the site

    I love a way throttle content delivery to any computers that do not have a local DP at their site.

    I can setup client policies but if the computer moves from site to site, this doesn't work. As one site may have a local DP and the other does not.

    If there is a DP at the site, they will receive content quickly without consuming bandwidth. So there is no reason to throttle. However, if they're at a site without a local DP, we have it going to our main sccm server at our datacenter. The delivery can consume quiteā€¦

    1 vote
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  8. Add Site to "Import computer information" wizard

    It is recommended to import computers on the primary site where they should be assigned to, not the CAS, because in some scenarios that causes issues. All administrative tasks should be available from the CAS. It would be great to add the ability to the "Import computer information" wizard to select a primary site (similar to the Client Push wizard). That would then import the computer information remotely on the primary.

    4 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  9. When configuring cache size via client settings - cache cannot be deleted

    When using the new option in 1606 branch for configuring client cache size - the options to delete cache from the client's size is grayed out.
    either it's by design or not - it blocks the reason to use this feature as deleting cache is one of the most basic troubleshooting tasks for deployments and it is not possible to be done unless deploying a custom script...

    19 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    3 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  10. Include updated Windows Update Agent during client install

    There are well documented issues with issues when using older versions of the Windows Update Agent. The configmgr client install still just checks for the base level of the Windows Update client. The client install should include the most up to date windows update agent so that customers will not be required to deploying the updated agent after client install to resolve known scan and related issues.

    0 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  11. Certificate selection tool

    I think a simple certificate selection tool for clients would be really handy. I am thinking in exactly the same way as momcertimport.exe in SCOM where you can run the exe either as GUI or cmd line and choose a specific certificate to use.
    As we know, current certificate selection is not fool proof and can be very tricky when multiple certificates are installed on one device. A simple certificate picker or override tool would assist massively when dealing with HTTPS environments, particularly in DMZs. Numbers are often much smaller and we are dealing with the final 5% which canā€¦

    13 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  12. Retain users settings in Software Center. i.e. Business Hours, after client upgrade.

    When ever the client is upgraded our users have to reset their Business Hours in Software Center. This is extremely difficult in a 60000+ environment to get the communication out. Why can't the users settings in the client upgrade process be retained?

    85 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  13. change automatic agent upgrade behaviour

    currently using the automatic client upgrade process on servers causes the SCOM agent to be stopped ahead of the upgrade causing hundreds of SCOM alerts that then need closing or investigating. The option of "don't upgrade servers" still causes the SCOM agent to be stopped.

    Either provide the option not to stop the SCOM agent during client upgrade or honour the "don't upgrade servers" check before you stop the SCOM agent.

    7 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  14. 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.

    45 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  15. 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
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  16. Allow the Client Upgrade to be performed outside maintenance windows

    We would like the Client Upgrade feature to allow the client to be upgraded outside of maintenance windows but also give the option to only install when no user is logged in, like deploying Applications allow.

    270 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    under review  ·  14 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  17. More criteria for client certificate selection

    Currently the selection criteria when more than one certificate is available are limited to the options ā€œClient authentication capabilityā€, ā€œCertificate Subject contains stringā€, ā€œCertificate Subject or SAN includes attributeā€. This really limits the usability of the feature.
    It would be great if there are additional selection criteria like ā€œIssuerā€ or ā€œCertificate Templateā€.

    44 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  18. Disable 24hr cache hold

    Add a checkbox in client settings to disable the 24hr hold on cache packages or set soft limit till hdd reaches x space.

    2 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  19. Client Upgrade via Software Updates

    Each branch update should offer an MSP for the CM client or offer the client as a software update so that we can more easily stay current with the latest client. When we had CUs in software updates we stayed current all the time. But these full MSI installs for the client slow us down considerably.

    67 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    4 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  20. 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ā€¦

    106 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  7 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base