Existing package, different install path?
Hey guys,
Question: I have an existing package that curretly installs itself in the C:\Program Files folder... Now, we have a specific case where this package would need to be installed in the D drive, under Program Files. Can I reuse the same package to accomplish this?
Thanks!
Steph
Question: I have an existing package that curretly installs itself in the C:\Program Files folder... Now, we have a specific case where this package would need to be installed in the D drive, under Program Files. Can I reuse the same package to accomplish this?
Thanks!
Steph
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
Sure, but it depends on how you deploy. If you are able to specify a command line argument, add the argument 'ROOTDRIVE="D:"'
Posted by:
Jamie B
16 years ago
The ROOTDRIVE property must be terminated with a \
ie ROOTDRIVE="D:\"
ie ROOTDRIVE="D:\"
Posted by:
Fau
16 years ago
That easy?
as in something like:
msiexec /i "path\mymsi.msi" ROOTDRIVE="D:\" /qb
?
If so, it's not working.... ? is it because the package was made via capture? Or it shouldn't impact anything?
as in something like:
msiexec /i "path\mymsi.msi" ROOTDRIVE="D:\" /qb
?
If so, it's not working.... ? is it because the package was made via capture? Or it shouldn't impact anything?
Posted by:
anonymous_9363
16 years ago
Good catch, JB. Have a gold star :)
Your command line arguments are spot-on. It shouldn't make any difference if you have a capture. Run the install with a verbose log. That'll show you to which paths the various properties are being resolved.
Your command line arguments are spot-on. It shouldn't make any difference if you have a capture. Run the install with a verbose log. That'll show you to which paths the various properties are being resolved.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.