Microsoft

Microsoft Endpoint Configuration Manager Feedback

Suggestion box powered by UserVoice - Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more

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. It would be great to export just task sequence xml file so it can be added into git repo in multi admin enviorment

    It would be great just to get drop in task sequence to export task sequence xml file to it can be uploaded to external repository as way to keep track of changes in any change management system

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →

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

    Our 2006 release is now in the opt-in phase (fast ring)
    Blog: https://techcommunity.microsoft.com/t5/configuration-manager-blog/update-2006-for-microsoft-endpoint-configuration-manager-current/ba-p/1569562
    Docs: https://docs.microsoft.com/mem/configmgr/core/plan-design/changes/whats-new-in-version-2006
    Support Information: https://aka.ms/cmcssreleaseinfo

    This releases adds the Community Hub https://docs.microsoft.com/en-us/mem/configmgr/core/servers/manage/community-hub which addresses some of the User Voice asks you have added for task sequence version control, auditing, revision history etc.
    The Hub is nascent and we will continue to iterate, improving and adding new features.
    As part of this process we would appreciate your comments and feedback on the Hub.

  2. Run Scripts: Should be able to invoke from Deployment Status Node

    Run scripts brought a brand new model to handle client troubleshooting, but it can run from collections only.
    it would have been super useful to be able to run it on a machine\category from the Deployment Status node and then maintain clients with in progress \ unknown \ active \ inactive state.
    today when we have a list of computers who didn't report their status we need to manually create a collection with these clients to run a scripts and there's not even a built-in way to create a collection from the asset details

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Client Operations  ·  Flag idea as inappropriate…  ·  Admin →
  3. Fix Support Center on running app deployment eval cycle remotely

    When Support Center runs App Deployment Evaluation cycle locally, it uses Schedule 121, which is OK. However, when it’s connected to remote machine, it uses Schedule 123, which was deprecated at some point.

    Future release of Support Center should always use schedule 121.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Tools  ·  Flag idea as inappropriate…  ·  Admin →
1 3 Next →
  • Don't see your idea?

Feedback and Knowledge Base