Software Deployment

Did you see this FAQ?

How do I control the destination drive of my package?
http://itninja.com/question/do-you-have-a-sample-protocol.ini?5

Hope this helps,
Bob

yes ive tried that, but it says that that rootdrive will not work BC it points to the windows "program files" folder, it said to use this instead, but it is not working either

Make sure that you add the ROOTDRIVE property in caps. and set it to D:\

It should then install your app to D:\Program Files\[Installdir]

If it isnt then make sure the drive is available during the install.

You could also go to the Property Table and change all of the paths to point to D drive.

rootdrive is in all caps

Hi Nevik - not sure if you still need a solution for this. A few months ago, I was having a hard time getting the Install Directory changed to D:\ (using Wise). I tried RootDrive with no luck. I finally added a custom action to my script:

Created a new property called MYDIR (or something unique) and entered desired drive letter for the value (i.e. D:\)

After the Cost Finalize entry in the User Interface sequence, insert a Set Directory custom action

Enter a unique Custom Action Name - doesn't matter what it is as long as it's unique

For the Directory field, clicked on the Browse button, and chose the folder you want the app to install to, and click OK. The Directory field will be populated with the property name of the folder (i.e.INSTALLDIR)

In the Directory Value field, entered the custom property you created in all caps/square brackets, followed by the folder path you want the application to install to: i.e. [MYDIR]Program Files\Windows Resource Kits\Tools. Click OK

It worked like a charm.
Hope this helps.

Does any1 have an idea why this command isnt working:

MSIEXEC /i "Path to MSI" ROOTDRIVE=D:\

I've found the rootdrive command option to be problematic - its works on most occasions, but some vendor supplied MSI's have some weird properties - one I had had DIRPROPERTY1, DIRPROPERTY2 etc that all had to be set to D: as WELL as rootdrive ... I found all this by extensive logging of the installation and also looking at the file table and tracing the directory structure there.

Hope that helps.

Paul

Using the SetDirectory Custom Action in WISE works fine.

But is there any reason why ROOTDRIVE won't work.


We should all be concerned if TRANSFORMS as a property stops working!!

If you write the custom action, it works. But if you install the msi in silent mode, it again takes the C:\Program Files as install directory.

For the change directory to work in silent mode, use the custom action under the "Normal Execute Immediate/Deferred" sequence.