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.
If you require assisted support, please see https://aka.ms/cmcbsupport for more details.
-
Application supersedence for user deployments
At the moment application supersedence is only working with machine deployments. Please make this work for user deployments.
6 votes -
Application supersedence for user deployments
At the moment application supersedence is only working with machine deployments. Please make this work for user deployments.
0 votes -
Detection method for MSIX Apps should have version 'Greater than or Equal' option
Current detection method for MSIX native Deployment Type only allows us to check version equals to 1.x.y.z.
If that application is set to auto install updates afterwards the software center application status turns to failed. I experienced this after deploying Microsoft Whiteboard application, when I deployed to my user base app deployment was successful for over 5000 machines and deployment success status was almost 99%. After 2 weeks users complained they see Failed status in Software Center next to Whiteboard application. After troubleshooting the issue I came to know whiteboard application was set to install automatic updates and the version…
1 vote -
Add "Favorites"/Pre-Defined Dependencies to Dependency Settings in Applications
I use application dependencies a lot and in general this works well in my environment. Setting them up is currently a bit cumbersome because you need to create the dependency then add the applications/deployment types to the dependency. I find that there are some dependencies that I use very commonly (Visual C++ Redistributables, .NET) where I'm always setting up the same dependency for different apps.
Instead of manually having to do this for each application, it would be nice to save these dependencies somehow so they could easily be added from a saved list. Perhaps the console could remember recently…
2 votes -
windows source management
Allow multiple "Product Code" separated by a comma, in the "Windows Source management" under Deployment Type - Program tab.
This would be helpful for such MSI with sub storage streamed in. Those MSI change their Product Code on the fly during installation depending on language detected.
2 votes -
windows source management
Allow multiple "Product Code" separated by a comma, in the "Windows Source management" under Deployment Type - Program tab.
This would be helpful for such MSI with sub storage streamed in. Those MSI change their Product Code on the fly during installation depending on language detected.
0 votes -
Deployment option for CMG available/required apps
It would be useful to us for an option, similar to allowing application to run via task sequence, that would let us select which applications we would want users to see/install via the CMG. Currently most apps we use are deployed as available to all users but only a select few have the content distributed to our CMG and so causes problems when users try to install and ConfigMgr waits to download content.
0 votes -
Prioritize application installation/removal and hold reboots until all deployments are complete.
I worked with Radia for many years. Two things from Radia we miss are the ability to set priority and holding reboots until the end of all deployments. For priority, we could set a value of 1 to 99 on an application. Anytime there were multiple deployments to a device they would be performed in low to high number priority order for install and reverse for uninstall. Uninstalls would occur first. We could also set reboot=reallysuppress in any msiexec command line and set a flag on the application to reboot on install, uninstall, update, etc. Radia would then wait until…
1 vote -
Add the "Version" data type to registry key detection methods
Most modern applications e.g. Microsoft 365 Apps, store their version with a period in the value(e.g. 13127.20408) which makes the key a string and not an integer. When deploying updates to applications I would like the ability to say the version is greater than or equal to a number which is only possible with integers. In Global Conditions there is extra Data Type options and one is "Version", this allows the periods in version values to be treated as decimal points and manipulated like an integer.
3 votes -
Wait for second reboot in custom tasksequence
The docs say that SMSTSWaitForSecondReboot variable does not apply to custom task sequences. That is true, unfortunately.
A few customers use custom tasksequences to update application bundles and the variable could help here.
The problem: Software Updates (Cumulative W10 etc) have been installed during the day, reboot is pending until next maintenance window. Maintenance window opens at night and starts task sequence for application updates. Task sequence has a reboot step or app install forces a cm hard reboot by exit code 1641. Now when the system reboots, the task sequence may fail on startup because of a second reboot…1 vote -
Application Approvals - Add support for webhooks
I would love to see support for sending Application Approvals via webhooks, whether by specifying specific apps (Teams, Slack, Discord), or being able to define a JSON schema so that folks who live in Teams/Slack/etc all day can more easily see App Requests come into a channel and be able to click Approve.
For Teams, at least, this should allow for the use of an AdaptiveCard payload, too, which could potentially capture the response from ConfigMgr and update the card in the Channel to show that it's already been Approved/Denied.
1 vote -
Pre-deploy software to user primary device on application groups
Actually there is no way to Flag application groups to pre-deploy on user primary device
It would be great to have like on application deployment the capability to flag the groups to install on primary user device
15 votes -
Allow the option to set maintenance windows against application & software update deployments
Would be nice if we were able to create maintenance windows against software application and update deployments.
This could be really useful for large planned deployments such as Win 10 feature updates without affecting current patching update deployments.
1 vote -
TLS 1.2
How about the average Joe who just wants to use TLS 1.2 and download whatever is needed? A link to what is a simple fix would be nice.
1 vote -
Icon database - Once icon is added to application the first time, make it available for further use
Having all the icons within internal database would make the process of creating applications and specifically newer versions of applications smoother if we had the option to choose icon we have already imported previously rather than go browsing from some corner of your drive.
1 vote -
Required Software notification
We would like to be able to remove the "Outside my business hours" option on the required software changes notification added in 1902. This option requires users to understand the difference between maintenance windows and business hours which can be confusing. This is even more confusing if you disable the options tab in Software Center so that the "Configure Business hours" option doesn't work.
25 votes -
Include a time delay in the SCCM Application Dependencies Tab
When adding dependencies to an appliaction is would be good to set a time delay between it and the application being installed.
I have had an instancing in a current project that 2 applications need a time delay otherwise they do not recognise each other as being installed. The only way that this can then be resolved in to uninstall both then install one and then other while waiting for required time of 5 minutes.
9 votes -
Application deployment and "Maintenance window" settings cause the application to kill
-Problem overview
If you deploy the application under the following conditions, the running application will be killed immediately after the download phase.
The customer has set "Maintenance Windows", and the problem is that the application is killed at a timing outside the "Maintenance Windows" range.This behavior is reproducible. (Confirmed with MECM 2002) I want to confirm whether this behavior is a by design or a known issue.
-Repro step
1. Set "Maintenance Windows" to the device collection. The next step is to set the installation deadline before entering "Maintenance Windows".In the application's Deployment Type properties, on the Install…
43 votes -
Add "Repair" as possible action in the Application Deploy software Wizard
When deploying an application as required it is only possible to install/uninstall the application. It would be an idea to add the "Repair" action in this wizard. Why, you could use the repair action to do tasks you previously did with a legacy package on a scheduled base. We have this script that installs the application but also contains a part that changes user files. That part needs to be done on a scheduled base. This would be beneficial because then one script can contain all actions and can be made required by the deployment withou reinstalling the application.
1 vote -
Add support for MSP
Please add support for creating an application installation for MSP files so I don't have to write custom batch files anymore
1 vote
- Don't see your idea?