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. Show Powershell equivalent command(s) at any wizard completion

    At wizard completion for anything, show the Powershell cmdlet equivalent like in other System Center products.

    1,322 votes
    Vote
    Sign in
    (thinkingā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    24 comments  ·  Admin Console  ·  Flag idea as inappropriateā€¦  ·  Admin →
  2. Software Center "Sort by" default view

    Change default "sort by" order from "Most recent" to Alphabetic list (Application name A-Z). Or remember the setting for the client. Or allow a SysAdmin setting for site-wide default setting. It always resets back to Most recent.

    287 votes
    Vote
    Sign in
    (thinkingā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    12 comments  ·  Software Center  ·  Flag idea as inappropriateā€¦  ·  Admin →
  3. When a console crashes and you are editing a task sequence, allow sedo unlock if user name matches yours

    It happened to me yesterday with SCCM 1602 CB, I was editing two task sequences at the same time, trying to copy a section from one into the other when the console crashed. I needed the work done and this didn't help as as soon as I started the console again I got the familiar message shown below. The problem is you have to wait 30 minutes for the sedo lock to be removed or use PowerShell cmdlets to try and remove the lock.

    I don't think that is necessary at all as there is already a retry button onā€¦

    207 votes
    Vote
    Sign in
    (thinkingā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  10 comments  ·  Admin Console  ·  Flag idea as inappropriateā€¦  ·  Admin →
  4. ADR Available Deployments

    I would like to see ADR's support the creation of Available deployments in addition to Required deployments. We have some business cases where a certain subset of servers are aren't allowed to "push" software updates to until the server/app owners have verified the patches.

    The issue is that these servers don't have connectivity to the internet so we have to deliver them via ConfigMgr. By creating an Available update using an ADR, it streamlines our ability to "deliver" the updates to all systems, and allow the Patching Team, or App/Server owner to patch according to their own business schedules.

    201 votes
    Vote
    Sign in
    (thinkingā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    19 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  5. DSC to replace or compliment basline feature

    DSC is a wonderful framework for handling baseline configurations across Windows and Linux machines, but it's completely unsupported in SCCM directly. While a Pull server is certainly more simplistic than an SCCM hierarchy, it would still be very beneficial to have some integration in a couple of areas:

    Management Points can easily be configured to host mof configurations for clients, and a new client policy class for allowing the SCCM agent to configure the pull server settings on a host would be great. Alternatively a new role could be made ... not sure that would feel as elegant.

    The baselineā€¦

    164 votes
    Vote
    Sign in
    (thinkingā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    2 comments  ·  Compliance Settings  ·  Flag idea as inappropriateā€¦  ·  Admin →

    This feature will evolve from the “run scripts” features that first showed up in ConfigMgr 1706 tech preview. It lets you build a library of powershell, and execute them on demand. We will evolve DSC capabilities into this feature too.

  6. Emergency/Immediate halt or pause of a software deployment then resume a software deployment when needed.

    In SCCM, there should be a way to stop or discontinue a software deployment should there be an emergency or issue and then resume the deployment when desired. For example, if software has been deployed to the environment and in an event of an emergency or major issue, SCCM should allow the administrator to stop or pause the software deployment in real time, resolve the issue then restart the software deployment again. Ideally, this would accomplish in one push of a button. Unlike now, the administrator goes and deletes the deployment and recreates the deployment again leaving the inability toā€¦

    99 votes
    Vote
    Sign in
    (thinkingā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  5 comments  ·  Client Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  7. Task Sequence Pre-Cache for all Packages inside

    It would be nice to have the ability to conditionally pre-cache all packages in Upgrade TS and not only OS Upgrade step.

    To describe it in more details, in current design we are able to pre-cache only OS Upgrade step to computers based on conditions. This is not enough for companies with 20+ languages as best approach is to create en-us core image and then apply MUI on top of that. Doing this will cause system to report as e.g. de-de so we would need to download and distribute to 150+ DPs all supported Upgrade packages instead of distributing onlyā€¦

    78 votes
    Vote
    Sign in
    (thinkingā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    8 comments  ·  Operating System Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  8. Complex scheduling: Enable patch deployments to servers based on SDLC (Dev / QA / Prod / DR)

    Based on Patch Tuesday, allow application / business owners to select appropriate down time for the server as well as a sequenced order (e.g., Development servers during the first week after Patch Tuesday, QA on the second week after Patch Tuesday, Production servers on the third week after Patch Tuesday, et cetera). This allows the business owners to "own their own destiny" and get systems administrators out of the business of coordinating patching maintenance windows. In addition, the ability to insert "change freezes" that force the schedule to increment all downstream targets out by an additional week to compensate forā€¦

    64 votes
    Vote
    Sign in
    (thinkingā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  9 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  9. Request full control over allow/disallow force closing of Office 365 apps when installing updates instead of force closing Office apps

    In ConfigMgr 1610 Update Rollup 1 provided the change so Office 365 Updates did not force close any office applications when Office 365 patches were installed through ConfigMgr Software Center.
    https://docs.microsoft.com/en-us/sccm/sum/deploy-use/manage-office-365-proplus-updates#restart-behavior-and-client-notifications-for-office-365-updates

    With ConfigMgr 1706 we require the option to disallow force closing of office 365 applications when patches are installed through the ConfigMgr Software Center.

    49 votes
    Vote
    Sign in
    (thinkingā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  2 comments  ·  Software Updates  ·  Flag idea as inappropriateā€¦  ·  Admin →
  10. Ability to enable/disable any deployment (like you can with software update deployments)

    You should be able to enable or disable any deployment (for applications, packages, software updates, etc) by right-clicking and selecting enable or disable.
    Currently to disable an application deployment you either have to delete the deployment or retire the application and for packages you need to disable the program.
    Software update deployments already have this feature.
    You should also be able to enable/disable a deployment from the Monitoring workspace.

    46 votes
    Vote
    Sign in
    (thinkingā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  1 comment  ·  Admin Console  ·  Flag idea as inappropriateā€¦  ·  Admin →
  11. OSUninstall - Make ConfigMgr Aware of going back to previous builds

    Please Make CM aware if an OSUninstall (Reverting to previous Build) has happened, so it can heal itself into a functional state. Currently if you perform an OSUninstall from say 1809 to 1709, after you've upgraded originally to 1809 using a CM Task Sequence, the CM Client is non-functional.
    Client is in Provisioning Mode, Services are disabled, and once you fix that, it thinks it's int he middle of the Task Sequence and shows the Upgrade TS "Installing", so then you need to clear that out.

    Please make OSUninstall & CM Play Nice together, so we can offer users theā€¦

    39 votes
    Vote
    Sign in
    (thinkingā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    3 comments  ·  Operating System Deployment  ·  Flag idea as inappropriateā€¦  ·  Admin →
  12. PowerShell Cmdlet for Modifying Nested Task Sequence (Get/Set-CMTSStepRunTaskSequence)

    It would be very helpful to have a cmlet that will allow you to modify the "Run Task Sequence" with PowerShell.

    I'd like to be able to script replicating an entire task sequence "suite" (including all of the nested sequences) and re-linking the new nested sequences.

    My use case is something like this:
    I want to start development work on a new build revision. The script would duplicate the production sequences (both parent and children) and repoint the "Run Task Sequence" steps to new "DEV" child sequences.

    This would automate the process and ensure that none of the production sequencesā€¦

    16 votes
    Vote
    Sign in
    (thinkingā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    1 comment  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  13. 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ā€¦

    11 votes
    Vote
    Sign in
    (thinkingā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  14. 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ā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    3 comments  ·  Troubleshooting & Support  ·  Flag idea as inappropriateā€¦  ·  Admin →
  15. 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ā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  2 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  16. Make CM Pivot usable at the CAS level

    Make CM Pivot usable at the CAS level

    8 votes
    Vote
    Sign in
    (thinkingā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  0 comments  ·  Admin Console  ·  Flag idea as inappropriateā€¦  ·  Admin →
  17. Update CM cmdlet documentation and downloadable help file

    Running update-help pulls down a help file to an older version of the cmdlets. For instance, do a clean install of the console and cmdlets.
    Type:

    Get-Help Add-CMApplicationCatalogWebsitePoint

    On a machine that has not had the help file updated, you will see 6 parameter sets under Syntax. Run update-help and then try again. You will now see 2 parameter sets under Syntax. In addition, there is no detailed information for the new cmdlets added.

    7 votes
    Vote
    Sign in
    (thinkingā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  3 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  18. 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ā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  2 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
  19. 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ā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  0 comments  ·  Collections  ·  Flag idea as inappropriateā€¦  ·  Admin →
  20. 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ā€¦)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinkingā€¦)
    planned  ·  0 comments  ·  PowerShell  ·  Flag idea as inappropriateā€¦  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base