In our current version of Filewave (11.2.1) I am recreating all of our filesets to be MSI filesets (to the best of my ability). However, there are a few that I have not yet been able to find a way to do so, such as Adobe Air. So far, I've only been able to get the EXE to work. Removing an MSI association allows for automatic removal of the program, but removing the EXE association does not uninstall it.
Is there a way to set up EXE-based filesets to uninstall the program when the association is deleted?
Also, what is the best method to upgrade software versions if the original fileset was made with Fileset Magic, and new fileset is an MSI fileset?
I noticed in my test that applying the new fileset at the same time as deleting the original caused the deletion to also remove files needed by the updated one.
Go through each sub-key until you find a DisplayName value whose data that matches the name of your app. Then check the UninstallString value about 14 lines down in the same sub-key. That's the string that gets invoked when you click the Uninstall/Remove button/link in Programs and Features. Copy the data for that value and try it out from the command line and see if there's a way for you to run it silently. Normally it pulls some some UI wizard that walks you through the uninstall. Sometimes adding a /s, /silent, /q, or /quiet may do the trick. To might also be able to find a switch to run the uninstall silently on the software vendor's website in a KB or Technote article. Or you could contact the vendor and ask directly.
Once you've figured out the command line to run the uninstall silently go back to the FileWave Admin, select your EXE fileset and click Scripts in the toolbar. Add a Post-Uninstallation Script and paste your commandline to silently uninstall the package there. This script will get triggered when the association is removed. I've noticed that some apps simply cannot be uninstalled silently because the uninstaller for the app was not created with a provision to run silently.
With regards to your 2nd problem it seems to be a timing issue. I could be wrong but it appears that the MSI is installing first and then the Fileset Magic fileset is getting rolled back afterwards or while the MSI is still in the middle of installing . Have you tried forcing the old Fileset Magic fileset to be removed first with one model update/verification and then have the new MSI fileset installed afterwards with a different model update/verification. If that works then you might want to try something like this. Add a Requirement script to the new MSI fileset that basically returns an exit code of 1 if the installation folder for your app is present on the hard drive. That guarantees that the new MSI fileset will not activate until the old Fileset Magic fileset has finished rolling back.