Options for creating transform
Hi all.
I have some vendor apps that I deploy new versions of several times a year.
These are quite inflexible, can't pass it any parameters, so I usually extract the .msi file from their setup.exe, install it silently, then use Wininstall LE 2003 to capture some settings/customization of the program. When I deploy, I simply use an autoit script that does runwait msiexec /i "originalpackage.msi" /qb! then msiexec /i "customsettings.msi" /qb!
This actually works quite well, however we're considering moving to doing GPO based deployments, so I'd like to make this a cleaner "msi only" process.
Ideally I'd like to make my custom .msi file a transform, and apply it to the vendor's msi at install time.
I could manually enter all the changes into Orca as a transform, but I'd rather get a root canal :)
So my question, can I:
a) Use something to convert my custom .msi file to a mst file?
b) Find a program that will capture my changes to a mst file instead if an msi file?
c) Do something else that I haven't thought of?
I have some vendor apps that I deploy new versions of several times a year.
These are quite inflexible, can't pass it any parameters, so I usually extract the .msi file from their setup.exe, install it silently, then use Wininstall LE 2003 to capture some settings/customization of the program. When I deploy, I simply use an autoit script that does runwait msiexec /i "originalpackage.msi" /qb! then msiexec /i "customsettings.msi" /qb!
This actually works quite well, however we're considering moving to doing GPO based deployments, so I'd like to make this a cleaner "msi only" process.
Ideally I'd like to make my custom .msi file a transform, and apply it to the vendor's msi at install time.
I could manually enter all the changes into Orca as a transform, but I'd rather get a root canal :)
So my question, can I:
a) Use something to convert my custom .msi file to a mst file?
b) Find a program that will capture my changes to a mst file instead if an msi file?
c) Do something else that I haven't thought of?
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
dm1
16 years ago
Posted by:
anonymous_9363
16 years ago
Generate an MST file using ORCA (free d/l from MS) with all the changes you need.
" I could manually enter all the changes into Orca as a transform, but I'd rather get a root canal :) "
There are some freeware MSI/MST tools around, if you (or your skin-flint employer) didn't want to spring for Wise or InstallShield. Google for "MSI +create +freeware" and take your pick. WinInstall Lite is relatively pain-free http://dl.winsite.com/bin/downl?16500000037147
Posted by:
smason
16 years ago
ORIGINAL: dm1
You dont convert MSIs to Transforms, the whole point of an MST is to work in tandem with the MSI without altering the MSI from its original form. Generate an MST file using ORCA (free d/l from MS) with all the changes you need.
OK, makes sense, but unless I really don't know how to use Orca (fairly likely actually :) )
do I really need to create a several records for every change that I need to add?
Say I need to replace one dll, and add 20 configuration files. Does that mean I need to create a feature component, and a file component and link them together 20 times, plus directory components, or is there an easier way?
Since I already have a .msi of the changes, is there any way to export/import them?
Thanks,
Steve
Posted by:
Inabus
16 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.