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. PS Cmdlet Operating System Upgrade Package handling

    The PS Cmdlet currently offers options to manage Operating System Images but not Operating System Upgrade Packages.

    It would be great if corresponding Functions could be added:
    Get-CMOperatingSystemUpgradePackage
    Get-CMOperatingSystemUpgradePackageUpdateSchedule
    New-CMOperatingSystemUpgradePackage
    New-CMOperatingSystemUpgradePackageUpdateSchedule
    Remove-CMOperatingSystemUpgradePackage
    Remove-CMOperatingSystemUpgradePackageUpdateSchedule

    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  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  2. PowerShell Script status

    1. Take me right to script status after running the script.

    2. Under Script status after deploying script allow for filtering/export/reporting.

    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  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  3. Making PowerShell Cmdlets Discoverable in SCCM

    Presently the PowerShell Cmdlets for SCCM require use from the console or running a separate script like below.

    Import-Module "$($ENV:SMSADMINUI_PATH)..\ConfigurationManager.psd1" # Import the ConfigurationManager.psd1 module
    Set-Location "$((Get-PSDrive -PSProvider CMSite).Name):" # Set the current location to be the site code.

    An alternative would be two options (Neither means re-writing the Configuration Manager console.

    One. Create a shortcut to launch the above script as a "PowerShell Configuration Manager Console"

    Two. Leverage some variant on a solution found here on the TechNet Script Repository which drops in a Hardlink with MKLINK pointing to the Configuration Manager BIN folder with the correctā€¦

    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  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  4. Change temporary unpack path of Support Center Viewer

    If i open a "Bundle" in Support Center Viewer all the data gets stored in:
    C:\Users<USER>\AppData\Roaming\Microsoft\ConfigMgrSupportCenter.Common\Temporary

    It woul be nice to Change that path or to provide a path during the unpack procedure. Right now i have alsmost 8GB of data in that path and it seems to not clean up by itself.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    completed  ·  0 comments  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  5. Filter for Datetime "between" for Support Center Logfile Viewer

    I would be great to have a between Filter for Datetime in the Support Center Logfile Viewer.
    Like this:
    Include: 2017-03-08 11:00:12.323 <->2017-03-09 09:00:12.323

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    completed  ·  0 comments  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  6. Boundary Group - Add/Remove/Set Site System

    create a new powershell cmdlet to allow add/remove/set a site system to a boundary group

    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  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  7. New-CMDetectionClauseWindowsInstaller Missing Braces in Product Code

    When an MSI detection rule is created with New-CMDetectionClauseWindowsInstaller, and applied to a Deployment Type with Set-CMScriptDeploymentType, the product code in the detection rule is missing the braces. This causes the detection rule to fail to detect an application that is actually installed. The application is successfully detected after adding the surrounding braces to the product code in the SCCM console.

    2 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  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  8. Run Script under System context

    The new Script functionality in the console allows deployment to a machine, but runs at USER level, not SYSTEM. We adhere to best practise and users are not admins, thereby limiting its utility for admin functions.

    It also prevents us from running cleanup scripts which require the system context (specific case is stuck BITS transfers initiated by CCM)

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    completed  ·  0 comments  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  9. Add a Copy-CMTaskSequence cmdlet

    With the console you can create a copy of a task sequence, but there does not appear to be a direct way of doing this via powershell. This would make staging image changes much easier.

    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  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  10. Allow parameters to "Run Script"

    When using the "Run Script" against a collection allow the script to accept parameters.

    2 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    4 comments  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  11. Save-CMSoftwareUpdate Applet - Add a Retry parameter

    I would like to see a parameter added to the Save-CMSoftwareUpdate applet, that allows us to specify how many times the applet should retry downloading patches that fail to download.

    Currently if a patch fails to download, the applet moves onto the next patch without retrying, which induces administrator activity post-execution, or complex scripting to determine patches that are not downloaded and retrying them again.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  12. Powershell cmdlet to download all software updates in a Software Update Group

    There are Powershell cmdlets to create software update groups and to add software updates to a specific software update group but no cmdlet to download all the updates in a software group - this has to be done manually

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    completed  ·  3 comments  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  13. Start-CMApplicationDeployment

    the Start-CMApplicationDeployment cmdlet should have a parameter for Automatically Update Supersedence, like on the UI.

    currently the only workaround would be doing via WMI directly
    $Deployment = Get-WmiObject -Namespace "root\SMS\site$($SiteCode)" -Class "SMSApplicationAssignment" | Where-Object { $.ApplicationName -like "$AppName" -and $.CollectionName -like "$CollName"}
    $Deployment.UpdateSupersedence = "True"
    $Deployment.Put()

    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  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  14. Remote powershell for SCCM

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

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  15. Resultant Client Settings

    add a get-CMResultantClientSettings so we can be able to check what the client should have by powershell without need of the 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ā€¦)
    1 comment  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →

    As of 1610, we now have Get-CMResultantSettings

    NAME
    Get-CMResultantSettings

    SYNTAX
    Get-CMResultantSettings -Name -SettingsType {Device | User} [-Setting
    {BackgroundIntelligentTransfer | Cloud | ClientCache | ClientPolicy |
    ComplianceSettings | ComputerAgent | ComputerRestart | EndpointProtection |
    HardwareInventory | MeteredNetwork | MobileDevice | NetworkAccessProtection |
    PowerManagement | RemoteTools | SoftwareDeployment | SoftwareInventory |
    SoftwareMetering | SoftwareUpdates | StateMessaging | UserAndDeviceAffinity}]
    [-DisableWildcardHandling] [-ForceWildcardHandling] []

    Get-CMResultantSettings -Id -SettingsType {Device | User} [-Setting {BackgroundIntelligentTransfer | Cloud | ClientCache | ClientPolicy | ComplianceSettings | ComputerAgent | ComputerRestart | EndpointProtection | HardwareInventory | MeteredNetwork | MobileDevice | NetworkAccessProtection | PowerManagement | RemoteTools | SoftwareDeployment | SoftwareInventory | SoftwareMetering | SoftwareUpdates | StateMessaging | UserAndDeviceAffinity}] [-DisableWildcardHandling] [-ForceWildcardHandling] [] Get-CMResultantSettings -InputObject -SettingsType {Device | User} [-Setting {BackgroundIntelligentTransfer | Cloud | ClientCache | ClientPolicy | ComplianceSettings | ComputerAgent | ComputerRestart | EndpointProtection | HardwareInventory | MeteredNetwork | MobileDevice | NetworkAccessProtection | PowerManagement | RemoteTools | SoftwareDeployment | SoftwareInventory | SoftwareMetering | SoftwareUpdatesā€¦
  16. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  17. Invoke-CMDeploymentSummarization

    the Invoke-CMDeploymentSummarization should have an option to pass the software name as paramenter. the only option would be using deploymentid, but to get the deploymentid we need use get-cmdeployment, but this does not help if you want to run the summarization before running the cmdlet. having -collection -softwarename would be a great addition

    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  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  18. New-CMSoftwareUpdateAutoDeploymentRule missing switch (EnableFailureAlert)

    SCCM admins would like to have a switch added to New-CMSoftwareUpdateAutoDeploymentRule cmdlet to allow them to generate an alert when the ADR rule fails.
    See screenshot below

    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  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  19. Add more discovery details to the Get-CMDevice commandlet

    When looking at the properties of a device, many attributes are included. For example, MAC address is an attribute that appears in those properties. When using the Get-CMDevice PowerShell commandlet though, these extended properties are not displayed.

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →

    Get-CMDevice returns instances of SMS_CollectionMember. Changing the output of this cmdlet is very likely to be a breaking change, and collection/device cmdlets like this are our most heavily used. Therefore there’s too much risk in changing the behavior here.

    Fortunately, all is not lost. Several releases back we introduced a new cmdlet, Get-CMResource which will return the raw resource objects from WMI. “Get-CMResource -ResourceType System” will return SMS_R_System objects and this should give you what you want. Get-CMResource output can still be pipelined into other collection cmdlets.

    For more information, see: https://docs.microsoft.com/en-us/powershell/sccm/configurationmanager/vlatest/get-cmresource

  20. Get-CMSiteMaintenanceTask pipeline to Set-CMSiteMaintenanceTask

    Before upgrading a CM Site, it is recommended to ensure that no maintenance tasks are running - it would therefore be useful to disable all of them during an upgrade "just in case" and would prevent the need to check the run time of each one.
    There's a Get-CMSiteMaintenanceTask, but I cannot store this as a variable and use it in the "-MaintenanceTask" argument of Set-CMSiteMaintenanceTask. I've been through the properties to look for a suitable one to explicitly pass to the argument, but nothing seems to work......

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    3 comments  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base