Scriptlogic MSI Studio - Quick Review
I've been meaning to install MSIStudio from Scriptlogic for a while to check it out, and I finally had time. I created (and edited, post-creation) a basic response transform, and repackaged a really old install (it was so old, folder names had to be 8 char!). For both, I was quite satisfied with how it functioned, and the plethora of customizations, especially post-creation; just editing the .msi or .mst. via right-click, edit.
Having used both Wise & AdminStudio in the past, the methods were very familiar to me. With that background, it's likely I wasn't a good person to test how a new ConfigMgr admin might understand how to use the app. But if you've used other Transform Editors, it's a very familiar layout.
If you work for a company which has a large department that needs to keep track of project status during package creation, one of the other vendors' offerings may be a better fit. But if you are a small to mid-size company with few people that would create a transform or repackage something, this would definitely fit the bill. I was able to quickly find everything I'd ever had to find when customizing an install: regkeys, files, permissions, custom actions, properties, what the entry in ARP looks like. I could create my own vbscript custom action, I could add my own Components and Features, and I could add to the upgrade list of GUIDs. I could mess with the order of InstallExecuteSequence, or delete items within the sequence. I know that's not a definitive list--but that's pretty much everything I've ever had to do when customizing an install as an admin.
I couldn't figure out how to import a .reg for stamping the .mst; but manually creating the Component, and Feature, then manually creating the regkeys in the registry, copying them over, editing them to be [ ] variables, then in the registry table moving the regkeys from their component to my component, building & saving worked. So it's possible to stamp your mst; but it was slightly painful! Although more likely... I just didn't know how to do an import regkey action within my custom component.
As an extra bonus, I checked the prices of the 'standard' full license for the other 2 vs. MSI Studio Standard. MSI Studio was easily 1/3rd to 1/4th the price of those others.
It should be noted I didn't test all of the options available--just the 2 that I've used most of the time. Creating a transform is the main one. Repackaging something is generally the absolute last choice to an admin--the vendor usually has an MSI. Even if that MSI is buried inside of a setup.exe. That just means you have to look harder to find it!