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. add a powershell possibility to add requirements to a deploymenttype of an application

    At the moment it is not easy to add requirements to an application deploymenttype with PowerShell. I think many of us would benefit if this would be simplified.

    157 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  2. Run Scripts: Ability to Edit Scripts

    In 1706, once you create a script and approve it (or deny it) there is no way to alter the script except but to create a new one. Would be great to have the ability to set the script back to waiting for approval, which would unlock the code to be edited.

    155 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 →
  3. Improve and speed up adding or removal processes of direct members to collections, optimize handling in backend

    We need a quick way to quickly populate or empty collections. Targets should be imported as rules without triggering other processes in the background (eval/re-built). The same also applies to removal rules.

    Please implement something like an cmdlet “Add-CollectionMemberRules” / “Remove-CollectionMemberRules” with fast adding rules method, without delays, without rebuilding the complete collection sets in the background. The cmdlet should support especially adding rules like "DirectMembers".

    Note:
    This will help to control and steer application (ramp-up / ramp-down) rollouts, depending on device target lists, created by internal IT or delivered by business partner. The lists could based on different information…

    64 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 →
  4. PowerShell cmdlets for editing task sequences

    Being able to edit task sequences with PowerShell would make managing task sequences much easier. Some possible new cmdlets could include:

    Add-CMTaskSequenceStep
    Get-CMTaskSequenceStep
    Remove-CMTaskSequenceStep
    Set-CMTaskSequenceStep

    Add-CMTaskSequenceGroup
    Get-CMTaskSequenceGroup
    Remove-CMTaskSequenceGroup
    Set-CMTaskSequenceGroup

    58 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    12 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  5. Phased deployment support for PowerShell cmdlets

    Phased Deployment Powershell Cmdlets

    47 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 →
  6. 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…)
    4 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  7. New-CMApplication rejects icons larger than 250x250

    New-CMApplication rejects icons larger than 250x250 and returns the warning and error below, even though the SCCM console allows icons up to 500x500.
    WARNING: The maximum size of an icon is 250px X 250px.
    New-CMApplication : Validation of input parameters failed. Cannot continue.

    30 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 →
  8. Add missing InstallationBehaviourType parameter to new DeploymentType cmdlets in SCCM Powershell Cmdlets.

    This goes for all new Add/Set-CM*DeploymentType but for my example, I'll refer to Add-CMScriptDeployment.

    An example below is my generic Script Deployment Type.

    Add-CMScriptDeploymentType `
    
    -ApplicationName "$PublicName" `
    -DeploymentTypeName "$AppName Client" `
    -ContentLocation "$AppLocation" `
    -InstallCommand "$InstallStr" `
    -UninstallCommand "msiexec /x $MSICode /qn" `
    -MaximumRuntimeMins 720 `
    -LogonRequirementType WhereOrNotUserLoggedOn `
    -UserInteractionMode Hidden `
    -ProductCode
    -ScriptLanguage PowerShell `
    -ScriptText $scriptDetect

    When this is run, the DT is created with the Installation Behaviour set to the default value of "Install for system if resource is device; otherwise install for user"

    The previous version of this cmdlet - Add-CMDeploymentType had the parameter available…

    27 votes
    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 →
  9. PowerShell cmdlets need to be cleaned up

    I use a LOT of PowerShell ... and the PowerShell modules in SCCM are ... well... bad.

    Issue 1: I should not have to set my running location to a site to run a cmdlet. No one uses a set-location to make sure they are in the AD domain root before running a get-ADUser (unless they have a multi-domain environment and need to call something specifically), yet SCCM requires this to be true. It makes scripting needlessly complex.

    Issue 2: there are a pointlessly large number of cmdlets. Do I really need a Get-CMDeviceCollection and a separate Get-CMUserCollection? Why can't…

    25 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 →
  10. PowerShell Cmdlet for Modifying Nested Task Sequence (Get/Set-CMTSStepRunTaskSequence)

    It would be very helpful to have a cmlet that will allow you to modify the "Run Task Sequence" with PowerShell.

    I'd like to be able to script replicating an entire task sequence "suite" (including all of the nested sequences) and re-linking the new nested sequences.

    My use case is something like this:
    I want to start development work on a new build revision. The script would duplicate the production sequences (both parent and children) and repoint the "Run Task Sequence" steps to new "DEV" child sequences.

    This would automate the process and ensure that none of the production sequences…

    19 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. Allow "Delay enforcement" according to grace period in New-CMSoftwareUpdateAutoDeploymentRule

    allow setting "delay enforcement of this deployment according to user preferences, up to the grace period defined in client settings" check box via New-CMSoftwareUpdateAutoDeploymentRule

    15 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 →
  12. Unify Powershell Functionality

    The recent Powershell features like 'Run Script' and allowing them to be added directly to a Task Sequence step are fantastic, but things are beginning to feel somewhat fragmented.

    It would be great if SCCM had a central script repository, maybe backed by git, that we could pull scripts from as opposed to adding them.

    This would allow us to easily use the same code in a Task Sequence and a 'Run Script' without having to maintain it in multiple places. Perhaps we could even add a special Powershell Script Package Program type that would pull a script from the…

    14 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    completed  ·  0 comments  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  13. PowerShell Redistribute Content

    Create a PowerShell cmdlet that will redistribute (not refresh) content on a specific distribution point

    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 →
  14. invoke-cmclientnotification improvements

    In 1602 support in the Admin Console GUI was added for additional client notification triggers.

    https://blogs.technet.microsoft.com/manageabilityguys/2016/03/29/whats-new-with-configmgrs-client-notification-feature/

    However there is still a gap in the functionality for this cmdlet. Currently as of 1706 you are still only able to invoke user and machine policy per the documentation:

    https://docs.microsoft.com/en-us/powershell/sccm/configurationmanager/vlatest/invoke-cmclientnotification

    11 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. Updates and servicing - Powershell CmdLet

    Working for a company with several Configmgr hierarchies, it would be great with a PowerShell cmdlet to initiate and control the updates and servicing.

    11 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 →
  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…)
    1 comment  ·  PowerShell  ·  Flag idea as inappropriate…  ·  Admin →
  17. New-CMSoftwareUpdateAutoDeploymentRuleDeployment missing -RequirePostRebootFullScan option.

    The New-CMSoftwareUpdateAutoDeploymentRuleDeployment command is missing the -RequirePostRebootFullScan option. This should be added similar to the New-CMSoftwareUpdateDeployment command.

    10 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 →
  18. SCCM 2012 R2 - PowerShell Commandlet needed to remove Updates from Group (Add-CMSoftwareUpdateToGroup exists)

    Hi all, my customer is using the PowerShell on a really high level to automate nearly all his ConfigMgr Patchmanagement Tasks. They are using Add-CMSoftwareUpdateToGroup but they're missing the matching Remove Commandlet.

    10 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. Set-CM<Type>DeploymentType fails with Invalid Property when updating Content Location

    Since I updated to 1706, any of the Set-CM<Type>DeploymentType cmdlets fail with an error when I try to update the content path/location to another location. Based on the error message, it seems the cmdlets need to have extra parameters added to handle the separate Install and Uninstall content paths/locations. Perhaps you could add -UninstallContentLocation and a switch for -UninstallContentSameAsInstallContent.

    Set-CMScriptDeploymentType : Invalid property: object Application(ScopeId8C35D19A-F107-4878-83CC-9E26B213220D:Applicationa463d8c5-c106-43ae-993b-f5bcb2f4ae4c:15) property
    DeploymentTypes.DeploymentTypes[0].Installer.Installer.UninstallContent: Uninstall Content not found in Contents collection
    At line:54 char:3
    + Set-CMScriptDeploymentType -ApplicationName $cmApplicationNa ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo          : NotSpecified: (:) [Set-CMScriptDeploymentType], InvalidPropertyException
    
    + FullyQualifiedErrorId : Microsoft.ConfigurationManagement.ApplicationManagement.InvalidPropertyException,Microsoft.ConfigurationManagement.Cmdlets.AppMan.Commands.SetScriptDeploymentTypeCommand

    9 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 →
  20. 7 votes
    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 →
← Previous 1 3 4
  • Don't see your idea?

Feedback and Knowledge Base