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. Run Scripts: Need improved monitoring and reporting on script execution

    Allow filtering on Monitoring - Scripts. Filter by time and date, collection, and script name.

    5 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Client Operations  ·  Flag idea as inappropriateā€¦  ·  Admin →
  2. Run Scripts: Do not preserve parameters when scripts are re-run, and log parameter usage in Monitoring

    When using parameters, the last value used should be blanked out when run again. The value of parameters is the dynamics of it all. You can overwrite the value but seems it would be best servers to not retain the value after running. Would also be great if the parameter used was logged in the Script Status node for ease of tracking.

    4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  0 comments  ·  Client Operations  ·  Flag idea as inappropriateā€¦  ·  Admin →
  3. 4 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  1 comment  ·  Client Operations  ·  Flag idea as inappropriateā€¦  ·  Admin →
  4. Run Scripts: Allow parameters to be marked as passwords so it's hidden when entering

    Run Scripts: Allow parameters to be marked as passwords, so scripts can be executed by passing on passwords but the password isn't displayed while being typed.

    Real life example: Using PowerShell scripts to run Deep Freeze tasks such as freezing or thawing computer. The Deep Freeze command line tool requires entering the passwords to be able to execute the commands.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Client Operations  ·  Flag idea as inappropriateā€¦  ·  Admin →
  5. Run Scripts: Allow for specifying the number of concurrent jobs

    Run Script: Define # of concurrent jobs (optional)

    It would be nice if, optionally, we could limit the number of machines the script is being executed on simultaneously.

    For instance, I created a script that is collecting some local logs and pushing them back to a network location.
    I do not want it to run on 1000+ servers simultaneously so if I could define the maximum number of servers the script should be run from concurrently, that would be nice.

    3 votes
    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 →
  6. Run Scripts: Need to have visibility on who executed a script (accountability)

    Script status should provide details on who executed a particular script.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Client Operations  ·  Flag idea as inappropriateā€¦  ·  Admin →
  7. Run Script: Ability to pass collection variables

    I want to run a powershell script with the new Run Script, with the ability to see the collection id, collection variables, collection members that script is being ran against. The script runs on the local system as SYSTEM so it can't reach back to SCCM to obtain this information. I know you can add credentials to allow this, but a simple GET-CMRunScriptCollectionName or GET-CMRunScriptCollectionVariables would be nice.

    3 votes
    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 →
  8. Run Scripts: Schedule the script to run later

    It would be nice to be able to schedule a script to run at a later date and/or time. It would also be nice to see what scripts are scheduled and by who and when and to what device or collection. Also the ability to cancel it. I've used a tool before that did this very nicely and it would be nice to have SCCM able to do it as well.

    2 votes
    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 →
  9. Search filter for Client Operations in Monitoring

    Client Operations in Monitoring allways open with 1000 oldest. Maybe a better start filter could be recent summarized. there's also a saved search filter but no search option!

    2 votes
    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 →
  10. Run Scripts: Add the option for scripts to access package content

    Add an option to scripts to be able to define a package source so that you can access additional files from your script without needing to point to a network location. Not everything fits neatly into a single script and sometimes you need additional files for modules, config files, etc. This could work similar to the "Run Command Line" task sequence step.

    Yes I know you can just use a package for these, but packages are so 2007. Besides, we all want speed!

    2 votes
    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 →
  11. Powershell 7 support for Run Scripts, Task Sequences, and Configuration Items

    Explicitly being able to select the option of using PowerShell 6.x in scripts/compliance rules/task sequences would be a good future thinking feature to adopt as soon as possible.

    Ideally a version option built in to SCCM like that for x32/64 OS, but for PS 5.1/6.x would make this interesting.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Client Operations  ·  Flag idea as inappropriateā€¦  ·  Admin →
  12. Run Scripts: Ability to run unapproved scripts on a test collection

    The "run script" feature is fantastic, but somewhat clunky when multiple lower level admins are adding scripts, as they can't be tested before approval.

    It would be great if we could designate a "development" collection for running scripts that have not been approved yet.

    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 →
  13. Run Scripts: Prevent Script feature from sending all (i.e. optional) parameters

    What I've noticed when using the new "Scripts" feature is that SCCM runs scripts with a very specific command format/syntax when calling a PowerShell script. Part of that is explicitly specifying every individual script parameter, regardless of whether it is mandatory.

    I suppose that normally, this shouldn't be a problem, but besides being unnecessary and against the spirit of optional parameters, I've also been running into what I assume is a bug, where SCCM fails to properly pass all parameters. There seems to be a parameter limit, or more likely, a character limit to the command line SCCM runs onā€¦

    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 →
  14. Run Scripts: Option to be integrated with Application / Packages deployment

    Running Script : option to be integrated with Application / Packages deployment. On going into deployment type or in package program we should have option to use approved scripts from console.

    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 →
  15. Powershell script Collection

    After running a script on a collection or set of machines have the ability to automatically create a collection on machines that failed the script or machines that could not be connected to. So that after the machine is online the script can be run against it.

    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 →
  16. Peer Cache

    We are currently having an issue with Peer Cache where it will reuse folders in the Cache directory causing a Hash Mismatch error.

    We suggest either Peer Cache checks to make sure a folder doesn't already exist before it downloads or we suggest that the Task sequence does fail and just moved on to the next Super Peer.

    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 →
  17. Hide parameter values in Run Script log

    Task Sequence can hide values from being recorded in the task sequence log. It would be nice to have this ability to do the same for the Scripts (Scripts.log). I know it is not recommended to use passwords while using the Scripts feature, but there are cases which I want to send passwords. I don't really have any concern in certain cases. However, I just do not like how the password (script parameter) can be viewed later within the Scripts.log. It would be nice to have the same feature to hide parameters as the Task Sequence will hide credentials inā€¦

    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 →
  18. Run Script Needs Better Logging on the Server Side

    The scripts.log on the client is great, but I have seen where the console never gets results. I've waited 10 minutes and it just sits there showing the green progress bar. The script itself runs in less than 2 seconds. The MPRelayMsgMgr.log and SMSMessageProcessingEngine.log on the server don't show the machine name, and the information they do show is limited. Makes troubleshooting really difficult when the script that needs to run allows you to remote into a machine (remoting is blocked by company policy and a PowerShell script is needed to run in order to enableā€¦

    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 →
  19. Run Scripts feature should support other scripting types (VBScript, Perl, etc)

    It would be awesome if more languages were supported for real-time Script deployment in addition to PowerShell. Maybe VBscript, Perl or Javascript, etc.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    Noted  ·  1 comment  ·  Client Operations  ·  Flag idea as inappropriateā€¦  ·  Admin →
  20. be able to clean multiple client operations at the same time on the monitoring node

    Currently we are only able to clean 1 client operation by 1, when it comes time to cleanup it's so long ...

    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 →
  • Don't see your idea?

Feedback and Knowledge Base