Software Deployment

Unless the MSI package itself offers a flag to accomplish this or you have access to the source, then you won't be able to modify the MSI package.

However, after installation, you could create a script that edits the .ini file that's created.  In that ini file, is there something like a variable such as: UniqueID=SomeValue and you are looking to create that string?

To create a script to do this (using standard Windows scripting, nothing fancy), create a UniqueValue.cmd file and put this in the file:

for /f "usebackq tokens=3 delims=," %%a in (`getmac /fo csv /v ^| find "Ethernet"`) do set MAC=%%~aecho static_%COMPUTERNAME%_%MAC%

Note that you will need to change "Ethernet" to whatever your interface names are.  If you're fortunate enough to not have whatever the variable is set in the .ini file already, you could do this (presuming the variable is UniqueID):

for /f "usebackq tokens=3 delims=," %%a in (`getmac /fo csv /v ^| find "Ethernet"`) do set MAC=%%~a
echo UniqueID=static_%COMPUTERNAME%_%MAC% >> C:\Path\To\File.ini

This will append that line to the file.  If for some reason it tries to put the UniqueID on the same line, just add echo. >> C:\Path\To\File.ini above the echo command listed in the code box above:

for /f "usebackq tokens=3 delims=," %%a in (`getmac /fo csv /v ^| find "Ethernet"`) do set MAC=%%~aecho. >> C:\Path\To\File.ini
echo UniqueID=static_%COMPUTERNAME%_%MAC% >> C:\Path\To\File.ini

I solved this problem, so if my experience would be useful to someone, I did the following: 1) I wrote a script of similar content as RyanTech advised me. 2) I converted this script into an .exe file 3) Using Orca and Master Packager I added a custom action to the msi package, in the execution sequence table I made sure that the program will be executed immediately after the installer writes the parameters to the .ini file. I spent a lot of time, but it worked!