Repackaging issue - changing INSTALLDIR
Hi everybody,
I'm having an issue with a package that I've changed the INSTALLDIR property. During setup capture, the installation put the whole files into C:\<appli name>, but I put ProgramFiles folder as Directory_Parent through Setup Editor on Wise. I've compiled it, then I've tested this new package with an admin user and it works fine, but when I'm logged into the same computer with a restricted user, I ran the application from her shortcut, there is a self-healing process and the application is launched. The problem is that at this moment appears a new folder on C:\, and this application have to show many picture and it can't find nothing.
I'm sure that there are something wrong with the INSTALLDIR, but I don't know how find out that issue because it just appears when it ran from a restricted user, not with an admin user.
Somebody knows where I could to watch to find out the mistake??
I'm having an issue with a package that I've changed the INSTALLDIR property. During setup capture, the installation put the whole files into C:\<appli name>, but I put ProgramFiles folder as Directory_Parent through Setup Editor on Wise. I've compiled it, then I've tested this new package with an admin user and it works fine, but when I'm logged into the same computer with a restricted user, I ran the application from her shortcut, there is a self-healing process and the application is launched. The problem is that at this moment appears a new folder on C:\, and this application have to show many picture and it can't find nothing.
I'm sure that there are something wrong with the INSTALLDIR, but I don't know how find out that issue because it just appears when it ran from a restricted user, not with an admin user.
Somebody knows where I could to watch to find out the mistake??
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
jmaclaurin
13 years ago
It could be that the vendor created the MSI with the intention that it would be installed to the directory created in the C: drive, but also put it in thier code to write to the same directory when the app is in use. You may not be able to move it.
FYI, if a vendor provided you with an MSI, its bad practice to repackage it. Your better off to make the changes in an MST.
FYI, if a vendor provided you with an MSI, its bad practice to repackage it. Your better off to make the changes in an MST.
Posted by:
thugz888
13 years ago
might be that the application creates runtime files on the original location that was provided. If so you can't change the location of runtime files. Better solution to your problem is leave it as it is and don't move the install location to a different one.
Posted by:
anonymous_9363
13 years ago
Assuming that this isn't a re-packaged vendor MSI, what's required is a simple process of detection.
The healing will create an entry in the event log. That entry will contain the component ID. You can then locate that component in the MSI and determine what files and folders it contains.
The healing will create an entry in the event log. That entry will contain the component ID. You can then locate that component in the MSI and determine what files and folders it contains.
Posted by:
cmi2000
13 years ago
Yes! It's a legacy setup. I'll watch the event log to find the component ID, we'll see...
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.