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.
If you require assisted support, please see https://aka.ms/cmcbsupport for more details.
-
Improved automation and extensibility by exposing Configuration Manager functionality through a REST web API
Exposing Configuration Manager functionality through RESTful web API's would open up a whole new world for interacting with ConfigMgr.
E.g. a web Admin console and easier integration with Service Management Automation (SMA).
It should also be easier for 3rd party vendors to create new web based solutions for say an self-service portal or a Windows App for tracking an OS or application deployment on a mobile device or phone.
Personally I would really like any easier way to interact with ConfigMgr. when running in Windows PE (OS Deployment) or a web portal for non-admins to provision new or existing machine…155 votesstarted ·AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, Microsoft Endpoint Configuration Manager) responded
This is now available in the 1612 Technical Preview.
-
Expose v_Update_ComplianceStatusAll in WMI
Expose SMSUpdateComplianceStatusAll in addition to SMSUpdateComplianceStatus to allow 3rd party tools to differentiate between 'Not Required' and 'Unknown' compliance states for software updates.
59 votes -
Expose Task Sequence Engine Component Properties in Status Message Rules for Automation
It would be nice to have the Properties available to pass to an External Script the same way the Insertion Strings can be.
What I was specifically trying to accomplish in this case is Adding a Computer to a Collection during a OSD Task Sequence for the Purposes of Software Updates. I created a Status Message Filter Rule that looked for a Client State Message ID 11140 (The task sequence execution engine started execution of a task sequence.) for a Specific Package / Task Sequence. This all worked as expected and launched the external command when the TS Launched (and…29 votes -
Introduce a CLI for Client Peer Cache
The new client peer cache functionality is great and we are currently evaluating whether it can replace our current alternate content provider.
The main functionality that is missing in Client Peer Cache is a CLI or API that can be used on the SCCM client to download a specific content id.
It would be great if we could launch a command or cmdlet to trigger the download of content using client peer cache and if that is not available download from the DP.14 votes -
Improve and document the AdminUI.ConsoleBuilder tool
A lot of customers would like to customize their admin consoles to add some missing views, columns and actions. For example, displaying User device affinity in Devices list or vice versa.
AdminUI.ConsoleBuilder is a good tool for this but it is very unfriendly and there is zero documentation on it.
It would be great if you add docs on it and improve the tool itself
13 votesNoted ·AdminMark Silvey - ConfigMgr Product Team (Engineering Manager, ConfigMgr, Microsoft Endpoint Configuration Manager) responded
Thanks for the suggestion!
-
Configuration Manager Properties tool Show Actions Status
The Control Panel app Configuration Manager Properties tool is an easy way to manually start client side actions on PCs. However you have no way to tell that the action worked unless you dig through numerous log files. A simple status message next to each command would allow you to see what is currently running on the client and when each step last completed. Would greatly speed up troubleshooting time and allow non SCCM admins a way to tell what is actively running.
13 votes -
SCCM Primary users and ADDS msds-primarycomputer attribute
Please have a way to integrate to keep the two attributes in sync
10 votes -
Allow the built-in CM Client package to be enabled for Alternate Content Providers (ACP)
The built-in CM Client package is a predefined package and is locked/read-only. Alternate Content Providers (ACP) such as 1E Nomad are not able to officially enable this built-in package for distribution by Nomad.
This request is to formally allow and support the built-in CM Client package to be enabled for content distribution by ACP's.
This would require the ability to set the AlternateContentProvider property of the built-in CM Client package.10 votes -
Support for the new Boundary model in Microsoft.ConfigurationManagement.Messaging.dll
The Messaging.dll only Support the old Boundary model for content requests and MP request. We need support for the new boundary model.
6 votesNoted ·AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
We will definitely look into adding support for the recent additions to location requests integrated into the messaging SDK for a future release.
-
Custom Catalog
Each Company want's to have a 'software' catalog and be able to customize it the way they want.
Having one mandatory software center, even a new one, does not fill this need.
I believe the model with a WebSite and a Web Service like the sofware catalog should be extend for the whole applications, even applications actually targeted with the use of the software center.
At the moment, informations are acquired by wmi and also by the catalog web service, and it does not make it easy to develop our own catalog.
6 votes -
Running ConfigMgr Control Panel applet actions should ignore throttling settings
When running an action from the ConfigMgr control panel applet, e.g. "File Collection" or "Software Inventory" the action should be executed immediatley and not respect the throttling settings. Internally it should be handled differently whether an action is triggered by the scheduler or an user.
6 votes -
Allow Console Extensions to access the Connected Site Code and Connected Server
Allow Console Extensions to access the Connected Site Code and Connected Server when launched from areas in the console that aren't IResultObjects. When an extension is launched from a node such as Applications or Packages, we no longer can use the ##SUB:Server## or ##SUB:Namespace## fields. Similarly for assembly based extensions, the IResultObject is null and we can't get at the IResultObject.ConnectionManager property.
5 votesNoted ·Admindjam (Product Director, or Executive, Microsoft Endpoint Configuration Manager) responded
This makes total sense. Great ask.
-
Switch to next SUP - scripted on client
ConfigMgr agents are able to fallback to an alternative SUP if the original SUP failed - agents do not fallback to the original SUP once it’s available again. In this case fallback needs to be triggered manually. This can be done from the console using „client notification“ – wouldn’t it be good to also be able to force SUP fallback on the client itself? Document a script method to switch to the next SUP that can be run on the client itself.
5 votes -
Graphical Overhaul for end user facing elements.
Make every user facing graphical element of SCCM extensible so that modern GUI Frameworks can be leveraged to improve the user experience SCCM should look like slack or Microsoft teams or any other beautiful GUI that is presented on Modern desktops
5 votes -
Allow third-party code to read secret task sequence variables value
Currently there is no way to use Secret Task Sequence Variables in third-party extension to SCCM. Please, add API for this or document how to achieve this.
5 votesUpdated by bobmn for sangeev/OSD
-
Allow third party applications or scripts to send status messages in WinPE
Currently we have the ability to post status messages in the OS, but not under WinPE. We'd very much like to be able to report on Nomad download progress during the WinPE stage of the deployment in order to true up the new Nomad dashboard with this part of the deployment process.
4 votes -
Make "client notifications" scriptable
Administrators can use the "client notification" feature from the admin console to trigger actions clients. This is a very useful feature - it would be even more useful, if this actions could be scripted. Pls. document how to script "client notification" actions.
4 votes -
Standardize package properties between SMS_TaskSequence_* SMSProviderObjects
SMSTaskSequenceRunCommandLineAction uses PackageID
SMSTaskSequenceInstallApplicationAction uses AppInfo (and ApplicationName?)
SMSTaskSequenceApplyDriverPackageAction uses DriverPackageID
SMSTaskSequenceApplyOperatingSystemAction uses ImagePackageID
SMSTaskSequenceUpgradeOperatingSystemAction uses InstallPackageIDWhile they are different objects and they do different things, shouldn't this be standardized across classes that can have content dependencies in a TS? This makes the data coming out of Get-CMTaskSequenceStep difficult to work with, as you have to keep a rolling library of properties to check for Package ID's.
3 votesNoted ·AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
We wouldn’t fix the backing WMI schema because that would introduce breaking changes to any SDK consumers.
We could consider a fix on the PowerShell side to allow for more consistent display of these objects (without changing the objects themselves) to make them easier to consume via automation.
-
Log to ETW
It would be handy if SCCM Agent (as well as the SCCM Server components) could send logs to ETW (instead or in addition to the files under C:\Windows\CCM\Logs) folder. That would allow us to redirect the events to a central location and analyze with event analysis tools, (i.e. OMS Log Analytics, Message Analyzer, etc.).
3 votesplanned ·AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
This is something that’s on our backlog.
-
Client Messaging SDK: Parse client inventory messages to a local file for debug purposes
If you play around with the possibility to send messages like inventory, ddr,... with the Microsoft.ConfigurationManagement.Messaging.dll it would be nice to write the message to a file on the lokal development system (for validation / verify purposes) instead of sending it over the wire to get the result.
3 votesNoted ·AdminAdam Meltzer (ConfigMgr Product Team) (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Thank you for your feedback.
In the short term, can be worked around by implementing your own instance of IMessageSender and using this to send the message.. In this custom sender, you can handle the message any way you want.
We will consider adding this as built in functionality to the SDK in the future for advanced debugging scenarios.
- Don't see your idea?