Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

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 System Center 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 System Center Configuration Manager feedback site is moderated and is a voluntary participation-based project. Please send only feature suggestions and ideas to improve Microsoft 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.

How can we improve Configuration Manager?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add support to extend more areas of the console

    It would be nice to be able to extend the details tabs of for example the devices. What i would like to accomplish is a upgrade resistant way of having https://sccm-zone.com/extend-the-sccm-console-to-show-collection-membership-using-console-builder-c6db52b408d8. It could be added by default but it would be more useful if the console was able to merge any xml ontop of the original ones.

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  2. Ability to disable alerts on 3rd party products like TrueSight Operations Management

    The ability to disable MOM/SCOM alerting during deployments is nice but having the ability to disable alerting on 3rd party products (like TrueSight Operations Management) would be extremely helpful.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  3. Need SMS Provider class for collection rules

    Currently it is not possible to efficiently query for properties of a collection membership rule. In the SDK the membership rules are a lazy property of the collection and must be retrieved one at a time before they can be tested. This iteration is impossibly slow and inefficient. If there was a SMS_CollectionRule WMI class then one could use a join query to search for Collections based on rule properties. In a real world situation, this would enable tools to quickly select a collection and find which collections it is a member of. This is really needed where collections are…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  4. WMI class for_CollectionRule

    Currently it is not possible to efficiently query for properties of a collection membership rule. In the SDK the membership rules are a lazy property of the collection and must be retrieved one at a time before they can be tested. This iteration is impossibly slow and inefficient. If there was a SMS_CollectionRule WMI class then one could use a join query to search for Collections based on rule properties. In a real world situation, this would enable tools to quickly select a collection and find which collections it is a member of. This is really needed where collections are…

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add WSUS Catalog #s to a Supported SQL View.

    With the SQL view vSMS_SUPSyncStatus, there is a column SyncCatalogVersion. This column allows you to see what version of the WSUS (pronounced “W” “SUS”) catalog is available at each software update point (SUP). When troubleshooting CMCB environment with two or more SUP it is import to know what catalog is at each SUP server. The vSMS_SUPSyncStatus has many more details available to it as compared to any of the existing SUP SQL views.
    So why is this information important? Knowing Catalog version #, sync date, sync status, etc. helps when troubleshooting SUP issues. This also allows for a dashboards/reports to…

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  6. Grant Select to smsschm_users on all SQL Synonym

    When CMCB or even CM12 creates an Inventory class, it also creates a SQL Synonym too. These SQL Synonyms, are basically the same as the SQL Views, with one key difference, they don’t have the permission set to allow for smsschm_users “select” access on them. This means that low rights users will receive an error when uses.

    So what is this important? This is a great question, and the reason is that the behavior when importing sms_def.mof changes between CM07, CM12, and CMCB. The SQL Synonyms is named exactly what is created in older versions of CM. So When creating…

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  9. Standardize package properties between SMS_TaskSequence_* SMSProviderObjects

    SMS_TaskSequence_RunCommandLineAction uses PackageID
    SMS_TaskSequence_InstallApplicationAction uses AppInfo (and ApplicationName?)
    SMS_TaskSequence_ApplyDriverPackageAction uses DriverPackageID
    SMS_TaskSequence_ApplyOperatingSystemAction uses ImagePackageID
    SMS_TaskSequence_UpgradeOperatingSystemAction uses InstallPackageID

    While 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add a 'Dependency' Boolean property to SMS_TaskSequence_* SMSProviderObjects.

    Add a 'Dependency' Boolean property to the SMS_TaskSequence_* SMSProviderObjects that will settle whether or not any given step has resolved its content dependency. When you move Task Sequences between sites these dependencies aren't resolved and Task Sequence steps will reference content from your old site. This makes it hard to perform any kind of automated correction without writing very inefficient code.

    It doesn't have to be named 'Dependency' but Task Sequence SMSProviderObject that can have content dependency should also be able to tell you whether or not it's successfully resolved (mapped is maybe a better word? I don't know) when…

    3 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  11. Provide information on syntax errors for WQL queries

    If you attempt to write a WQL query that has a syntax error, then try to save it, you get a very vague "syntax error" message from SCCM.

    Please provide at least some information on WHY the syntax was flagged.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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.).

    0 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  14. Preserve ISVData field while copy/pasting Task Sequences in SCCM Console

    One SCCM extension uses SMS_TaskSequencePackage.ISVData to hold information about additional object properties. If an admin makes a copy of task sequence in Admin Console, the value of the SMS_TaskSequencePackage.ISVData gets ("Right-click Menu -> Copy"). The ISVData field value is empty in the copy.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow ISV proxy/client receive Task Sequence policies

    In our products' SCCM extension I've tried to get Task Sequence policies assigned to ISV proxy/client without success. After investigating, I've found out that ConfigMgr marks such policies with "secret" flag and don't allow them to be sent to ISV. Could you please implement a way to receive such policies by an ISV?

    Checked on SCCM 1702 (Site version 5.0.8498.1000)

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  17. SCCM Primary users and ADDS msds-primarycomputer attribute

    Please have a way to integrate to keep the two attributes in sync

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  SDK and Extensibility  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base