In our installer, the bootstrap app sometimes needs to do stuff that involves leaving files in the temp folder for custom actions in the MSI to pick up. The problem is, when a person remote logs into the OS using Remote Desktop Connection, the bootstrap app and the MSI see the temp folder in different locations. For instance, on Windows 2003 Server, the bootstrap app would see the temp path as being C:\Documents and Settings\Administrator\Local Settings\Temp\1 (or some other number at the end, depending on how many other users remote logged in prior), while the MSI always sees the temp path as C:\Documents and Settings\Administrator\Local Settings\Temp. I'm guessing that this is because the main msiexec process is running under SYSTEM instead of the user.
Is there any way to get the MSI to return the user's temp path instead of the SYSTEM temp path so it can access the files that the bootstrap app placed in the temp folder?
Failing that, where should the bootstrap app be putting files (and registry entries) so that the MSI can get at them even in remote login situations?