A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:
Many clients face issues when republishing apps with new customizations using Publisher, as the new configurations/settings do not apply if the user already has the same version of the app installed.
This proposal suggests adding an option to reinstall apps even when the same version is detected but with different customization settings. The solution would involve implementing an extra randomised registry key/value that can be used as a one-time detection mechanism. By setting and checking this key/value, we can determine if the app should be reinstalled with the updated customization.
For example, perhaps the Publisher could contain a right-click option "Reinstall" where this would create a new ConfigMgr App, or Intune App/Update, with the current settings and the one-time registry/key in the detection script.
In addition, with the new package, this will enable customers to leverage the supersedence feature where customers can explicitly uninstall the software first (if necessary) before reinstalling the new package with the desired configurations. This will help in situations where an install-over-the-top does not work, and instead, an explicit uninstall is necessary.
In this end this approach will help ensure that republished apps with new configurations can be applied effectively, even if the app version remains unchanged.
Benefits:
Ensures new app customizations are applied without changing app versions.
Provides a flexible and simple solution to address a common client issue.
Can be integrated with Intune supersedence for streamlined detection and reinstallation.
Good idea with the randomised registry key. It could be a GUID registry value under a subkey for each application ID, so that uninstalling the app could also wipe away all config records for that application by deleting one key.