Ideas

One of the pain points in patching is we have to manually create collections for each application we want to target for patching. Some type of option to automate this creation would be helpful.

Add the ability to use a custom detection method to better detect when the app is installed or look at other methods of detection and not just a registry key or file version. I believe the detection is already prepackaged with an app, can that be ...

The ability to use a custom install script for advanced installs such as detecting OS type and adjusting install location based on Server OS or Workstation

Please can you add the app "Remarkable Desktop" to the Application Manager catalog so we can automate patching of this app. https://support.remarkable.com/s/article/Desktop-app

MCM supports On-Demand Distribution. We'd like to be able to set that from RMS in Patching > Deployment Processes.

It would be nice if admins could prevent dependencies from being added. Give us the ability to manage whether or not the dependency is necessary in the environment.

As a sys admin, I want to run my deployment process using schedule (not when the new version is released)

I would love to be able to disable Desktop icons from appearing when apps are installed or updated, similar to what Ninite does with the /disableshortcuts switch. We often don't want to advertise that a new product has been installed when the user...

I would like to define how many previous application version I want to keep as retired before removing the application/installation media from ConfigMgr.

Can you please add newest versions of Webstrom and Mongo DB applications