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

    280 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 →
  2. 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…

    192 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 →
  3. 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…

    119 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  8 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  4. Change target computer mapping for state migrations (USMT)

    Please make it possible to change the target computer when using state migration points as a means of transferring user data to one pc to another.
    The scenario would allow the backup (scanstate) of the old pc data, utilizing all positive aspects of SMP (centralized, encrypted, storage based on boundaries). IT could then later set target computer, which may not be known at the time the data gets saved.
    Ideally this should be possible in the admin console by “editing” the state item to map to a new computer, just after it has already been created. “Late mapping” so to…

    105 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. 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 →
  6. Allow Users to defer installation until some date/time during Enforcement Grace Period

    When users receive notification of upcoming required deployment, allow users a 4th option to defer install date to be sometime during grace period. This could be a date input field with a drop down calendar. Available dates should be between deadline and end of grace period.

    The notification would have 4 options:
    1. Install Right Now
    2. Install After Business Hours
    3. Defer Install on a specific date during grace period <-- This being new
    4. Snooze notification

    Additionally, when notification appears for deferred install date...user can choose a new deferred install date as long as the user is within…

    82 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. 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.

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

    72 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. Force Client Deployment on metered network

    We have several users who are ALWAYS on metered networks and will never get client updates.

    The client deployment currently does not honour the option "Client Setting - Specify how clients communicate on metered network connections".

    We need an option to override it for manual client deployment / update as well. (Force install checkbox doesn't work)

    Setting the connection to "not metered" in Windows 8.1/10 doesn't work when a 3rd party connection software is used and doesn't work at all for TCT Mobile LTE sticks so this is not a solution.

    69 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Client Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Auto Client Upgrade – possibility to use default boundary/fallback DPs and ignore maintenance Windows

    The auto client Upgrade would be a nice feature if the admin would have more possibilities to configure it. Actually the feature can’t be used for clients which has no matching boundary or has got a maintenance window. It is not possible to use the feature for the client deployment for all clients in the environment if the fallback option or a maintenance window is used. So it would be helpful for the client agent update process, to implement two additional features.

    - Allow clients to use distribution points from default site boundary group
    - Ignore Maintenance windows and force…

    59 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 →
  11. Improve Client Upgrade Mechanism

    There is SCCM CB 1806 (5.0.8692.1509) with the update "kb4462978" in the console installed.
    When using automatic upgrade and package deployment to provide CM client version upgrades,
    From the distribution point, although "client.msi" can be acquired, if "configmgr 1806-client-kb4462978-x64.msp" can not be acquired for some reason, a scenario occurs that results in "5.00.8698.1008" version did.
    If the MSP file can not be obtained, CM client version upgrade is expected to fail, but the result is not "5.00.869. 1509" but the "5. 08. 692. 1008" version.
    Success itself is a problem. The administrator misunderstands that the version upgrade of the CM…

    49 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 →
  12. 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 →
  13. 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 →
  14. Provide an option to automatically upgrade Client versions on PullDP

    We found some strange behavior's when having a Pull DP deployed and will deploy a SCCM Agent later. This occurs only when the newest Client version has not been upgraded to production.
    According to https://technet.microsoft.com/en-us/library/gg712321.aspx> the versions must be the same.
    ---
    On a computer that is configured as a pull-distribution point and that runs a Configuration Manager client, the version of the Configuration Manager client must be the same as the Configuration Manager site that installs the pull-distribution point. This is a requirement for the pull-distribution point to use the CCMFramework that is common to both the pull-distribution…

    38 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 →
  15. 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 →
  16. 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 →
  17. 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 →
  18. 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 →
  19. Allow maintenance windows to be targeted for ONLY client upgrades

    Allow maintenance windows to be targeted for ONLY client upgrades. In 1810, you can target a MW at all deployments, software updates or task sequences. It would be nice to have an option for client upgrades as well. That way you don't have to shuffle groups and software updates advertisements around when its time to upgrade.

    21 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 →
  20. Download content before starting required Task Sequence

    If the task sequence is deployed as "Available" it's possible to download the content before starting TS. But if I create a "required" deployment it's not possible to download the content before the user gets the pop up to start the task sequence.
    For the normal user is it not easy to find the TS in Software Center without any information. Because of this fact is it interesting to implement to pre-download function also to the "required" type.
    First of all, the content should be downloaded and afterwards the user should see the pop up to start the TS/Operating System.

    20 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 →
← Previous 1 3 4 5 6
  • Don't see your idea?

Feedback and Knowledge Base