Event details
One major difference we noticed moving from config manager to intune is the detection if an app is 'installed' or not on a device.. it would be great if intune IME would be able to detect if an app is installed on an endpoint if the detection condition is satisfied for apps that is assigned as available for install, even if the app wasn't originally installed via intune / company portal.
an example is say if an endpoint has appA v1, manually installed etc .. we then decide to deploy and manage appA v1 via intune, and make it available on company portal... it remains available for install, and intune has no idea that app is installed, unless a user actually click install...
this also makes it difficult to auto-update when say we want to shift to v2... users with v1 installed wouldn't automatically get the auto-update to v2... and even if they click v2 to install, supersedence rules won't realise v1 is on the device, and won't trigger uninstall of v1 for example before installing v2...
in reply to David Guyer about what fields that we would like for dynamic device group to detect if an app is installed .. registry key would be really useful as we often use reg key / value to detect if an app is installed or not and what version.
Another request would be if something can be done to reduce the need to download entire win32 intunewin bundle including install source just to 'uninstall' an app ... especially if the uninstall only needs a small script or command... SCCM has the ability to specify different source for install/ uninstall... that would be really useful to speed things up as we deal with lots of bigger apps. It makes no sense having to download 10gb just to uninstall v1, then download another 10gb of v2 to install the new version for example.
- shin0933Mar 23, 2026Brass Contributor
While it's not inherently obvious, in the requirements section of the Win32 application creation process, you can add an Additional Requirement that states a certain file/folder, registry key, or powershell script execution result must exist/not exist or equal a value (like an installation detection rule) before the installation can happen.
This is how I treat app V1 and AppV2 upgrades, make one deployment as an "available" installation for a group of users then make another deployment of the V2 upgrade a required installation for all users/devices but only if a certain requirement is met.It's not pretty, but it's a guaranteed working process.