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.
-
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.
-
Custom Key Value pair for all objects
Add the capability of creating any number of custom key value pair instances with a unique property to differentiate between vendors / identities. For instance, let us be able to create instances in a class like SMS_ObjectCustomFields or something and associate them with an object, for instance Packages. This would for instance provide us with a "labeling" or categorization capability for objects like Packages, Configuration Items etc.
Some requirements:
- Unique identifier per identity / vendor
- Maximum character length for Value property, 1024
- Being able to associate the Key/Value pair with an object
- Key property cannot be…3 votesplanned ·AdminBob Mac Neill (Software Engineer, Microsoft Endpoint Configuration Manager) responded
Thanks for the suggestion. Updating status to Planned – see https://blogs.technet.microsoft.com/configmgreng/2016/03/11/configmrguv/
Making as planned since we’ve added two new properties for Driver Packages. These are for Manufacturer and Model and can be seen in recent 1810 Technical Preview – https://docs.microsoft.com/en-us/sccm/core/get-started/technical-preview
- Don't see your idea?