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.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Unify Powershell Functionality

    The recent Powershell features like 'Run Script' and allowing them to be added directly to a Task Sequence step are fantastic, but things are beginning to feel somewhat fragmented.

    It would be great if SCCM had a central script repository, maybe backed by git, that we could pull scripts from as opposed to adding them.

    This would allow us to easily use the same code in a Task Sequence and a 'Run Script' without having to maintain it in multiple places. Perhaps we could even add a special Powershell Script Package Program type that would pull a script from theā€¦

    12 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  2. Integrate the features of the SCCM Client Center into console

    The third party application SCCM client center provides essential troubleshooting support for the client. Why not integrate the features into the Admin console?

    10 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    3 comments  ·  Troubleshooting & Support  ·  Flag idea as inappropriateā€¦  ·  Admin →
  3. Transaction support for PowerShell cmdlets

    today when using powershell cmdlet the action is performed direct against the server, as example, if you want to create an application, add couple of deployment types and perform other small changes, you end up with lots of revisions (easily, 10). when you have lots of revisions, this start to impact the performance.

    it would be nice if we can have the cmdlets transactional, in this case, you create the object and the changes does not apply to the database, you need to "save" the change.

    on the application example, you could create the application, create the dt's, changes, etc.ā€¦

    9 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  2 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  4. TSProgressUI.ShowMessage - Enable Output

    Can you add Output to the ShowMessage Method Please.
    https://docs.microsoft.com/en-us/sccm/develop/reference/core/clients/client-classes/iprogressui--showmessage-method

    You currently have the ability to create a Message Box with several Options for the Buttons, but no matter what you pick, or options you choose, you never get anything actionable.

    Current Actions:

    0 - Ok
    1 - Ok/Cancel
    2 - Abort/Retry/Ignore
    3 - Yes/No/Cancel
    4 - Yes/No
    5 - Retry/Cancel
    6 - Cancel/Try Again/Continue

    If you could have it Create a Variable upon the end of the step
    SMSTSShowMessageOutput = "ButtonName"

    Which then would supply one of the following Values:

    Ok, Cancel, Abort, Retry, Ignore, Yes, No, Retry, Tryā€¦

    7 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Operating System Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  5. PowerShell cmdlet "Remove-CMMaintenanceWindow" should accept Window Time as parameter

    Powershell cmdlet "Remove-CMMaintenanceWindow" should accept StartTime as a parater. Current implementation only accepts limited parmaters of collectionid, and maintenance window name. If you have two windows by the same name, with different start times... you will remove both by using this utility. I suggest it should also accept the StartTime as a paramter for specific window deletion. Maintenance windows are a point in time schedule, and therefore the Point in time should be considered as a parameter for removal. The current implementation of this cmdlet is dangerous, and cannot be used for finite window removal.

    5 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  2 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  6. Remove the option to deleted the members from a collect when the collection is deleted.

    It seem odd that since you multi-select and deleted user / computers that you would need to have a prompt to delete the users / computers when deleting the collection.

    The process should be if you need to deleted the users / computers and the collection.
    - Multi-select and deleted computers. If there is a large number users / computers blocks deleted if number excesses High-Risk deployment settings.
    - Deleted the Collection
    - If the collection is limiting another collection. Then prompt if that collection should be deleted too.

    4 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  0 comments  ·  Collections  ·  Flag idea as inappropriateā€¦  ·  Admin →
  7. Allow use if DeploymentID as identifier in Set-CMPackageDeployment and Set-CMSoftwareUpdateDeployment

    Set-CMPackageDeployment and Set-CMSoftwareUpdateDeployment do not allow DeploymentID as unique identifier. Instead you need to use e.g. programname and packageid.

    In the case of Set-CMSoftwareUpdateDeployment this requires DeploymentName which is not even possible to retrieve from Get-CMDeployment

    Please, allow DeploymentID as an option to identifying the deployment in these cmdlets.

    4 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  8. 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 →
  9. Select specific WMI classes or Logfiles in SCCM Support Center

    It would be nice to have the ability to select specific WMI classes or Logfies easily within the SCCM Support Center. Right now i have to edit the config XML and sometimes the support center crashes. That would Help if you try to pull files or classes for specific Scenario from Clients and you dont Need all of them.

    2 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  10. Change temporary unpack path of Support Center Viewer

    If i open a "Bundle" in Support Center Viewer all the data gets stored in:
    C:\Users\<USER>\AppData\Roaming\Microsoft\ConfigMgrSupportCenter.Common\Temporary

    It woul be nice to Change that path or to provide a path during the unpack procedure. Right now i have alsmost 8GB of data in that path and it seems to not clean up by itself.

    2 votes
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  Tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  11. Fix Support Center on running app deployment eval cycle remotely

    When Support Center runs App Deployment Evaluation cycle locally, it uses Schedule 121, which is OK. However, when itā€™s connected to remote machine, it uses Schedule 123, which was deprecated at some point.

    Future release of Support Center should always use schedule 121.

    1 vote
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  Tools  ·  Flag idea as inappropriateā€¦  ·  Admin →
  12. Run Scripts: Should be able to invoke from Deployment Status Node

    Run scripts brought a brand new model to handle client troubleshooting, but it can run from collections only.
    it would have been super useful to be able to run it on a machine\category from the Deployment Status node and then maintain clients with in progress \ unknown \ active \ inactive state.
    today when we have a list of computers who didn't report their status we need to manually create a collection with these clients to run a scripts and there's not even a built-in way to create a collection from the asset details

    1 vote
    Vote
    Sign in
    (thinkingā€¦)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  13. 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 →
2 Next →
  • Don't see your idea?

Feedback and Knowledge Base