0

I'm developing a MSI package that installs my product. I do my best to follow all the best practice, however, there is one thing I haven't found anywhere how to do best. I need to supply one parameter that is computer-specific, i.e. I'd like to run something like msiexec.exe /I mypackage.msi MACHINESPECIFICPARAMETER="somerandomstuffhere".

My question is: how is this best implemented from deployment perspective, in order to work in large organizations? Does Group Policy or SCCM even support per-machine parameters (haven't been able to confirm/deny this)? The parameter in question can be stored e.g. in Active Directory as an attribute of that machine.

I know about transform files, but I myself would hate having to create a specific .mst file for each machine, so that's not a good option.

The parameter is not secret and can be stored pretty much anywhere, if that helps.

Many thanks to anyone willing to help!

zajic
  • 1

1 Answers1

2

Old now, but if it were me I'd include a csv file mapping the machine name to the argument. Then use a small installer script to get the machine name, read the appropriate value out of the file, and run the actual installer with the correct parameter.

But also, I'd try to build my application to configure itself this way at first run, rather than needing this info via the installer.

Joel Coel
  • 13,117