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. PowerShell Cmdlets without console

    Currently you have to install the ConfigMgr console in order to use the powershell cmdlets. It would be much easier to manage these cmdlets if the dependency on the console was removed. After all you might want to install this on a server which is designed to manage code which runs server core.

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    The Cmdlet Library is tightly coupled with the administrator console and the engineering investment to decouple them doesnā€™t make sense at this time nor is this something we are likely to ever do.

    The console was developed before the cmdlets (unlike products like Exchange, VMM, and MDT which have PowerShell underpinning the console) which means to truly ā€œfixā€ this we would need to literally flip the entire console design from being PowerShell built on top of the console to the console being built on top of PowerShell. Itā€™s pretty obvious that this would be a massive undertaking and we simply donā€™t have the engineering resources to do this. If at such time we decided to re-architect the console we would definitely ensure PowerShell is a first class citizen in the design.

    As a workaround today, you can use PowerShell remoting to connect to a machine that has the administratorā€¦

  2. Powershell cmdlets on client machines

    Currently, PS cmdlets are only available on machines where the Console is installed. However, there are many things that an admin may want to do that would be made a lot easier if a large subset of those commands where available on the client machines. This would especially be helpful when running scripts during a Compliance Item, but would also make an impact during OSD Task Sequences, or Packages that deploy and run scripts to perform actions, etc.

    Examples would be to query/modify collection membership during a script on the client, set primary user from client based on some criteriaā€¦

    19 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    I’m marking this as declined to return votes back to folks.

    This isn’t something we plan on addressing. The main problem as mentioned before is that the PowerShell cmdlets require SMS Provider connectivity to work, and that in turn requires having a certain level of trusted site server access for the account executing the cmdlets.

    We do support PowerShell remoting so you can run cmdlets from another machine that has the administrator console installed without having to install the console on the client machine that you’re currently connected to.

  3. Powershell - Return TopConsoleUser

    Get-CMTopConsoleUser -Computer MyPC

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    declined  ·  1 comment  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  4. 6 votes
    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 →
  5. invoke-cmdevicewipe

    One of my client asked me to create a script to automatically selective wipe a mobile device that have not connect since 2 months.

    I tried with invoke-cmdevicewipe but I can't do selective wipe. This powershell command is for a full wipe only.

    It is possible to add a switch to this cmdlets or a new one to selective wipe a mobile device?

    I also tried invoke-cmdeviceretire and it's not doing what they want.

    Thanks

    5 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 →
  6. Allow for SDK process to add to hardware inventory

    I want to be able to add business data to computer resources in ConfigMgr, without the need to populate hardware inventory on the client.

    I want to use the SDK to add additional properties/tags - things like production/nonprod, warranty information, application grouping, etc.

    5 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 →

    There’s two approaches you can do to this today.

    The most simple approach is by sending a custom DDR with additional properties. See: https://blogs.msdn.microsoft.com/ameltzer/2014/10/02/sdk-creating-ddrs-on-the-site-server-using-the-client-messaging-sdk-part-2-creating-system-ddrs/ for more details on this.

    The second approach is to extend hardware inventory. See: https://blogs.msdn.microsoft.com/ameltzer/2013/04/10/sdk-creating-custom-inventory-classes-for-clients-with-the-client-messaging-sdk/ for more details on how to do this.

    I hope that this addresses your needs!

  7. Improuving Powershell cmdlet performances

    I have written thousands of powershell lines to manage SCCM from powershell. I really don't understand why powershell cmdlets are so slow comparing to wmi ones. I really suggest to try to improve it.

    4 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 →
  8. Publish ConfigurationManager module to the PowerShell Gallery

    It would be really great if you would start leveraging PowerShell Gallery as a place to publish latest versions of ConfigurationManager module (cmdlet library). Even though the module can't work without the Console, it would still be a lot more handy to rely PowerShell Gallery to make sure I'm running the latest version of cmdlet library.

    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 →
  9. Windows Explorer and Notepad improvements.

    I would like to suggest Microsoft the following improvement initiatives regarding the Windows platform:

    1. In Windows Explorer: I suggest updating the "date modified" information of a folder based on the last change performed on its files. For example, if a file is overwritten, deleted, copied-into, or updated, the "date modified" information of that folder should reflect that change.

    2. In Windows Explorer: When copying files from the local hard drive to a removable storage device (e.g. USB memory), the files are not copied with the correct "date modified" information. This happens during summer time for files modified during winter time. Theā€¦

    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 →
  10. PowerShell in GUI - Remove AllSigned or Digitally Sign the Module

    When running the PowerShell Cmdlets from within the GUI in System Center Configuration Manager it forces a confirm before it allows the Console to run. The problem is simple as the Console is being run with "allsigned" as the executionPolicy but the Module is NOT Digitially signed. Change the launching ExecutionPolicy to Bypass or Digitally Sign the Module (either would resolve the issue)

    3 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 →

    Unfortunately there’s not enough actionable information provided here for us at this time.

    All of our PowerShell modules should be signed. You may initially receive a prompt to accept the signer of the modules, but beyond that they should function as expected in AllSigned mode.

    If you’re not seeing this, please let us know the exact error you’re seeing along with the product version you’re using so we can dig deeper into this issue.

    Thanks!

  11. Add "System OU Name" to get-cmdevice cmdlet

    Add "System OU Name" to get-cmdevice cmdlet.
    This is helpful information when troubleshooting and collecting information on multiple devices.

    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 →
  12. write the Client MP and DP configurations in registry or WMI

    I have multiple MPs and DPs that are assigned to a client.

    From the client (not using the servers or SQL) I cannot find a way to tell what the MPs and DPs are assigned in the Boundaries?

    currently I can pull current management point with the following PowerShell:
    $sms = new-object ā€“comobject ā€œMicrosoft.SMS.Clientā€
    $sms.GetCurrentManagementPoint()

    Can you write them to the registry or WMI?

    maybe something like this ...

    ManagementPoints\MPServer1
    \MPServer2
    \MPServer3
    \MPServer4

    DistributionPoints\DPServer1
    \DPServer2
    \DPServer3
    \DPServer4
    \DPServer5
    \DPServer6

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    declined  ·  1 comment  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  13. Add credential parameter for all PowerShell module cmdlets

    Add credential parameter for PowerShell module cmdlets to allow cmdlets to be run from alternate credentials, such as a service account. This would be very useful for passing a credential asset to a runbook in Azure Automation.

    3 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 →
  14. Allow Wildcard for cmdlets Get-CMPackage and Remove-CMPackage

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

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    declined  ·  0 comments  ·  SDK, PowerShell, and tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  15. Invoke-CMReport with parameter

    it would be good if the Invoke-CMReport gives us the option to pass parameters to the report. today it only open the report and that's it, you need to manually. another parameter that could be added would be to automatically export, so you don't actually need to open the report, just export the data

    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 →

    Invoke-CMReport supports parameters today with the ReportParameter parameter. It’s a hashtable so you set it with key-value pairs like this:

    Invoke-CMReport -ReportPath “Client Status/Client status history” -ReportParameter @{ Collection = “MyCollection”; “Time Range” = “4 weeks” }

    The ability to export reports is unfortunately out of scope for our cmdlets as this is a function of the reporting web site. You could probably use something like Invoke-RestMethod once you know a report URL to export it through automation.

  16. set-cmcollection does not terminate on name collisions with errors in -errorvariable and doesn't seem to work with try/catch

    If we could get this functionality it would go a long way in automating collection management.

    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 →
  17. Support Center Log File Viewer - manage columns

    Hello,

    it seems its not possible to manage the columns. For example I don't need to see the column called "file name". This is possible in CMTrace.

    Thanks.

    MK

    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 →
  18. improve Get-CMUser command

    at the moment, Get-CMUser command is returning only few parameters, this command is querying RESCOLLSMS00002 table which is not populated with many information about user. But the command itself is prepared to deliver more parameters. Can we expect this to be improved? to populate this table with more information or query smsruser for more details... like user attributes taken from AD.

    This would be very helpful with any automation scripts, if we don't need to query AD or WMI class for them.

    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 →
  19. [RFH] Computer restart requirement parameters in powershell are swapped

    While setting Computer restart settings in the console requires the notification dialog box display value (for example 1440) must be greater than the countown dialog box value (for example 120), in Powershell it is swapped and the following fails:

    Set-CMClientSetting -Name "Default Client Agent Settings" -ComputerRestart -RebootLogoffNotificationFinalWindowMins 1440 -RebootLogoffNotificationCountdownMins 120

    This way in Powershell it is not possible to set the correct values except if you swap the parameters:

    Set-CMClientSetting -Name "Default Client Agent Settings" -ComputerRestart -RebootLogoffNotificationFinalWindowMins 120 -RebootLogoffNotificationCountdownMins 1440

    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 →
  20. Client Actions Command line rights

    the client actions (on the client) that can be performed via the UI (control panel applet) should be allowed to be performed by a normal user via powershell.

    if you try to triggerschedule as normal user, you get access denied

    $SMSCli = [wmiclass] "root\ccm:SMS_Client"
    $SMSCli.TriggerSchedule("{00000000-0000-0000-0000-000000000021}")

    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 →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base