Client Management Suite

 View Only
Back to Library

Installing Selected Features of MSI with ADDLOCAL Property 

Sep 15, 2008 04:17 PM

Many times we have to customize the installation of vendor MSI, by selecting complete, typical or customize installation of the package. This will install particular features when selected. If we add another feature, it may not install, and we cannot see the files and registries added by the component present in this feature.

Using Custom Action:

Check for the custom action which is installing selected features and edit to add the feature.

Click to view.

Edit the custom Acton to add New Feature

Click to view.

Using Property:

Take log at the time of installing Vendor Msi. Search the log for ADDLOCAL property. Create new property "ADDLOCAL" in property table. Put the values displayed in the log file in addition to the feature that we want to install.

Note: This will generate ICE87 warning.

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Comments

Migration User
Mar 06, 2009 07:28 AM

Hi,

do not forget to add, your project's audit key[if standard exists], feature name in this property value......if you are not adding it,everything will get installed, unless your project specific registry /audit key.

Migration User
Oct 16, 2008 10:23 PM

It is always better to use ADDDLOCAL property in Command line while installation of MSI, rather than changing the feature levels everytime. Suppose you have to deliver the MSI to a different departments in an organization, who require different features of MSI, it is easier to do that with ADDLOCAAL property rather than changing InstallLevels for all departments and making numerous mst's.

Migration User
Oct 16, 2008 06:41 PM

Atlast someone got the point i was trying to make.
Thanks Loee!!!

Migration User
Oct 16, 2008 05:07 PM

You get the ice87 error becuse you are not supposed to hardcode ADDLOCAL in the Property Table. It will be forcing those features to be installed at repair-time and I'm sure that it can't be healthy at uninstall-time.
The condition on your customaction will force the features to be installed at repair-time. It should be "not Installed"
Also, yes, it is more usual to modify features in the Feature Table by changing their Level but the Custom Action solution should work well enough
looeee

Migration User
Sep 30, 2008 07:54 AM

Yup, I agree with you that we can do this by setting the feature levels and it should work fine. But if there is already a Custom Action present which is installing the given number of features, then instead of modifying the vendor MSI, it will be the best to modify the Custom Action. And it will take less effort in cast the number of features to be installed are a lot.

Migration User
Sep 29, 2008 02:29 PM

Why not use the featurelevel and instead altogether comment the custom action ?

Related Entries and Links

No Related Resource entered.