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.

For the new feature in 1702 ("Check for running executable files before installing an application"), add a countdown timer pop-up above the system tray, like the countdown for restart, but in this case to allow the user to save any unsaved work before the specified executables get automatically closed.

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

If you have e.g. Oracle as dependency set for ~50 applications and a new version is available, you have to manually update all 50 deployment types with this new dependency version.

If you only supersede it, the main applications which are using this as a dependency do not show up in softwarecenter anymore.

There must be a possibility to have an overview of dependent applications and update all of them with one click or exclude some for certain reasons.

In SCCM, it is possible to show Software Depedencies for an application. However, it is not possible to show applications which depend on a specific application (i.e. which applications depend on Oracle Client, Java Runtime, Microsoft .NET etc.). This would be valuable to decide whether the application can be retired.

Peter van der Woude provided a PowerShell based solution in 2013 which could be used as a starting point:
https://www.petervanderwoude.nl/post/showing-dependent-applications-in-configmgr-2012-via-powershell/

Please add an option in the Application Model to auto uninstall the application after xx number of days. This could be linked to Software Metering. This would be extremely beneficial to manage applications for license reclamation as well as removing vulnerable applications from the environment.

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.

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.

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

it would be very helpful for the overall user experience if it would be possible to use html or any kind of formatting in the localized description.
currently the description is not shown very pleasant...

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.

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.

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.

Current behavior is that application icons need to be specified in Application Properties. Wouldn't it be great to pull the app icon from the app content if it is available? This would save a lot of time for environments where application icons are a requirement.

Currently, application detection method scripts are ran in such a way that it causes issues with certain levels of PowerShell Constrained Language Mode. An example of how scripts are run is below.

"C:\WINDOWS\system32\WindowsPowerShell\v1.0\PowerShell.exe" -NoLogo -Noninteractive -NoProfile -ExecutionPolicy Bypass "& 'C:\WINDOWS\CCM\SystemTemp\11a53fac-8144-438e-aa01-6d2378be848b.ps1'"

To better allow detection method scripts to be ran under Constrained Language mode, the script should be ran with -File instead of with the call operator &.

With the current configuration it is not possible to use PowerShell based detection methods in some scenarios, reducing their usefulness.

See this idea for more info. https://ideas.patchmypc.com/ideas/PATCHMYPC-I-440

We need the ability to easily see which application is included in which application group.

This could be done similar to dependency references in the "References" tab of the application.