Changing install directory
Hi all
I am having trouble with [INSTALLDIR] value, basically the issue is that when we install our msi across the network via deployment tool it installs the files on to the wrong directory. the MSI need to install the files to C:\VM2 but on some machines it installs on D:\VM2.
I have used the following under MSI Script > User Interface > ValidateProductID
[Set Property INSTALLDIR to C:\VM2 (Action)]
But its not working and still installing the app on to D:\VM2.
Please can someone help me here. Many thanks
I am having trouble with [INSTALLDIR] value, basically the issue is that when we install our msi across the network via deployment tool it installs the files on to the wrong directory. the MSI need to install the files to C:\VM2 but on some machines it installs on D:\VM2.
I have used the following under MSI Script > User Interface > ValidateProductID
[Set Property INSTALLDIR to C:\VM2 (Action)]
But its not working and still installing the app on to D:\VM2.
Please can someone help me here. Many thanks
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
mekaywe
13 years ago
Posted by:
manna
13 years ago
Posted by:
Ash786
13 years ago
Thanks to everyone help :)
I have managed to resolve it, I couldn't find ROOTDRIVE and SystemRoot variables but what I have done is to move the Condition just before ValidateProductID on the User Interface tab. it does change the the value for INSTALLDIR what I wanted it to be.
Also how do you use ROOTDRIVE with INSTALLDIR
I have managed to resolve it, I couldn't find ROOTDRIVE and SystemRoot variables but what I have done is to move the Condition just before ValidateProductID on the User Interface tab. it does change the the value for INSTALLDIR what I wanted it to be.
Also how do you use ROOTDRIVE with INSTALLDIR
Posted by:
anonymous_9363
13 years ago
Posted by:
Ash786
13 years ago
Posted by:
anonymous_9363
13 years ago
You cannot specify a drive in INSTALLDIR. That's what ROOTDRIVE is used for.
http://msdn.microsoft.com/en-us/library/aa371372%28v=vs.85%29.aspx
http://msdn.microsoft.com/en-us/library/aa372064(v=VS.85).aspx
http://msdn.microsoft.com/en-us/library/aa371372%28v=vs.85%29.aspx
http://msdn.microsoft.com/en-us/library/aa372064(v=VS.85).aspx
Posted by:
Ash786
13 years ago
Posted by:
mazessj
13 years ago
Ash,
There are many properties that don't appear in the Property table. Some are defined automatically at runtime. Some are used to control or override the default behavior of Windows Installer. ROOTDRIVE falls into both of these categoies. If you don't explicitly set it, Windows Installer sets its value automatically, pointing it to a local writeable HDD with the largest free space -- in your case, D:\. See the links VBScab provided for more detail.
You should read up more on the basics of Windows Installer.
There are many properties that don't appear in the Property table. Some are defined automatically at runtime. Some are used to control or override the default behavior of Windows Installer. ROOTDRIVE falls into both of these categoies. If you don't explicitly set it, Windows Installer sets its value automatically, pointing it to a local writeable HDD with the largest free space -- in your case, D:\. See the links VBScab provided for more detail.
You should read up more on the basics of Windows Installer.
Posted by:
Ash786
13 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.