All ideas

Please add "Manage installation logging" to non-MSI installers when available. Although there are exceptions with badly built/scripted packages, most installers support setting a log path via command line switch and the programs installer builder ...

There are so many updates to this wonderful software that we would like to be able to automize our release of. Please consider.

The MSI based applications created by the publisher do not need the content when performing an uninstall. The content should be set to 'No uninstall content' for MSI.

OCR component for Bluebeam

This would be useful when you add additional command line arguments that require the full path to an INI file or any other license file during install.

Egnyte WebEdit enables users to select a file from the Egnyte web UI and automatically open the file in its native application

To fully automate the patchmanagement and installation for Adobe Reader

Use this description for Intune updates like it shows in SCCM updates: Instead of generic application description used in the Intune updates today:

Currently the maximum of 14 days is less than our production release of patches. We need this increase to be able to match our production patching deadline. For us at least 30 is needed.

When you publish the initial app version, and a new version comes along. I might have the need to keep the older version for 1 or 2 iterations while the update package I most likely are only interested in keeping the latest version in Intune.