In a similar way that a --optionfile can be used to guide responses for an installation, is there a way that a system administrator for a corporate account could place a config type file adjacent to the setup*.exe file that would allow that system administrator to customize what components are seen/installed for users on their network. We'd like to do this so that we can avoid installing software that they're not licensed to use and give the admins control over what end users might install.
asked 05 Jun '12, 15:59
This can easily be built by using xmlFileGet/iniFileGet actions. For example:
This will read setup.ini and check if key
This can be exdended to make it more difficult to guess component names by doing:
answered 06 Jun '12, 09:04