Microsoft

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

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  6 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow retire or delete of an application that has deployment types that reference eachother

    We have a number of applications that contain deployment types that depend on each other. It is annoying that in order to retire or delete the application, each deployment type has to be deleted first

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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.

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  2 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  5. Make it possible to choose "Client Local Time" on all deployment types.

    1. When deploying an application as available, it will by default be set to UTC time in the scheduling section without the ability to change it to "Client Local Time"
    2. When deploying an application as required, it will by default be set to UTC time, unless I check the "installation deadline" then I get the abillity to choose "Client Local Time"

    Here in Denmark and other places in Europe UTC is a bit confusing, we always have to be aware of this when deploying applications eg. I want to deploy an application for the end users at 08:00AM then…

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  2 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  7. Deployment Evaluation Cycle detects manually installed applications (AppDiscovery.log) but does not reflect this status in Software Center

    Think about a KeePass application including a working detection method. Click "install" in Software Center, it installs and gets detected correctly.
    Now think about a user who manually installed the same KeePass version. The application is deployed to "any machine" as "available". So, this user get's it as well. But it never shows up as installed in Software Center unless I click one time on "install". Even running the "Application Deployment Evaluation Cycle" does not change the button to "uninstall" or list it as installed in "Installation Status". AppDiscovery.log shows the DeploymentType_blabla as "discovered".

    We're using SCCM 1802 with all…

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  11. Wake on LAN by maintenance window start time not deployment time

    WOL packets are sent when a required deployment's time to install is hit. It would be nice if we could also set this to wake up machines by maintenance windows, or have a maintenance window that wakes up computers. What is the use of waking up a computer at the deployment start time of 7PM if the computer's maintenance window doesn't start until 10PM?

    23 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  2 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  12. Source list URL path not relative to the MSI that was run

    Currently if you run an MSI using a wrapper, and the MSI is located in a subfolder, the source list reg keys get set differently.

    The path in HKEY_CLASSES_ROOT\Installer\Products\<product code>\SourceList\Net gets set to the relative path of the MSI at run time.

    The path in HKEY_CLASSES_ROOT\Installer\Products\<product code>\SourceList\URL gets set to the root content URL on the DP.

    This causes issues if the local cache has been removed or purged. The user can no longer perform a repair as the source path is invalid.

    Normally I'd say just uninstall and reinstall, but in the case of some CAD systems that can…

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  14. Pre-Cache all Available deployments (not just task sequences)

    Provide an option to pre-cache ALL available deployments, not just OS deployment task sequences.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  15. 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…

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  16. We need an Event based deployment versus Time based deployment

    Please put in Event based deployment versus Time based deployment based on file/registry/Event log change. The deployment date should be used as the absolute earliest the event could take place. The expiration date should still hold true.

    The action could possibly happen on a single device, but need to occur to devices within a boundary/collection.

    The usage scenario is when a computer device is being used in a 24 hour retail setting, and the maintenance window is dependent on when the retail location determines a time in which it can take such action. The retail store may only have a…

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  0 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  17. Export and Import Global Conditions

    Please allow us to export and import global conditions. The code exists somewhere since this can be done when exporting and importing applications. Bonus points for Powershell cmdlets.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  18. Allow priority ( order) between applications without dependancies

    For example, application with priority 100 will be install before application with priority 500.
    There is some case were dependencie is not sufficient / too strict.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  6 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  19. Enable/Disable Feature for Application Deployments

    Enable/Disable Feature for Application Deployments
    When a Deployment is created, it is Enabled by default and there is no way to Disable it. In the current state, a Deployment could get created incorrectly, resulting in a large number of computers in the company getting rebooted, unwanted software or blue screens (if its something incompatible for that platform). In SCCM 2007 we got around this by creating a "Disabled" program for each Package, then after an Advertisement was QA'd, we would associate the "Enable" Program with the Advertisement. This option is not available in 2012. Seems like a pretty simple feature…

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Noted  ·  1 comment  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  20. Allow setting of default icons in software center

    Split this item from a bigger umbrella item.
    This is to allow the changing of the default icons for all task sequences, or all package / programs in software center.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Application Management  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base