I am trying to deploy AIR apps internally and am running into permission issues relating to AIR's insistence on installing to all users, which is set as normal in a temp msi file under "SecureCustomProperties". It is always the first entry in this field.
I have discovered the following:
-An AIR package is a zip file, but does not contain the msi; so the msi file must be generated by the AIR player.
-During installation the AIR package is unzipped to user\local\Temp{randomdir}; which is where it places "setup.msi" (This folder is swiftly deleted after installation)
Since the msi only exists for a few milliseconds prior to installation, I cannot edit the msi file prior to install. I could do it for the first installation by copying and modifying the temp folder, then executing the new msi; but I am using Adobe's built in updater, so this would mean repeating this procedure every time a new version is posted - defeating the whole point of automatic updates.
I am curious if it is possible (via group policy, or anything at all) to add an exception for Windows Installer to either:
- Allow ALLUSER installation for non-admins from an MSI either
- called "setup.msi" in a subfolder of "user\local\Temp\"
- or an MSI with a specific ProductCode, AppId, and PubID
- Or configure WindowsInstaller to ignore the ALLUSER flag (by turning it off, or simply dropping item 0 in SecureCustomProperties), either globally for a certain user group, or for an MSI file as defined above
If those things are not possible, I always am open to suggestions, and grateful for any help on this.
Thanks