If I am wanting to embed/automate the MS License Key within a SW Distribution bundle, would this be handled simply as a LICENSE KEY=path to license key switch on the .msi command in the action script? Or is there another preferred way to handle this?
There’s no “general” way to handle license keys - each product installer is different. You should google for your specific product and look for “unattended” or “silent” install to determine the command line parameters, configuration file, or registry entries to generate.
Once you know how to install / configure the product unattended, if you post those instructions here we can help instruct you on how to integrate those instructions via BigFix.
<MSI_PATH> is the location of the MSI file.
<LOG_PATH> is the location where you want the log file created.
<CUSTOMER_KEY_PATH> is the location of your customer key.
or
Alternatively you can use the following install command:
msiexec /I “<MSI_PATH>” /qn /l*v <LOG_PATH> licensekey=CUSTOMER_KEY
Where:
<MSI_PATH> is the location of the MSI file.
<LOG_PATH> is the location where you want the log file created.
<CUSTOMER_KEY > paste the full customer key (i.e Lwhdgdetbjghgbjklk).
If you are installing Microsoft products, I recommend their Key Management Server (KMS). We have scripts that can run in Bigfix to force the endpoint to register with our KMS server.
Maybe I’m not understanding the challenge. Does the vendor’s recommendation work? Is the key static or dynamic/unique?
We’ve called keys as command line arguments and by pointing to licensing files successfully. If those don’t work, then it is either a syntax issue or installer issue.