Installing Selected Features of MSI with ADDLOCAL Property
Updated: 07 Jul 2009 | 6 comments
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.
Edit the custom Acton to add New Feature
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.
About Endpoint Management Community Blog
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. Filter by:
Blog Tags
Configuring Altiris Client Management Suite Altiris Deployment Solution Symantec Management Platform (Notification Server) Wise Packaging Basics Altiris Server Management Suite Best Practice Compatibility Tip/How to Helpdesk Solution Altiris IT Asset Management Installing Workflow Solution Ghost Solution Suite Windows Reporting Performance Upgrade Features ServiceDesk 7.x Database Agents Dell Management Products
Comments
FeatureLevel
Why not use the featurelevel and instead altogether comment the custom action ?
I Agree, but
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.
Piyush Nasa Altiris Certified Professional (ACP)
http://msiworld.blogspot.com/
Um
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
thank god..
Atlast someone got the point i was trying to make.
Thanks Loee!!!
ADDLOCAL property in Command line
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.
Piyush Nasa Altiris Certified Professional (ACP)
http://msiworld.blogspot.com/
Do not forget
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.
Would you like to reply?
Login or Register to post your comment.