I am in the process of testing our setup for network deployment and I am wondering if it is possible to dynamically create the parameters of a command line for a MSI package contained in my installer.
Specifically, I would like to support the inclusion of TRANSFORMS="<transform list>" for the MSI package if it exists without a user having to use /stage_only to extract the packages.
I know that I can add properties to the command line and pass in values using properties. Those properties get expanded when the package is executed. But I am not certain how to make the jump from a command line option passed in to the suite to modifying the msi package.
Doing this will allow admins with SCCM or SMS to push our our product and include some optional setup parameters on some systems.
Specifically, I would like to support the inclusion of TRANSFORMS="<transform list>" for the MSI package if it exists without a user having to use /stage_only to extract the packages.
I know that I can add properties to the command line and pass in values using properties. Those properties get expanded when the package is executed. But I am not certain how to make the jump from a command line option passed in to the suite to modifying the msi package.
Doing this will allow admins with SCCM or SMS to push our our product and include some optional setup parameters on some systems.