ActivCard Gold 2.2 modifying default (typical) options
Hello, I’m fairly new to modifying MSIs, creating transforms, etc. and was wondering if anyone could help with this specific problem.
I have a program called ActivCard Gold being installed via GPO. The installs work fine but I need for one additional feature to be installed.
Doing the install manually, one would select “customâ€Â, then expand the section for card reader drivers (Smart Card Readers Drivers & USB Tokens), then enable the USB (ActivCard USB Reader V2) feature. It’s laid out much like the features list for the MS Office install.
That feature is listed in the MSI as follows:
Features.JPG
Edit: changed to screenshot.
Using ORCA, I’m trying to make this feature install by default.
Any help is appreciated.
I have a program called ActivCard Gold being installed via GPO. The installs work fine but I need for one additional feature to be installed.
Doing the install manually, one would select “customâ€Â, then expand the section for card reader drivers (Smart Card Readers Drivers & USB Tokens), then enable the USB (ActivCard USB Reader V2) feature. It’s laid out much like the features list for the MS Office install.
That feature is listed in the MSI as follows:
Features.JPG
Edit: changed to screenshot.
Using ORCA, I’m trying to make this feature install by default.
Any help is appreciated.
0 Comments
[ + ] Show comments
Answers (8)
Please log in to answer
Posted by:
WiseUser
18 years ago
The important column of your feature table is the "Level" column (value of 110).
Is there a property defined in your property table called "INSTALLLEVEL"? See here for information about it:
http://msdn.microsoft.com/library/en-us/msi/setup/installlevel.asp
Read the remarks at the bottom of the following page to further understand the mechanism:
http://msdn.microsoft.com/library/en-us/msi/setup/feature_table.asp
Is there a property defined in your property table called "INSTALLLEVEL"? See here for information about it:
http://msdn.microsoft.com/library/en-us/msi/setup/installlevel.asp
Read the remarks at the bottom of the following page to further understand the mechanism:
http://msdn.microsoft.com/library/en-us/msi/setup/feature_table.asp
Posted by:
gdmix
18 years ago
Great, thanks. I’m still working on it but I now have a much better understanding of the process.
Posted by:
gdmix
18 years ago
I must be missing something. INSTALLLEVEL is set to 100, and I now have the feature set to 100. It still does not install that feature, unless doing a custom install which is supposed to set the level. If it’s already set to 100, shouldn't it install by default?
Features.JPG
Property.JPG
Edit: Odd, images show on preview, but not on post. Changing to links.
Features.JPG
Property.JPG
Edit: Odd, images show on preview, but not on post. Changing to links.
Posted by:
WiseUser
18 years ago
What command line are you using to install the MSI?
What about the "Attributes" column of your feature table?
Any custom actions that might be changing the INSTALLLEVEL?
What about the "Attributes" column of your feature table?
Any custom actions that might be changing the INSTALLLEVEL?
Posted by:
gdmix
18 years ago
I made a better SS of the features table and added the conditions table.
Features.JPG
Property.JPG
Condition.JPG
I’m not using any additional switches for the install right now. Just msiexec /I app.msi /qn
Thanks for all the help.
Features.JPG
Property.JPG
Condition.JPG
I’m not using any additional switches for the install right now. Just msiexec /I app.msi /qn
Thanks for all the help.
Posted by:
WiseUser
18 years ago
I'd say that you've found the problem (condition table).
I'm guessing you're either running Windows NT or the property WANDAREQ is being set to "-1".
If you can't see where the WANDAREQ property might be set/changed, try deleting the row of the condition table where the "Level" column is equal to "0" (just as a test).
I'm guessing you're either running Windows NT or the property WANDAREQ is being set to "-1".
If you can't see where the WANDAREQ property might be set/changed, try deleting the row of the condition table where the "Level" column is equal to "0" (just as a test).
Posted by:
gdmix
18 years ago
I’m not sure why, but your right, the condition table was what was keeping it from installing. Removing the conditions for the feature didn’t work, but after also removing the conditions from the parent, it did.
I may just have the feature and the parent removed from the condition, then set the features how I need them, for the final msi.
Thanks for all the info. I’m still learning but I have learned a lot in the last week.
I may just have the feature and the parent removed from the condition, then set the features how I need them, for the final msi.
Thanks for all the info. I’m still learning but I have learned a lot in the last week.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.