In intune I want to create a dynamic group that checks wether or not some app is installed on this user's device. Is there any way to query to see if an app is installed on a device or on a user's device.
Thanks!
In intune I want to create a dynamic group that checks wether or not some app is installed on this user's device. Is there any way to query to see if an app is installed on a device or on a user's device.
Thanks!
There's no direct method to do this today. What's the purpose of the group once you created it? IOW, what will you use it for?
I'm not the OP but my example would be the current Chrome vulnerability. I have devices that have Chrome not installed via Intune.
I want to be able to force install an update to Chrome on all machines that have it installed without having to force install Chrome for everyone or having to go through and pick the machines.
https://msendpointmgr.com/2020/05/26/automated-3rdparty-patch-remediation-in-intune-with-azure-automation/ That is an example someone else came up with to solve this problem.
For that specific scenario (and assuming Windows since it doesn't make sense on iOS or Android necessarily), you could/would deploy the update to all devices using a Win32 App and use the detection method to ensure it only runs on systems where the update is applicable -- this is the entire purpose of Win32 apps having a detection method.
Yes was discussing Windows in this situation. So for MSI I would need to package it as an intunewin app to get the options for app detection method. I didn't realize the app detection rules were used to also detect if the app was already there. I thought they were intended to use to see if the App is now showing up as installed.
I realized you're probably pointing out the detection rules under requirements. Got it, that would solve this, I would just need to maintain an app without the requirement rule for first time installs of the app.
Sorry, I called out detection method when I actually meant the requirement rule.
For an MSI based installer, yes. In general, packaging MSIs as a Win32 package is always recommended for a variety of reasons.
8 people are following this question.