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. Create folders under "Deployments"

    Allow the creation of folders under "Deployments"

    31 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  2 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  2. Integrate a References tab on Application objects

    Application objects should have a References tab that is identical in functionality to the References tab on Task Sequence objects.

    The current References tab in an Application object's properties is very limited (Shows App dependencies, App Supersedence, and Virtual Environments).

    30 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  4 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add BITS Priority settings for Package ans Application

    BITS job is creates as LOW priority when deploy package or application, but Software Updates download are launched with a BITS priority NORMAL and software updates download prior to package or applications.

    If it take a long time to download QU/FU and user want to deploy package or app immediately during client download QU/FU, users cannot do it as far as downloading QU/FU due to the difference of BITS priority.

    Add BITS Priority settings for Package ans Application in this scenario.

    36 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  4. Office 365 Installer - Detection Method

    Office 365 Installer - Detection Method
    When creating an application for Office 365 using the built-in "Office 365 Installer" feature, the application gets created with a default detection method that only uses the version.
    So, if you create 3 separate applications (Office, Project, and Visio), or if you create Applications with different languages, they all have the same detection methods.
    So, if you install Office first, you can't Visio or Project.
    The detection method should include a product and language:

    Examples:
    SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\VisioProRetail - da-dk
    SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ProjectProRetail - da-dk
    SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\O365ProPlusRetail - da-dk

    29 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add grace period to delay detection method for installers that exit too quickly

    Many application installers spawn child processed and then exit before actually finishing, causing Detection Method to fail. The solution widely used right now is to wrap the installer in a script and use some kind of "sleep" function. It would useful to have an optional parameter on the "detection method" tab to delay the detection check for up to 'x' seconds/minutes after the installer exits.

    Note: we can sort of do this now by forcing a reboot after the installer exits; the computer will restart and run detection check afterwards, but this just leads to a lot of longer installs…

    27 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  6. Automatically Close

    Thank you for the Auto close of the executable specified on the install behavior, the problem I have is chrome.exe, aftre the application closes, it starts the install, if the user just starts it up again, it continues to run again, leaving 2 versions installed, chrome.exe, and new_chrome.exe, with the request to admin credentials to update, corrupting the installation

    Can we add to the Automatically close, keep closed until installation returns a Zero

    26 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  7. Package ID in Application list

    Everytime I have an error in the "Distribution Point Configuration Status" I have to search for the "failed" application with the Package ID in the "Content Status". This works very slow! Please show the "Package ID" in the Appliaction List of the Console.

    26 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  2 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  8. Retiring Applications

    Allow 'Retiring' applications that in fact stop being deployed, without having to remove the 'Deployments' that contain tracking data about their previous installations.

    26 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  3 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  9. Trigger Hardware Inventory After Installing Applications

    Many ConfigMgr administrators set aggressive hardware inventory cycles for their client citing the need to keep an up-to-date inventory for the applications installed on their company's assets. Aggressive inventory cycles can obviously have a negative impact on site performance, and very often is unnecessary as there are frequently no changes to the inventory. Administrators can perform a work around by using wrappers or run additional programs to initiate a hardware inventory post install, however this causes an administrative overhead to installing applications.

    I propose adding an option to application/package deployments that would trigger a hardware inventory after a successful installation.…

    25 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add Install Behavior to Uninstallations

    As stated above, the Uninstall command should be forced to check if an executable is running via the Install Behavior tab, same as installations. I could see some cases where you'd want it to uninstall anyway, so maybe a checkbox could be added on how to handle this.

    Right now if a user clicks "uninstall" or if Supersedence is set to run an uninstall, the application will just begin the uninstall. This isn't ideal, as If the old version of software is uninstalled, it will typically crash the application, and then the new version would begin installing to the horror…

    25 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow MSI Source locations to use DP's configured for HTTPS

    I recently ran into an issue with an MSI that we have deployed which required access to its installation source during a patching operation, and discovered these two problems. We worked around the issue by pinning the content in the ccmcache.

    On the application deployment properties, SCCM can automatically update the source location windows installer uses for a detected MSI product code. However, it appears that windows installer is unable to use https source locations, only http.

    Another issue I have seen is that the windows installer source list gets appended (not replaced). As a client roams between content boundaries,…

    25 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  2 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  12. Application Catalog Requirements

    It would be extremely useful for the application catalog to display the reason why the application cannot be installed in terms of requirements. The generic requirement failure message is confusing to users and overall is not meaningful. If the hard drive doesn't have enough space it should say there is not enough space. Not having a meaningful failure message generates extra help-desk tickets.

    24 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  13. Option to use SYSTEM context for detection method for a user-based application deployment

    The application detection method only runs in the user context if it is deployed to a user collection. This would be reasonable if the Deployment Type user experience were set to "Install for User" (User context), however the detection method runs in the user context when this is set to "Install for system" installation behavior (SYSTEM context).

    24 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  3 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add support for Status MIF reporting with Application Model

    Packages/Programs in ConfigMgr support use of Status MIF reporting while the Application Model does not. Status MIFs can provide for more accurate and detailed status reporting, particularly for deployment execution failures. For this reason, some customers have been reluctant to transition to the Application Model.

    The Application Model relies on exit codes for determine success/failure of deployments.
    Disadvantages of depending on exit codes:

    Success exit codes (0, 3010, etc.) do not always indicate successful installation; failure exit codes do not always indicate failure

    Exit code 0 does not always indicate that the installation succeeded, but rather only that the installer…

    23 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  2 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow obscuring of all or portions of the SCCM installation command-line

    I would like to see an option added to SCCM to allow obscuring portions of the installation command-line. This functionality would be particular useful for application installations like Microsoft SQL Server Express which accept an argument to the setup.exe specifying a clear text password.

    The benefit of obscuring the password would be that the SCCM logs (i.e. appenforce.log) would not have a clear text version of the password which could be opened and read by any user having access to the c:\windows\ccm\logs folder.

    23 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add support for MSU files in Application Catalog

    From time to time msu quick engineering hotfixes need to be deployed to machines. It would be helpful if you could import the msu files just like an MSI then deploy using the application catalog. Another option would be to add support to software upgrades.

    23 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  17. Applocker Management

    Fully integrate AppLocker into SCCM similar to how you do for SCEP. Would be great to be able to create AppLocker rules and monitor what get allowed and disallowed.

    23 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  18. BITS Priorities for User Initiated Deployments

    Test in 1606: For User launched Application deployments (i.e Software Center) , the BITS job is created as FOREGROUND priority which can hog all of the available bandwidth on the machine.

    Package/Programs downloads are launched with a BITS priority of LOW – please can we standardize on this for all user initiated content downloads.

    23 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  6 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  19. Phased Deplyments for Available applications with supersedence

    Phased deployments are great, but we have lots of users, with lots of applications that are nor required, but are superseded.

    Say we have 100,000 users, 50'000 have an application installed that has an update. We don't want a required deployment as not everyone has the application, and we don't just want to deploy the update to the application to 50,000 in one go. so this feature would be nice.

    23 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add "uninstall application" as an dependency option when creating applications

    An example could be when users want to install 'Office 365 x64' on a machine which has 'Office 365 x86' installed. For the 1. to be installed the other should be uninstalled.

    23 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  2 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base