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. 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 →
  2. 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"

    9 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 →
  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.

    94 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. Add NumberOfDependedDTs property to Get-CMApplication

    Currently, the only place to see NumberOfDependedDTs is from Get-CMDeploymentType. Other properties like NumberOfDependentDTs and NumberOfDependentTS have been propagated to the Application Level, it would be useful to have NumberOfDependedDTs too.

    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 →
  5. 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
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  6. Remote powershell for SCCM

    Like: Import-PSSession $(New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://server.domain.local/PowerShell/)
    -But for SCCM..

    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 →
  7. Export all data option for key nodes

    I would like the ability to right-click various nodes, eg packages, applications, task sequences, etc and export the data for that node to a file, eg csv which could easily be read back in via powershell. This would allow test environments to be set up quickly and might even help provide an a way to restore a production environment if all else fails...

    3 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 →
  8. Issues with Import-ClientConfiguration

    Import-CMComputerInformation is not allowing me the same access via Powershell as the console itself.

    https://www.reddit.com/r/SCCM/comments/6dipv2/permissionstoimportcmcomputerinformation/

    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 →
  9. Create a PowerShell cmdlet or cmdlet parameter to add return codes to application deployment types

    Add a PowerShell cmdlet or cmdlet parameter to add return codes to application deployment types.

    12 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  2 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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 →
  11. Run Scripts: Show PowerShell Intellisense in script editor prompts

    Now that we have the ability in TP1706 to upload and run PowerShell scripts against endpoints, it has exposed the need to be able to tab complete and validate syntax with intellisense from the console. I'm not asking you to recreate the PowerShell ISE/VSCode, just some rudimentary intellisense for when you are working on the Admin Console.

    0 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 →
  12. MVP - DCR wanted for server groups

    My customer has +_ 600 maintenance windows using the server grouping feature .

    Feature Request Nr1 : They use the node drain / node resume feature with PowerShell. They are still modifying and changing the script almost every week . That script is used for those 600 collections :

    a) a central repository/place to enter the script details and be able to reuse that for each server group collection like for power management custom templates .
    b) If they make a change in the “central” PowerShell repository , it keeps history ( Like application revisions ) and replaces that automatically…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  13. Allow Wildcard for cmdlets Get-CMPackage and Remove-CMPackage

    This would make it easier to remove multiple packages with similar names.

    3 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 →
  14. Set-CMSoftwareUpdateDeployment missing SoftDeadlineEnabled parameter

    Expose -SoftDeadlineEnable to Set-CMSoftwareUpdateDeployment -SoftDeadlineEnabled

    Its on Get-CMSoftwareUpdateDeployment not Set.

    6 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow use if DeploymentID as identifier in Set-CMPackageDeployment and Set-CMSoftwareUpdateDeployment

    Set-CMPackageDeployment and Set-CMSoftwareUpdateDeployment do not allow DeploymentID as unique identifier. Instead you need to use e.g. programname and packageid.

    In the case of Set-CMSoftwareUpdateDeployment this requires DeploymentName which is not even possible to retrieve from Get-CMDeployment

    Please, allow DeploymentID as an option to identifying the deployment in these cmdlets.

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

  17. PowerShell Cmdlet to collections & deployments for a computer

    Would be good to have a PowerShell CmdLet to get information on all collections and deployment for a computer is listed for.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  18. Create application from Licence for Store Apps

    Create application from PowerShell from the 'Licence for Store Apps'

    8 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 →
  19. PowerShell cmdlet "Remove-CMMaintenanceWindow" should accept Window Time as parameter

    Powershell cmdlet "Remove-CMMaintenanceWindow" should accept StartTime as a parater. Current implementation only accepts limited parmaters of collectionid, and maintenance window name. If you have two windows by the same name, with different start times... you will remove both by using this utility. I suggest it should also accept the StartTime as a paramter for specific window deletion. Maintenance windows are a point in time schedule, and therefore the Point in time should be considered as a parameter for removal. The current implementation of this cmdlet is dangerous, and cannot be used for finite window removal.

    5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  2 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  20. Collection Configure Alerts

    Create a powershell to configure the alerts on a specific collection. like adding collection to EP dashboard and configure thresholds

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

Feedback and Knowledge Base