/build/static/layout/Breadcrumb_cap_w.png

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

0 Comments   [ + ] Show comments

Answers (4)

Posted by: anonymous_9363 12 years ago
Red Belt
0
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 12 years ago
Orange Senior Belt
0
The ROOTDRIVE property must be terminated with a \

ie ROOTDRIVE="D:\"
Posted by: Fau 12 years ago
Senior Purple Belt
0
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?
Posted by: anonymous_9363 12 years ago
Red Belt
0
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ