Microsoft

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

    1,557 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  36 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  2. Show Powershell equivalent command(s) at any wizard completion

    At wizard completion for anything, show the Powershell cmdlet equivalent like in other System Center products.

    1,452 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    24 comments  ·  Admin Console  ·  Flag idea as inappropriateā€¦  ·  Admin →
  3. Prompt users for reboot, but NEVER force it

    The reboot settings only allow for the user to postpone a reboot for up to 24 hours. Why can't we expand that time or just keep reminding them forever until they reboot themselves? The longer that they have been pending a reboot, remind (pester) them more frequently. Or auto reboot if nobody is logged on.

    1,334 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    40 comments  ·  Compliance Settings  ·  Flag idea as inappropriateā€¦  ·  Admin →
  4. Make ConfigMgr work with Autopilot and Enrollment Status Page (ESP)

    When deploying a device using Autopilot, the Enrollment Status Page (ESP) is used to prevent access to the desktop until the device provisioning tasks are complete. But ConfigMgr doesn't integrate with the ESP, so there's no way to wait for packages, apps, or task sequences - the user doesn't know when the process is done. Add that integration.

    867 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  19 comments  ·  Operating System Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  5. ConfigMgr Web Console

    Introduce ConfigMgr Web Console and remove the need to update the console on every device with each SCCM CB Upgrade as local admin rights are needed to update the console.

    The ConfigMgr Web Console might be similar to Azure Portal with Microsoft Intune.

    With SCCM CB updates getting released more frequently than before, this will provide benefits and ease of management. The Admins can connect to the ConfigMgr console from any computer in the organisation without the need to install it.

    732 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    24 comments  ·  Admin Console  ·  Flag idea as inappropriateā€¦  ·  Admin →
  6. 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ā€¦

    396 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  17 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  7. Software Center "Sort by" default view

    Change default "sort by" order from "Most recent" to Alphabetic list (Application name A-Z). Or remember the setting for the client. Or allow a SysAdmin setting for site-wide default setting. It always resets back to Most recent.

    377 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    17 comments  ·  Software Center  ·  Flag idea as inappropriateā€¦  ·  Admin →
  8. ADR Available Deployments

    I would like to see ADR's support the creation of Available deployments in addition to Required deployments. We have some business cases where a certain subset of servers are aren't allowed to "push" software updates to until the server/app owners have verified the patches.

    The issue is that these servers don't have connectivity to the internet so we have to deliver them via ConfigMgr. By creating an Available update using an ADR, it streamlines our ability to "deliver" the updates to all systems, and allow the Patching Team, or App/Server owner to patch according to their own business schedules.

    274 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    27 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  9. DSC to replace or compliment basline feature

    DSC is a wonderful framework for handling baseline configurations across Windows and Linux machines, but it's completely unsupported in SCCM directly. While a Pull server is certainly more simplistic than an SCCM hierarchy, it would still be very beneficial to have some integration in a couple of areas:

    Management Points can easily be configured to host mof configurations for clients, and a new client policy class for allowing the SCCM agent to configure the pull server settings on a host would be great. Alternatively a new role could be made ... not sure that would feel as elegant.

    The baselineā€¦

    169 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Compliance Settings  ·  Flag idea as inappropriateā€¦  ·  Admin →
  10. 131 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    14 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.

  11. 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ā€¦

    130 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 →
  12. Complex scheduling: Enable patch deployments to servers based on SDLC (Dev / QA / Prod / DR)

    Based on Patch Tuesday, allow application / business owners to select appropriate down time for the server as well as a sequenced order (e.g., Development servers during the first week after Patch Tuesday, QA on the second week after Patch Tuesday, Production servers on the third week after Patch Tuesday, et cetera). This allows the business owners to "own their own destiny" and get systems administrators out of the business of coordinating patching maintenance windows. In addition, the ability to insert "change freezes" that force the schedule to increment all downstream targets out by an additional week to compensate forā€¦

    69 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  9 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  13. OSUninstall - Make ConfigMgr Aware of going back to previous builds

    Please Make CM aware if an OSUninstall (Reverting to previous Build) has happened, so it can heal itself into a functional state. Currently if you perform an OSUninstall from say 1809 to 1709, after you've upgraded originally to 1809 using a CM Task Sequence, the CM Client is non-functional.
    Client is in Provisioning Mode, Services are disabled, and once you fix that, it thinks it's int he middle of the Task Sequence and shows the Upgrade TS "Installing", so then you need to clear that out.

    Please make OSUninstall & CM Play Nice together, so we can offer users theā€¦

    61 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    3 comments  ·  Operating System Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  14. Ability to enable/disable any deployment (like you can with software update deployments)

    You should be able to enable or disable any deployment (for applications, packages, software updates, etc) by right-clicking and selecting enable or disable.
    Currently to disable an application deployment you either have to delete the deployment or retire the application and for packages you need to disable the program.
    Software update deployments already have this feature.
    You should also be able to enable/disable a deployment from the Monitoring workspace.

    60 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  1 comment  ·  Admin Console  ·  Flag idea as inappropriateā€¦  ·  Admin →
  15. Request full control over allow/disallow force closing of Office 365 apps when installing updates instead of force closing Office apps

    In ConfigMgr 1610 Update Rollup 1 provided the change so Office 365 Updates did not force close any office applications when Office 365 patches were installed through ConfigMgr Software Center.
    https://docs.microsoft.com/en-us/sccm/sum/deploy-use/manage-office-365-proplus-updates#restart-behavior-and-client-notifications-for-office-365-updates

    With ConfigMgr 1706 we require the option to disallow force closing of office 365 applications when patches are installed through the ConfigMgr Software Center.

    49 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  2 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  16. Read Only Intune connector

    Please can we have a read only Intune connector so that we are able to have asset information from standalone Intune in SCCM.

    We would like to be able to utilize asset information in the way that you can with hybrid Intune, without having to use hybrid Intune. AS far as i can tell, this is not currently possible in any other way.

    22 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  1 comment  ·  Mobile Device Management  ·  Flag idea as inappropriateā€¦  ·  Admin →
  17. Update CM cmdlet documentation and downloadable help file

    Running update-help pulls down a help file to an older version of the cmdlets. For instance, do a clean install of the console and cmdlets.

    Type:

    Get-Help Add-CMApplicationCatalogWebsitePoint

    On a machine that has not had the help file updated, you will see 6 parameter sets under Syntax. Run update-help and then try again. You will now see 2 parameter sets under Syntax. In addition, there is no detailed information for the new cmdlets added.

    13 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  4 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  18. Interactive step during OSD (or any other TS)

    To be able to add an interactive step when running a TS would be useful in many cases. You might not always want to run an OSD as User Driven, but still in one step you want user input.
    Not only for production, but for test purposes this would be really good.

    Today, I'm running a very customized solution to make this happen.
    I created this one in order for this to happen, it should be easier.
    https://plus.google.com/105132092500423486001/posts/9aCA7LUVpuv

    12 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Operating System Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  19. Unify Powershell Functionality

    The recent Powershell features like 'Run Script' and allowing them to be added directly to a Task Sequence step are fantastic, but things are beginning to feel somewhat fragmented.

    It would be great if SCCM had a central script repository, maybe backed by git, that we could pull scripts from as opposed to adding them.

    This would allow us to easily use the same code in a Task Sequence and a 'Run Script' without having to maintain it in multiple places. Perhaps we could even add a special Powershell Script Package Program type that would pull a script from theā€¦

    11 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  20. Remove the option to deleted the members from a collect when the collection is deleted.

    It seem odd that since you multi-select and deleted user / computers that you would need to have a prompt to delete the users / computers when deleting the collection.

    The process should be if you need to deleted the users / computers and the collection.
    - Multi-select and deleted computers. If there is a large number users / computers blocks deleted if number excesses High-Risk deployment settings.
    - Deleted the Collection
    - If the collection is limiting another collection. Then prompt if that collection should be deleted too.

    10 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  1 comment  ·  Collections  ·  Flag idea as inappropriateā€¦  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base