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. Make Get-CMPackage Return All Packages

    Currently, Get-CMPackage only returns ā€œordinary packagesā€, not software update packages or task sequence packages or other types. If you run the command in verbose mode, you can see the WQL query filters PackageType=0 and activity <>3.

    Documentation for this cmdlet states ā€œGet-CMPackage returns all packagesā€ and this is wrong. It returns all packages where type = 0. Can we please create PackageType as a parameter so all packages can be managed with one cmdlet?

    3 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 →
  2. Improve folder support in cmdlets

    Actually, it is possible to create a collection with a cmdlet. But we cannot create it in a specific location. We need moving it after creating the collection. Why not just add a parameter to the New-CMDeviceCollection cmdlet?

    20 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    8 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →

    Thank you for your feedback. Folder support is something that is very limited in the cmdlet library today and something that’s in our backlog to improve in a future release. In my opinion, I think the way things should work is if you’re in a collection folder in the cmdlet drive provider, it should just create the collection in the right place.

    I’ve linked this feedback to our internal work item to improve folder support so this doesn’t get lost.

    Thanks!

  3. Add /ResetBase to New-CMOperatingSystemImageUpdateSchedule

    Now that optimization of the WIM and removal of superseded updates is available as an option for offline servicing in the console, it would be great if this option could be added as a switch to the New-CMOperatingSystemImageUpdateSchedule cmdlet. I use this cmdlet to automate scheduling of updates in an ADG against all my WIMs so it would be great if I could shrink them down at the same time without needing to do this in the console.

    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 →

    Thanks for your feedback.

    Updating status to noted, see https://docs.microsoft.com/en-us/sccm/core/understand/find-help#send-a-suggestion for an explanation of each value.

    We’ve addressed this in our 1902 release as well as the ability to import a single .wim from the multi-index .wim.
    https://docs.microsoft.com/en-us/sccm/osd/get-started/manage-operating-system-images#BKMK_AddOSImages

    As Vlad mentioned, the New-CMOperatingSystemImageUpdateSchedule CmdLet has -RemoveSupersededUpdates

    I’ll update the status to completed if this addressed your ask. If not, then let us know any gaps.

  4. Phased deployment support for PowerShell cmdlets

    Phased Deployment Powershell Cmdlets

    28 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 →
  5. add a powershell possibility to add repair command to a deploymenttype of an application

    add a powershell possibility to add repair command to a deploymenttype of an application

    21 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 →
  6. Set-CMAutoDeploymentRuleDeployment to include missing AllowWUMU and AllowUseMeteredNetwork

    Although you can now add multiple deployments to a single Automatic Deployment Rule there a couple of options that can be read but not set. These are:

    "If software updates are not available on the distribution point in current, neighbor or site boundary groups, download content from Microsoft Updates."
    and
    "All clients on a metered internet connection to download content after the installation deadline, which might incur additional costs"

    I can successfully retrieve all Deployments associated with an Automatic Deployment Rule via the Get-CMAutoDeploymentRuleDeployment cmdlet and see the current settings for these properties by parsing the DeploymentTemplate XML.

    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 →
  7. Pass script parameters with Invoke-CMScript

    Allow the Invoke-CMScript to pass script parameters. This could be done with a ScriptParameter hashtable similar to how Invoke-CMReport functions.

    44 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 →
  8. 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 →
  9. Powershell 6.x support everywhere in SCCM

    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
    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. MVP-New-CMConfigurationItem / Set-CMConfigurationItem supported platform

    the New-CMConfigurationItem and Set-CMConfigurationItem should be able to set the supported platforms. today this is not possible to easily perform this task

    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 →
  11. ConfigurationManager PowerShell module should register itself as an Env Variable

    Today, when you install the CM Console, the PowerShell module will be placed under the %CMInstallDirectory%\AdminConsole\Bin\ConfigurationManager.psd1

    This makes sense given where the user is choosing to install the console, and that's fine. But placing it here off the beaten path means that it is not importable using PowerShell's module autodiscovery features. For instance, if a module is found in any of the standard user or system paths (or registered under the $ENV:PsModulePath) the user can easily import the module without having to specify the full path, a big user quality of life win. This is the way that SQL Serverā€¦

    85 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 →
  12. Save-CMSoftwareUpdate error RPC server unavailable when connecting under a different account

    My idea is to have the scenario described below supported.

    When running Save-CMSoftwareUpdate command on a CMSite-PSDrive that connects to a ConfigMgr site in a different domain (used Get-Credential to pass credentials in New-PSDrive call) than the user account the PowerShell window is running as, I get error 'The RPC server is unavailable'.

    I can successfully change location to the PS drive, and run other ConfigMgr PS cmdlets.

    Commands:
    New-PSDrive -Name <sitecode> -PSProvider 'CMSite' -Root <siteserverFQDN> -Credential (Get-Credential)
    Set-Location <sitecode>:
    Save-CMSoftwareUpdate -SoftwareUpdateName <name> -DeploymentPackageName <name> -Verbose

    Verbose output from Save-CMSoftwareUpdate call:

    VERBOSE: Start: Execution of WQL query: Select * fromā€¦

    12 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 →
  13. 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
    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 →
  14. 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 →
  15. 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 →
  16. 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 →
  17. 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 →
  18. 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 →
  19. 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 →
  20. 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 →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base