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. 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 →
  2. Status message

    It would be usefull to allow the creation of StatusMessages for any event.
    This could be tuned in DefaultClientSettings (just as hinv classes), but setting it only thru PSH would be a first step.

    For example, when a user requests an app:

    new-CMStatusMessageDefinition -class "SMS_UserApplicationRequest" -event "CreateRequest" -messageid 33333 -strings ($ciid,$username,$devicename,$usercomment...)

    Best regards

    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 is a complicated problem, and not one we plan to address at this time. There are some solutions today with varied levels of usability.

    We do have a special status message class on the client designed for some extensibility: SMS_UnknownMessage. You can specify custom values for this and have it get processed by the management point. The management point has a list of status message types it accepts, and we have no mechanism for extending this at this time. You can also have a component that writes custom status messages directly to the site server inbox. You could theoretically write whatever you want here, but you need to take care to ensure that this is properly secured and monitored since you need to be a trusted user to write to the status inbox.

    Keep in mind that even if you do get custom status messages processed by the site,ā€¦

  3. Add PowerShell cmdlet to update Application Catalog icons in Software Center.

    Add cmdlet to update Application Catalog icons in Software Center.

    We currently store icons in the root of the app content folder and manually right-click on the Application object located in \Software Library\Overview\Application Management\Applications.

    Then we click the Aplication Catalog tab and click the Browse button to browse to an update icon.

    This manual works, but having the ability to automate via a cmdlet automated would allow a mass update and could make it easier when transferring or integrating ConfigMgr ecosystems in the event of a merger or acquisition.

    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 →
  4. 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 →
  5. Make client CIM methods work over WinRM

    Currently using Invoke-CimMethod will fail on remote clients unless you use a CimSession with a CimSessionOption specifying the DCOM protocol.

    The server side classes work great with CIM cmdlets, it'd be great if there were parity there with the client classes, especially since PowerShell 6.0 doesn't include the WMI cmdlets that people will gravitate toward to use DCOM.

    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 →
  6. 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 →
  7. 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ā€¦

  8. Allow New-CMTaskSequenceMedia cmdlet to add empty variables

    When creating Task Sequence Media with the Admin Console, you have the ability to create empty variables. However, when you attempt to do the same thing with the New-CMTaskSequenceMedia PowerShell cmdlet, you get this error:

    New-CMTaskSequenceMedia : The variable value should not be empty.

    Sample code:

    $TSVariable = @{ 'OSDComputerName' = '' }
    New-CMTaskSequenceMedia -StandaloneMedia -TaskSequenceDistributionPoint $TSDistributionPoints -MediaPath "$TSMediaPath\$($TaskSequence.Name).iso" -MediaInputType CdDvd -MediaSize SizeUnlimited -TaskSequence $TaskSequence -Variable $TSVariable

    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 →
  9. Orchestrator Powershell V4

    Since SCORCH isnt that public its very hard to find a good solution. So we have only Powershell v2 for Orchestrator and that makes it hard for a none scripter to find easy solutions. All around work with v4.

    Our first step with SCORCH: deactivate 100day unused PCs and move them to a folder and delete them after 1 month after movement.
    HORRIBLE!
    With user accounts its even more complicated.

    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 →
  10. 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 →
  11. 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 →
  12. 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 →
  13. 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 →
  14. Run Scripts: A Copied and pasted powershell script from SCCM to Powershell ISE, will not run in the ISE

    I tried to edit a PS script in the ISE environment. The script began with a simple variable assignment i.e. $A = get-item... but the script would error : The term 'A$=" is not recognized as the name of cmdlet... Typing the identical line above or below would work. Almost like the copying and paste process used a different character set.

    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. Add NumberOfDependedDTs property to Get-CMApplication

    Currently, the only place to see NumberOfDependedDTs is from Get-CMDeploymentType. Other properties like NumberOfDependentDTs and NumberOfDependentTS have been propagated to the Application Level, it would be useful to have NumberOfDependedDTs too.

    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 →
  16. [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 →
  17. 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 →
  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. 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 →
  20. 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!

← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base