Chained .msi package

[madiganz]

Is it possible to create a chained .msi package without actually knowing the exact file name? The build for the .msi file changes its name.

I tried doing C:\Scripts\Deployment\*.msi, but this does not seem to work.

Running a batch file using this technique does not work because it says that the first windows installer needs to finish before moving on to another one.

Creating a CA with running another .msi file does not work because it looks for the specific product key.

Any help would be great.

Thanks