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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Make automatic client upgrade more intelligent to not break other running installations

    Right now, the automatic Client upgrade scheduled Task is not aware of any running installations. So if appenforce.log shows a running Installation and at the same time the randomly timed scheduled tasks kicks in, the Installation cannot finish without error and will randomly leave the Installation or the SCCM Client itself in a unhealthy state. A reinstallation is the only way out.

    Repro steps
    - Activate automatic Client Upgrade in Hierarchy settings
    - Exclude some test clients from automatic client upgrade
    - Create an Application with a deploymenttype using a custom script
    - As the script, use a batch fileā€¦

    193 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    5 comments  ·  Client Deployment  ·  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ā€¦

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

    82 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  1 comment  ·  Client Deployment  ·  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.

    48 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 →
  5. 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

    35 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  4 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  6. 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
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  1 comment  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  7. WMI Fix integrated with SCCM Console

    WMI Fix integrated with SCCM Console and improve client installation description error.

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

    12 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 →
  9. 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
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  0 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  10. 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 →
  11. 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
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  0 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base