Problems Caused by Using Command Line Property Values in an MSI During Installation
Updated: 26 Sep 2007 | 3 comments
Scenario: The MSI has different settings for different regions \ groups \ units.
Recommendation: Create one base MSI file and create a transform (.mst )for the region \ group specific installation.
Problem:
The command line parameter values are ignored and all properties will default to the initial value (which is present in the MSI) during MSI repair.
Solution:
Use of Transform will solve this problem as the settings will get merged to the base installation.
Example
msiexec.exe /i msiname.msi VARFLIP="True"
If you need to, set the value VARFLIP ="TRUE"
It is advisable to set the value in the transforms rather than running the MSI with command line property value as this value will not be taken care when the MSI goes for repair. It defaults to NULL when the MSI goes for a repair.
blog entry Filed Under:
The Endpoint Management Community Blog is the perfect place to share short, timely insights including product tips, news and other information relevant to the Endpoint Management community. Any authenticated Connect member can contribute to this blog.
Comments
Persistent property works also.....
You can also pass a command line Property and store it in the registry so it is perserved during repairs. You need to make an entries in the Registry, RegLocator, and AppSearch tables. I used this one and it works pretty slick. There is an old kb article with more details https://kb.altiris.com search for 23940.
John
Usage of MST
Its always a good practice to use MSTs to make property modifications, disable/enable a feature/CA etc. This technique will be very useful, when the application package is gonna undego activex deployment.
Cheers'
Viju
Microsoft MVP [Setup-Deploy]
Weblog: www.msigeek.com
Properties and Self Repair
Better yet, the use of Session.Property and CustomActionData will get you around this issue.
Would you like to reply?
Login or Register to post your comment.