Single MSI with Multiple .config files with parameters during deployment
Answers (3)
Comments:
-
thanks for the answer. So to further clarify i would just be able to add /finance or /ops from KACE1000 command line with the single MSI and it would be able to differentiate between the departments. Correct? - anadeem1 8 years ago
Not quite. You'd need to specify the public property - whatever you decided to name it - and its value on the command line. The condition set on the component, along with the entry in the DuplicateFile table, would copy the relevant file to its target folder:
MSIExec /i "%~dp0whatever.MSI" DEPT_NAME=FINANCE [other command-line arguments, e.g. logging]
2nd attempt at this..
I have done something similar to this.
I would recommend one MSI and 4 MSTs, one for each department putting the correct file for each dept.
Or, one MSI, 4 files (dept1, dept2, etc.) then a batch file for each dept, that would first copy the dept1 file as deptest.config, then install the MSI.
The particularly Gucci way of doing this would be to have one MSI, one MST. The MST would contain 4 components conditionalised, ideally, a method of doing an AppSearch, to detect something on your machine that defines it as dept 1 or dept3 (reg key, env var etc.)
However, I think you are going to be stuck with actually defining that yourself. which would mean either 4 different commandline arguments (to provide the info to make the condition TRUE) or, 4 MSTs each one installing the appropriate file for the dept that you define.
