Best Practices Question
Desktop Authority - best practice for Flash installs?
I'm looking for ideas on how people are managing flash. We want to centrally push out the first-time flash install. The installer is a .msi so it can be easily pushed silently with desktop authority.
My question is about validation logic. I don't want it to re-attempt to install with each boot, so normally I would use a file-exists or file-version validation logic. However, flash uses the file version number in the exe's and dll's it installs (thus the file name changes for each version,) so I can't use a simple file check. DA doesn't support wildcards in the file existence logic so I am thinking my choices are:
1) use a one-time rule and hope nothing goes wrong
2) use the actual file name in the file-exists logic, rewriting the rule every time flash changes versions (and filename)
3) let it reinstall every boot
4) stop using .msi and run a batch file that installs and sets a flag, then i can check via the flag.
None are great solutions and I was thinking I am missing something and was wondering what others are doing for this type of situation.