When an msi launches for a user after install it usually indicates that there are components that are in the package that are user/profile specific. In my experience, when a msi fires up for a user after install and it needs to go back to the actual source msi, there are files that it is trying to add to the user's profile. Take a look at the msi and see if it has any files that are being put into the the user's documents and settings folder. If there are, that is the reason the msi fires for the user and it needs to connect to the source. You will need to modify the package to account for that.
A couple of things to try if it's not possible to have the PC be able to reach the msi:
- Remove those files from the msi and test it to see if the app will work. Some apps do all that configuration on first run for a user.
- If that does not work, you could try using Active Setup to create a small script that would do the setup for the current user pieces. If you are not familiar with Active Setup see http://www.sepago.de/helge/2010/04/22/active-setup-explained/ for a good explanation on what it is and how it works.
We have done a fair bit of both of these methods and have not had a situation that can't be handled this way.
any other ideas. still not working.
Can you determine what exactly is being changed when the user logs in and runs the app and the msi runs? That would help to determine what actions need to be taken.
start your packaging process, put the file on the machine then, do the install from a folder on the machine, do your re packaging, then push that package that will have the msi in its original install folder
haven't tried it and just spit balling it