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. Add -RebootBehavior option to Set-CM<Type>DeploymentType

    In previous command Set-CMDeploymentType is was possible to set reboot behavior but in the new Set-CMScriptDeploymentTYpe and SetCMMSIDeploymentType it is not an option.

    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 →
  2. 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 →
  3. 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 →
  4. 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 →
  5. Improve command Get-CMApprovalRequests

    add filter to return values based on current status. right now for any automation we need to report thousands of requests and filter them by Where-Object.

    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 →
  6. Fix Support Center on running app deployment eval cycle remotely

    When Support Center runs App Deployment Evaluation cycle locally, it uses Schedule 121, which is OK. However, when itā€™s connected to remote machine, it uses Schedule 123, which was deprecated at some point.

    Future release of Support Center should always use schedule 121.

    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 →
  7. Add-CMScriptDeploymentType -AddDetectionClause "OR" functionality

    It would be helpful to have the ability to select OR as a Connector Value (which only has 2 states AND, OR) for the AddDetectionClause of Add-CMScriptDeploymentType
    The best example of this is when trying to create a ConfigMgr Client Update application. The client has a different GUID depending on whether it is x86 or x64.

    Why am I making a separate application deployment for the client upgrade as opposed to the built in one? The built in one will not use the files local to itself and pull the entire content accross the WAN again. So building an applicationā€¦

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Support for advanced detection clauses was added in 1810.

    Example:
    PS PS4:\> $cla1=New-CMDetectionClauseFile -FileName filetest -PropertyType Size -ExpectedValue 123 -ExpressionOperator IsEquals -Path C:\ -Value -Is64Bit
    PS PS4:\> $cla2=New-CMDetectionClauseFile -FileName foldertest -PropertyType DateCreated -ExpectedValue (Get-Date) -ExpressionOperator LessThan -Path C:\ -Value
    PS PS4:\> $cla3=New-CMDetectionClauseRegistryKey -Hive ClassesRoot -KeyName aaa
    PS PS4:\> $logic1=$cla1.Setting.LogicalName
    PS PS4:\> $logic2=$cla2.Setting.LogicalName
    PS PS4:\> $logic3=$cla3.Setting.LogicalName
    PS PS4:\> Add-CMMsiDeploymentType -AddDetectionClause $cla1,$cla2,$cla3 -ApplicationName app -DeploymentTypeName dt -InstallCommand mycommand -ContentLocation “\\127.0.0.1\C$\CCMTools\Orca.Msi” -GroupDetectionClauses $logic1,$logic2 -DetectionClauseConnector {LogicalName=$logic2;Connector="or"},{LogicalName=$logic3;Connector="or"}

  8. Add filters to the cmdlet Get-CMSiteStatusMessage

    The cmdlet Get-CMSiteStatusMessage needs additional filtering capabilities beyond the severity of the message such as the MessageID and the Component. In a large site the cmdlet returns way too many records and already exceeds the quota violations before you are able to filter the results using Where-Object. Similar like theĀ“FilterHashTable parameter the Get-WinEvent cmdlet provides.

    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 →

    We are improving this cmdlet for 1702 in the following ways:

    • Add FilterHashtable option like Get-WinEvent to add ad-hoc filtering
    • Add wildcard support for all filter parameters
    • Add array support for filter parameters
    • StartDateTime no longer mandatory (will default to 24 hours)
    • Add native ability to filter on MessageId, Module, and Component
    • ComputerName no longer requires successful DNS resolution for the specified name

    These changes should be in the next technical preview. We hope you like them!

  9. Allow prevent autoload of CM psdrive

    Rather than have to invoke PowerShell via the ConfigMgr console, I prefer to just load the module into my existing session/console.
    The issue is that on load, the module auto-creates a PSDrvie with the CMSite provider using my current credentials.
    This is an issue because my "normal" account has pretty limited rights in ConfigMgr (by design), and I'd prefer to "connect" to ConfigMgr via PowerShell using my "admin" account.

    I'm thinking the least impactful way to do it would be for the module to honor an environment or pssessionpreference for "NoAutoCreatePSDrive" or the like (rather like the AD module) andā€¦

    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 →

    This work has been completed for 1710.

    Docs are in the process of being published.

    Do disable auto-load of the PSDrive, create the following registry key:
    HKEY_CURRENT_USER\Software\Microsoft\ConfigMgr10\PowerShell

    Create a DWORD value called DisableCMDriveAutoCreate and set to 1 to disable auto-creation or 0 for default behavior. Deleting this registry value also restores default behavior.

    Note that by disabling CMDrive auto-creation, the PowerShell window created from the admin console will write errors and will not be useable until you manually load the ConfigurationManager.psd1 module.

    We are planning an additional change into 1802 where will write a warning to the console when importing the ConfigurationManager.psd1 module if this setting is enabled for additional awareness.

  10. 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 →
  11. 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 →
  12. 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 →
  13. 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ā€¦
  14. MVP-Powershell client settings for software center

    add a new Set-CMClientSetting to customise software center. today the only way is to use the props SettingsXml for SMSSCIClientComp (SoftwareCenter) WMI and create a xml to configure it.

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

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

    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 →
  17. CM Messaging SDK Documentation shouldn't be a .chm help file AND...

    The docs that exist for the CM Messaging (note, the messaging SDK is not a part of the larger CM SDK docs here https://msdn.microsoft.com/en-us/library/hh442686(v=cmsdk.16).aspx) is currently a .chm Help file, which is lovably nostalgic.

    However it doesn't do justice to the power of the SDK. For instance, Discovery and hardware inventory are barely covered in the SDK docs. I'm troubleshooting an issue now with the Messaging SDK in which a fake CM Client appears with Windows 6.2 NT Workstation, even though it is a fully patched Win10 machine. Weird stuff.

    Anyway, it would be great if the docs wereā€¦

    0 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 →
  18. Set-CMProgram should support operating system requirements

    Add the possibility to set an operating system requirement on program for legacy package. The cmdlet set-cmprogram has no switch for that.

    0 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 →
  19. Included canned powershell scripts

    Include canned scripts for creating collections applications and deployments with the ability to create a template from selections.

    0 votes
    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 →
1 2 3 5 Next →
  • Don't see your idea?

Feedback and Knowledge Base