Has anyone ever seen this? My customer's IT department pushes my company's MSI file out to desktops. The MSI file is designed to be installed per-user and has TARGETDIR set to a folder in the user profile. However, TARGETDIR is being reset to C:\ during the execution of Windows Installer and all the executables end up in the root directory of the C drive (not good!). I can see this happening in the MSI log file, but I cannot figure out WHY it is happening. The push to the desktop is executing the MSI under a high-privilege system account and not under the end-user's account, and I suspect that this is the root cause of the problem. Any ideas or suggestions on how to diagnose and fix this issue?
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


i don't know if you still need help on this, but this might be a possible solution:
Open the .msi file with for example orca.
Go to the table Custom Action and search for something like: SET_TARGETDIR
In some some MSI Files directories are set in this table, you can change in the directory table whatever you want and it gets overwritten by this custom actions.
Answered 05/20/2011 by: mafa2500
Yellow Belt

Please log in to comment