@ooGDoo Thanks for posting in our Q&A. For this issue, did you mean that the app is already in the device, but when you deploy the app as win32 app, it is still installed? If there is anything misunderstanding, please correct me.
To clarify this issue, we appreciate your help to check if the existing app's msi code is same as you configured in the detection rule. Please refer to the following link to get the msi code:
Note: Non-Microsoft link, just for the reference.
If there is anything update, feel free to let us know.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Yes, Intune checks the product code. One somewhat common issue with checking the product code is that some products have self-updaters that update the product and thus update the product code as well. Thus, have you validated that the product code is still the same on these devices where it appears that the product is installed?
Yes I did, it's the same.
Do you think it might be a timing Issue? How long should I wait after Changing the Detection Method.
To clarify here, are you using an LOB app or a WIn32 app for the MSI installation?
win32 app it is
Have you reviewed the IME log for additional detail and information on one of the devices exhibiting the behavior?
Nope I couldn't,
We changed the Installation so the scenario can not be replicated.
Thanks and Regards.
@ooGDoo It is a strange situation. If the existing app's msi code is same as you configured in the detection rule, it will occur an error in detection rule process before installing the win32 app. The following article describes the detailed process of deploying Win32 app via intune:
IME log includes more detailed information about the whole process. If you meet this situation next time, please review the IME log to check if there is any failed message. And we will continue to discuss this issue.
Thanks for your understanding.
Sign in to comment