Can I add a customer ID to an MSI with ORCA for a silent install?

Don’t guess the property name. Run the MSI with verbose logging and check the log around the customer ID prompt. If you find a property being set or read, test passing that property on the command line, for example: msiexec /i package.msi /l*v install.log CUSTOMERID=value. Replace CUSTOMERID with the actual name the installer expects.

A property can be absent from the table and still be used during installation. Adding a new row only helps if the installer’s UI or custom action actually reads that property. Test the command on a clean machine before putting it into your deployment package.

I’d look for the vendor’s silent-install instructions first. There may be a documented command-line parameter or a separate configuration file for the customer ID. If the MSI prompts even when run directly, changing its tables can turn into a lot of investigation, and a vendor-supported install method is usually easier to maintain.

ORCA can edit the MSI, but it can’t make an arbitrary field meaningful. Inspect the installer’s actions to see where the prompt gets its value and where that value is saved. Depending on how it was built, the right fix could be a command-line property, a transform, or a configuration step after installation, not a new Property table entry.

Also check whether the MSI is signed. Editing the package changes it and can invalidate its signature, which may matter for your deployment checks. Be cautious about baking a reusable license key into a package that lots of machines or people can access.