Score:0

How to deploy a MSI that needs a per-machine parameter?

cn flag

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!

cn flag
SCCM and other real Configuration Management solutions provide this capability. Group Policy does not.
zajic avatar
cn flag
OK, thanks! So I could just proceed with my approach of having cmdline accept the value, and rely that 'serious' customers will be able to use that? Anyway, I'd accept it as the answer.
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.