I'm having a problem with a package that will sometimes (1%) install into the SYSTEM32 folder instead of it's default INSTALLDIR (which is off of C:\ and not in PROGRAM FILES). While 1% is low, I've deployed to abotu 1000 machines so far and faced this issue 8-10 times. They're a mix of Windows 2000 SP4 and Windows XP SP2 systems.

What will happen is that instead of the application installing to c:\myfolder\bin it will install to c:\windows\system32\bin. The supporting files will all get placed there as well. Nothing in the verbose log seems to help at all. Has anyone run into this before or can you point me in the right direction?
0 Comments   [ + ] Show Comments

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.

Answers

0
Nothing in the verbose log seems to help at all. Has anyone run into this before or can you point me in the right direction?Forgive me, but that's nonsense. It will tell you where that property's content changed.. I noticed recently that a CA in a vendor MSI was setting SystemFolder to be the last referenced folder. I had to set a property before the CAR ran, populating it with [SystemFolder] and then resetting SystemFolder after the CA had run.
Answered 11/07/2007 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity