Endpoint Win32 app detection rule workaround?

[jblackburnHWGA]

Hi Is there is a simple work around for the detection rule when deploying an app?

 

I'm trying to send out C++ 2017 and i have no idea where the files install to or where the reg entry is for it.

 

Am I missing something simple?

 

I'm under the impression that the detection rule is a rule for checking if the software is installed both before and after install of the software. If the detection rule comes back as no the app installs if the detection rule comes back a no the app doesn't install and will try again after a set period of time up to 3 times.

I'm struggling to install some simple software just because of this rule

[snagrat]

If it’s an Msi then you can just use the msi string as detection. This will be prepopulated during the wizard.

 

If it is an exe then you will need to specify it manually. I usually install the software on a test machine and see what path is created. Then set the detection rule to file within that new location.

 

I’ve done C++ recently so can dig it out in a bit if you want?

[jblackburnHWGA]

Yea the MSI's are the easiest. I was thinking of dropping in a txt file into a folder as part of the install as i tend to use a cmd to install an exe file. Not great practice but a last resort

 

If you don't mind and you can let me know the detection rule for C++ it would save me a bit of a headache

[jblackburnHWGA]

just found this

https://zzz.buzz/notes/vc-redist-packages-and-related-registry-entries/

 

Not sure if its right but a good place to start