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. Include verbose information with import-cmpackage cmdlet

    The Import-CMPackage cmdlet does not provide much in the way of verbose output with the -verbose flag. This would be useful to identify what the cmdlet is performing in the background to determine if package already exists with the same name or not.

    Steps attempted:
    $Global:VerbosePreference = "Continue"
    $Global:DebugPreference = "Continue"
    $Global:CMPSDebugLogging = $true

    import-cmpackage -ImportFilePath "\localhost\c$\Users\Testing\TestPkg.zip" -Verbose

    Output: Verbose: Performing the operation "Import" on target "Package: ".

    Trace-Command -Name metadata,parameterbinding,cmdlet -Expression {Import-CMPackage -ImportFilePath "\localhost\c$\Users\Testing\TestPkg.zip" -WhatIf} -PSHost
    DEBUG: ParameterBinding Information: 0 : BIND NAMED cmd line args [Import-CMPackage]
    DEBUG: ParameterBinding Information: 0 : BIND arg [\localhost\c$\Users\Testing\TestPkg.zip] to parameter [ImportFilePath]
    DEBUG:…

    4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  2. OSD - Have different command-line options in the "Upgrade Operating System Task Sequence" to upgrade Windows 10

    Make the Upgrade Step more customizable. I'd actually like the ability to remove the /quiet tag from the setup.exe command line, and be able to add the additional commands right on that step instead of having to add additional steps to create the those variables.
    Add Check boxes for additional preset parameters to enable /disable, and text box to add custom (reflect drivers, etc)

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  3. Incorrect Icon Size When Using New-CMApplication and Set-CMApplication

    When using New-CMApplication or Set-CMApplication with the IconLocationFile parameter and an icon at least 128x128 in size, the application is created with a very small icon. I am not certain if smaller icons are effected.

    10 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  4. Powershell cmdlet for adding global conditions as requirements

    We are using PowerShell as a frontend for creating applications. As default we create multiple deployment type, each of them intented to run in certain environemts. These environemts are defined in some custom global conditions.

    When creating the deployment type we can very easily identify which global contitions shold be set as requirement. But we miss a Powershell cmdlet to automize this task. Instead we rely on the application creator to remember to add these conditions.

    So far I have found a PS-script that can add one of the build-in conditions, but it fails when trying to add a custom…

    39 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  5. Improve Content Replication

    Content Replication from Site to DPs should be a frustration free Process or SCCM Admins. Unfortunately, I know no customer without smaller or bigger issues in this area.
    Here is an uncomplete list of some issues I´ve noticed:
    • Content Eval - Scheduled Task lost
    o SCCM does not check if the schedule task got lost/deleted
    o Suggested Solution: SCCM should verify the Scheduled Task on Service Startup
    • Content Eval - Hash mismatch/Eval fails for package
    o When content Eval fails for a package, the admin must manually redistribute it / take care of the error
    o There should…

    225 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  2 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  6. 13 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  3 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  7. Make Windows 10 Setup Compatibility Scan Language Neutral

    It would be nice if a checkbox "Perform Windows Setup Compatibility scan withnout starting upgrade" inside "Upgrade Operating System" step in SCCM Upgrade Task Sequence would be language neutral.

    What I mean by this is that we would like to run this scan prior to the Upgrade itself but to be able to do that currently we have to switch the running OS to en-US (the same language as the Upgrade iso), then run the scan and in case an error is found, we need to switch back to original language again and reboot the computer. This is not a…

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  8. can we use iso image in sccm to deploy to all client instead of wim file

    can we use iso image in sccm to deploy to all client instead of wim file

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  9. change the display police on a Task Sequence Step when a condition exists

    change the display for a Task Sequence Step when a condition exists for example change the policy or highlight all steps to identify quicker where some conditions are applied

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Admin Console  ·  Flag idea as inappropriate…  ·  Admin →
  10. Do not allow "SMS" as Site Code Name

    I found some customers which has "SMS" as name of SCCM site. This make a lot of problems with normal management. This name should also be make as do not allowed (wizard blocks also other names). And if already named, it should allow one time change.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Setup and Server Infrastructure  ·  Flag idea as inappropriate…  ·  Admin →

    We do document this, and this has been the case since at least SMS 2003.

    See:
    https://support.microsoft.com/en-us/help/279868/reserved-site-code-names-in-sms-2003-and-configuration-manager
    https://docs.microsoft.com/en-us/sccm/core/servers/deploy/install/prepare-to-install-sites

    I’ve also confirmed that Setup disallows you from using the several “reserved” site code names and has done so since at least 2012 SP2.

    Was unattended setup used? That’s the only way I can think of that may have bypassed this validation.

  11. Switch to next SUP - scripted on client

    ConfigMgr agents are able to fallback to an alternative SUP if the original SUP failed - agents do not fallback to the original SUP once it’s available again. In this case fallback needs to be triggered manually. This can be done from the console using „client notification“ – wouldn’t it be good to also be able to force SUP fallback on the client itself? Document a script method to switch to the next SUP that can be run on the client itself.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  12. 3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Power Management  ·  Flag idea as inappropriate…  ·  Admin →
  13. Remove Deleted Content from Client Cache

    Today, when you remove an object from ConfigMgr (Package, application, etc), the content remains in the local client cache (if it was ever downloaded). In an effort to clean up that old content, I think it would be a great idea to automatically cleanup content. For example, once I delete an image from the admin console, I will never need it again on my client systems, so go ahead and delete it from any system that has it in the cache.

    (I currently use TidyCache to remove 'old' cache', but would prefer that this be handled natively by ConfigMgr. https://gregramsey.net/2015/11/17/tidy-cache-clean-up-old-ccmcache/

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  Content  ·  Flag idea as inappropriate…  ·  Admin →
  14. Temporarily suspend any SCCM client activity

    Many of our users (300000) need a feature to temporarily suspend any SCCM activity at least for a limited time per day.
    Activities that need to be suspended are:
    - Downloads
    - Installs
    - Reboots

    Business cases:
    Customers Skype sessions often get disturbed while a download is running in the background. We thought the setting "Suspend Software Center activities when in PowerPoint presentation mode" would help but from what our user reports it doesn't.

    Another scenario are users working on metered connections, e.g. as they are provided by Deutsche Bahn. Users working on such a connection quickly use up their…

    106 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  9 comments  ·  Client Settings  ·  Flag idea as inappropriate…  ·  Admin →
  15. Apply Boundary Groups to WinPE Management Point selection

    Currently it appears that when the SCCM agent in the WinPE boot image connects to a Management Point, it selects one without using the Boundary Group rules, instead selecting one from the AD published list, starting with the first alphabetically.
    Instead this should behave like the full blown Windows SCCM Client and select a Management Point based on Boundary Groups such as IP range.
    It is worth noting that Distribution Points are selected correctly according to Boundary Group by the WinPE client, for OSD content.

    101 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  16. Run Scripts: Need folder support for feature

    It would be nice to be able to make folders and apply security to each folder for the new scripts feature.

    37 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  4 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  17. Add 2 new options for MDT, define and use Deployment toolkit

    Add
    MDT Define Microsoft Deployment Toolkit Package
    Use Defined Microsoft Deployment Toolkit

    So you can define then just use the defined MDT Toolkit. This would make it easier when you have multiple Use Microsoft Deployment Toolkit Package, in the TS. This way they wouldn't all have to be edited. So after you make a change/update your UDI for whatever reason usually applications upgrades.

    This would same a major amount of time also ensure you don't miss one, and less time editing and testing.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →

    Hi. This reads like something that would be addressed with the ‘Daisy chain task sequences’ https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/8339997-daisy-chain-task-sequences-osd-and-non-osd

    With that you can updating a single referenced/child task sequence containing the MDT Package and any ‘parent’ task sequence will get that update too.

    Let me know if that matches your ask and I’ll merge your votes with that item.

  18. Possibility to priorize an (InPlace) Upgrade Task Sequence over Update Installation

    Since Microsoft introduced the strategy to deliver two new OS builds per year for Windows 10 and a mandatory expiry date of SAC builds, the focus / Engineering task focuses back to perform in place Upgrades via Task Sequences.

    As those Task Sequences are not deployed at a specific time during the week it might happen that some Windows OS Quality or Office Update are pending or queued for Installation. It does not make sense to deploy a Quality Update for the OS Build which is queued to be upgraded to a new OS Build (with new Quality Updates).

    My…

    23 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. Bring back CCMClean support

    We need a "manual" or force clean - a complete removal of all traces of the ConfigMgr client to be supported again.

    Too much wasted time is spent trying to track down all the left overs that cause unhealthy clients.

    Thankfully some of those in the community have published scripts that help, but unfortunately they are "not supported" and many times incomplete.

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  Tools  ·  Flag idea as inappropriate…  ·  Admin →
  20. For the option to "Run only on the specified client platform," include the option to specify specific Windows 10 branches.

    Include the ability to select specific Windows 10 branches for the option "Run only on the specified client platform." I have scenarios where I would like to limit certain task sequences and/or packages to e.g. current branch 1607 but not 1703.

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Operating System Deployment  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base