Forum Discussion
Correct App detection rule File Path for User Folder
Detection rules run as SYSTEM, not as user even if you deploy it as a user package. You have to use something outside a Users folder to detect the installation, I usually create a file in c:\programdata\customername\...\installed.txt and check on that to see if the installation succeeded
Detection rules run as SYSTEM, not as user even if you deploy it as a user package. You have to use something outside a Users folder to detect the installation, I usually create a file in c:\programdata\customername\...\installed.txt and check on that to see if the installation succeeded
I was playing around with a win32app that got installed in the USER context ... ANd just adding a %username% in the detection rule... first it indeed tries to find it as system
Of course that would just fail
But it seems it also tries to find it as user if the system detection fails... and by the looks of it ... it succeeds
- Ok.. What? Is this something new?! I'm sure I tested this multiple times in the past and read that detection is done by system
- I know.... everywhere I am reading the same explanation.... so I was flabergasted to see this message in the IME 🙂
Harm_Veenstra Ahh makes sense. No wonder I couldn’t find much documentation on it. Do you have any doc that states the detection rule is on the system level? And thanks for the tip too!
It doesn't really mention it on https://docs.microsoft.com/en-us/mem/intune/apps/apps-win32-add#step-4-detection-rules , but it's just the way it works I'm afraid (Many people ask for user level detection rules).
Please mark my answer as solution to mark it as solved.- Ok thanks so much for your response and help!
