Event details
I have applications that autoupdate. This makes managing detection rules challenging. It's tempting to use the "IF Program Files <program> folder exists" rule, but that can cause headaches when the time comes to deploy a new updated app if it uses the same folder. In some cases, the ProductID code is the same. I would absolutely love an easier way to manage the detection rules for .MSIs and .EXEs that autoupdate. Is that something that can be considered?
Microsoftshin0933 ,
Can you tell me a bit more about why just dropping the version off isn't sufficient? Just looking for the file or regkey but ignoring version?
-David Guyer - Intune Product Manager
We have a few win32 apps that self update. Sometimes we need to deploy a new update over the apps that self update. This is where the challenge is because if I use a version regkey value, then that value could get changed after a self-update. Same thing for product ID. If an installation is required and the Intune deployment detection method is set to the version regkey value or ProductID, then the installation will try to go through again.
If the detection method is set to the existing of a file/folder, then I have to find something that is set to that version of the program. Otherwise Intune will say the application is already installed, but it didn't install the new update.My work around is to use a custom powershell script that searches for select criteria, uninstalls everything, then, re-installs the new update, should the self-updating application get stuck or hung.
Does this make sense? I'm happy to provide further details if needed. I've also attempted to work with the program owner, but my efforts appear to not go anywhere.