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. Install Servicing Stack Updates Before Other Updates

    Currently, when servicing stack updates and regular updates are deployed in the same software update group, the patches do not apply in a determinant order. This leads to cases where a cumulative update that requires a new servicing stack is installed before the servicing stack itself.

    While this can be worked around by separately deploying the servicing stack update before updates that require said servicing stack, it would be much more convenient if the update installation process checked if there are any servicing stack updates to be deployed and automatically installed them first

    681 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    12 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  2. Add 80072ee2 as a default code to the WSUS Scan Retry Error Codes

    If a SUP/WSUS server is offline or in a disaster situation, clients should be allowed to failover to another SUP.

    Currently if a SUP goes offline, clients simply will never scan again, and this is not an ideal situation.

    105 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  3. Automatically Publish Full Content for Third Party Software Updates

    With the release of CB 1806 we are now able to publish third party updates using custom catalogs. Ideally, third party patches would function exactly like first party patches from an administration and automation perspective. Currently there's two main areas where this is not the case.

    Synchronization Schedule:
    I could be wrong on this but I believe that subscribed catalogs sync automatically every 24-hours. While that's nice, it would be great to simply integrate with the existing sync schedule. Sync the catalogs, publish relevant metadata to WSUS, then sync the SUP(s).

    Automatic Deployment Rules:
    Currently, only update metadata is publishedā€¦

    248 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    12 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  4. Improve SCCM's built in WSUS cleanup and maintenance task

    Preview SCCM versions have a basic WSUS cleanup and maintenance task. It should be evolved and expanded to include SQL index optimization, IIS configuration optimization, and deletes of declined updates.

    29 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  5. Option to reboot at the end of the maintenance window

    We have an issue with business wanting to know within a 15-30 minute timeframe when the server reboots. With the maintenance windows today we can only open for installation and reboot but do not know when during the maintenance window the reboot will happen. Would it be possible to allow a setting to wait with the reboot to the end of the maintenance window. This way the reboot time would be predictable and installation would happen during the maintenance window. The option could be something like "If reboot is required wait until the end of the maintenance window to reboot"ā€¦

    18 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  6. Add deployment setting-Allow enforcement outside of maintenance window for deferred update (updates that have missed one maintenance window)

    There are many benefits to having one deployment for all of our workstations. We have an ADR that approves our patches and deploys them to a singular collection. Our update schedule is segmented so that not all locations go at once. Since we only have one deployment, this assignment is carried through by maintenance windows. We would love a setting that allows the workstations to wait for their maintenance window after our approval, but as soon as it has missed one window "and is now a deferred update" then enforce outside of maint. windows. We know we could go backā€¦

    10 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  7. Change the default timeout for feature updates, when feature updates timeout they should fail and stop.

    The feature updates in our environment always time out on the older machines with mechanical drives as they are slow to update. It would be helpful if the timeout was set to a lot more than 1 hour by default. Secondly when it does time out it would be helpful if it failed the deployment instead of sitting in software center saying it's installing indefinitely. The only way I've been able to do this is to delete the client from SCCM and re-install the agent on the client machine. Distribution of feature updates through SCCM needs a lot of work.

    30 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    3 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  8. Office 365 Proofing Tools language Selection

    Office 365 Proofing Tools language Selection:

    In SCCM, we cannot select the Office 365 Proofing Tools Languages along with the Office 365 Client Update. But, if we choose the Office 365 languages then the respective Office 365 Proofing tools language will be selected.

    Office 365 language size will have ~400-500MB and the Proofing tools language size will have 30-150MB. So, if we select ONE language, then it will be around ~450-650MB. Here most of the users will not have Office 365 language Pack, but they will use Office 365 Proofing Tools languages for Grammer, Spell check, etc.

    As per theā€¦

    22 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  9. Allow WSUS servers to download updates only on HTTPS

    Currently, the WSUS servers connect to the URLs (both HTTP and HTTPS) to download the updates, as mentioned in this link: https://docs.microsoft.com/en-us/sccm/sum/plan-design/plan-for-software-updates#BKMK_ConfigureFirewalls

    This means allowing HTTP traffic to come down to internal servers (by creating exceptions in the proxy settings), causing serious audit failures and security concerns.

    Also, a lot of proxy solutions also have a capability to block the content from whitelisted HTTP URLs if the file size is too large, thinking that it might be malicious content. This again causes problems when Windows 10 Feature and Express Updates are downloaded!

    Hence, it would be great to publish allā€¦

    15 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  10. Support Phased Deployments in Automatic Deployment Rules

    I think this is pretty straight-forward. If the Phased Deployment feature is to become a thing for software updates it needs to be supported as part of ADRs. If organizations are manually deploying updates then they're simply doing it wrong. If anyone thinks I'm transitioning from automated deployments to manual phased deployments they vastly underestimate my laziness.

    5 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  11. The Office 365 updates behavior in SCCM 1802 still feels off and unpolished

    We still see prompts for closing running office applications and while Software Center displays a reboot required, the update doesn't seem to get installed unless manually triggered through the in-app notification.

    63 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    6 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  12. Bring Servicing Plans into Parity with WUfB/Intune or Kill Them

    Since the initial release of Win 10 servicing plans they haven't kept up with their WUfB/Intune companions. While I can appreciate that many are not using servicing I feel it's a bit of a chicken and egg problem.

    Specifically:
    Remove SAC-T at some point (Win 10 1903 and beyond won't have it)
    Increase the delay to 365
    Configure the uninstall period (2-60)
    Support the Insider releases.

    Alternatively, since WUfB is now integrated into the console just get rid of servicing plans entirely. In such case you may want to integrate the dual scan configuration into the WUfB node.

    11 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  13. Add software updates package source restrictions or warnings

    When a software updates package is created, the given path is cleared of any existing content. This is very destructive if an incorrect path is given. One of several things should happen:
    1. Restrict the location of software updates packages if another package is using the same folder or any folder below.
    2. Warn if additional content is detected in the given path for a software updates package.
    3. Not clear additional content from software updates packages source locations.

    We recently ran into this with a co-worker making documentation and put in the root path for all of our packagesā€¦

    10 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  14. Deploy patches to servers only after an event has occurred successfully during a defined period of time

    Deploy patches to members of a server collection after a chosen event has completed successfully within a defined period of time, this would allow for a backup to occur for example before deploying the patches. This would then check that an event has happened before running the patch install process using ConfigMgr, and using status messages to create alerts based on event viewer this could then be used for non MS backup utilities.

    3 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  15. Allow offline patching of Feature Updates

    Currently (as far as I can tell anyway) there is no way to offline patch a feature update. I'm currently in the process of developing an upgrade strategy for moving from 1709 to 1809.

    At the moment, I have to deploy the feature update, and once complete, the subsequent patches are applied soon after, increasing disruption to users already inconvenienced by having their computer offline for at least 30 minutes while the feature update applies.

    It would be great if the feature update could be kept "up-to-date" by allowing offline patching, and therefore necessitating only a single reboot, which wouldā€¦

    3 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  16. Update changes to maximum runtime for software updates with machine policy

    If maximum runtime for an update is changed it can take weeks/months and sometimes never to update on a client that already received the update assignment.
    In our case it was a feature update and we changed the software update maximum runtime after deployment once we found this was missed.
    We still find clients after 1 month that is in failed state for the update and have the standard maximum runtime value.

    4 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  17. 102 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    8 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →

    Updating status to planned, see https://docs.microsoft.com/en-us/sccm/core/understand/find-help#send-a-suggestion for an explanation of each status value.

    Weā€™ve shipped fixes for a few scenarios that can cause this in 1902 but know there are some scenarios left.
    May we ask anyone still experiencing it on 1902 to gather verbose logs from the client and send a frown so we can troubleshoot additional scenarios that cause the error.

  18. Bios & Firmware Centre

    While there is some nice ideas to update bios and firmware, it tends to require a lot of customisation. It would be nice to have a new feature in Software updates dedicated to this. Just construct a framework and hopefully the tier 1 vendors would provide the 'plugin' to be able to update/patch within SCCM

    2 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  19. Provide an Install Updates TS step which uses DISM

    There should be an Install Software Updates TS step which allows you to select an existing Software Update Group/Deployment Package and apply all those updates using DISM rather than just triggering a scan of available deployed updates.

    5 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  20. Ability to get reports on individual update by clicking on the Pie

    When I click on individual updates, I see on the bottom the pie chart of "Total Asset Count:" I am requesting that be a link that automatically launches the report so I can get a listing of all the machines related to the pie chart. Similar to when I click on a deployment and I can drill down to the list of Objects related to that deployment where it failed, succeeded, etc. I know I can run a report, but the report is not always accurate and "live". For that matter, where is it getting that number from??

    4 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
← Previous 1 3 4 5 20 21
  • Don't see your idea?

Feedback and Knowledge Base