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. Import/Export Cmdlet Parameter aliases

    Could we please have a common alias for the file path parameters in the various import/export cmdlets?

    For example, currently we have:
    1. Export-CMBaseline uses -Path to set output path, and
    2. Export-CMTaskSequence uses -ExportFilePath.

    Then we have:
    1. Import-CMBaseline using -FileName to determine location of exported files
    2. Import-CMApplication using -FilePath,
    3. Import-CMTasksequence using -Path.

    A common alias like "Path" or "FilePath" for all these parameters will be very handy in reducing complexity of scripts calling your Cmdlets.

    1 vote
    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 →
  2. Add the ability to add and edit Install Behavior for Application Deployment types with PowerShell cmdlets

    Add the ability to add and edit Install Behavior for Application Deployment types with PowerShell cmdlets

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  3. Run Scripts: Need ability to schedule execution

    Since version 1707 it's now possible to run Powershell scripts for a collection, but these scripts cannot be scheduled. It would be of real value if these Powershell scripts could be scheduled.

    88 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  4. Save-CMSoftwareUpdate - Add parameter to specify download source path (UNC\Network)

    When using this cmdlet to download updates from an update group into an update package, where is the download source and is it possible to specify a custom location?

    For example, if I wanted to specify my download source as a WSUS content folder on another server I could I do something like this.
    Save-CMSoftwareUpdate -SoftwareUpdateGroupName $mySUG -DeploymentPackageName $mySUPkg -SoftwareUpdateLanguage "English" -DownloadLocation "\myWsusServer\wsuscontent"

    This would be helpful in the following scenario, let's say we have a stand-alone primary that cannot be connected to the internet due to a business requirement, but has access to an upstream WSUS server that downloads…

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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…

    40 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 →
  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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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.

    40 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 →
  8. PowerShell Cmdlet to display the required software updates for a device

    I would like to have a cmdlet to display all required updates for a device, or all devices. I have made a SQL query to do this, so I know it's possible. The query is based on the "Software Updates - A Compliance" reports, but only lists required updates, not installed. This is very useful for finding any missed updates that may be important or critical.

    13 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 →
  9. MVP-Powershell for Adding EP collection to dashboard (UpdateVisibilityInEPDashBoard)

    add-CMCollectionToDashboard and Remove-CMCollectionFromDashboard would be great addition to the existing powershell so the UpdateVisibilityInEPDashBoard WMI method would not be required anymore

    4 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 →
  10. Run Scripts: Should allow for exporting results from Script Status

    Run Script: export the results from Script Status to Excel file

    11 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  11. Should support "run as" functionality when executing scripts (Applications, Run Scripts, etc.)

    SCCM PowerShell scripts running in a corporate environment are hobbled due to the NT AUTHORITY\SYSTEM context. I have multiple cases where I could create an Application that just runs a PowerShell script but the script needs to run as a domain admin to do what it has to. The new Scripts feature also needs run-as functionality for fire & forget type tasks. Including a run-as facility in SCCM would significantly extend the product's flexibility.

    14 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 →
  12. 15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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 →
  14. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  15. Run Scripts: Add Deploy in the Scripts section in the software library

    Would love to see the ability to right click on a Script in the software library and be able to select Deploy.

    12 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 →
  16. 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.

    11 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 →
  17. Run Scripts: Need cmdlets to support feature

    Create cmdlets for the new in console Powershell scripts. Some good ones would be new Script Deployment and get script results.

    EX:
    New-CMPSScriptDeployment -Name "Script Name" -CollectionName "Collection Name"

    10 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 →
  18. 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.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  19. Create a PowerShell cmdlet too add/edit/remove duplicate hardware identifiers

    New-CMDuplicateHardwareIdentifier
    Set-CMDuplicateHardwareIdentifier
    Remove-CMDuplicateHardwareIdentifier

    Please create cmdlets to add/edit/remove duplicate hardware identifiers. We have a large organization and those pesky Lenovo Yoga's get a USB to Ethernet dongle with each one. We have over 500 dongles currently, and I don't see a way to automate importing those MAC addresses. Thanks!

    64 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    9 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for your feedback and suggestions, updating status to started.

    We added these CmdLets in our 1910 release:
    New-CMDuplicateHardwareIdGuid
    New-CMDuplicateHardwareIdMacAddress
    Remove-CMDuplicateHardwareIdGuid
    Remove-CMDuplicateHardwareIdMacAddress

    More details here:
    https://docs.microsoft.com/en-us/powershell/sccm/1910-release-notes?view=sccm-ps

    Please try them out and share any feedback you may have, then I’ll likely close this item with our 2002 release.

  20. PowerShell CmdLets: Improvement for Software Update Maintenance

    Paging Adam Meltzer.
    I’ve spent the last couple of weeks writing a PowerShell script to provide end-to-end maintenance of software updates. My goal was to use the CM cmdlets as much as possible. While I think I have everything working the experience leads me to make the suggestions below. In all honestly; maybe I’m just doing it wrong and there is a way to do the things I couldn’t figure out.
    The documentation for Get-CMSoftwareUpdateDeploymentPackage says that it returns a CMSoftwareUpdateDeploymentPackage object but it’s actually returning WqlResultObjectBase. Maybe I’m just supposed to cast it but I failed trying.

    I could…

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

Feedback and Knowledge Base