TechSmith Snagit and Camtasia - MSI installer support

How has everyone handled the MSI installation? With TechSmith products having a pre-req of .net, webview2,c++ do you add dependencies to the PMPC installations or create your own pre-scripts to make sure the pre-req are installed first?

We have shipped this product with a caveat. MSI will be a base install only. This is because the MSI install cannot update an existing EXE installation, and we could not determine how to differentiate between an existing MSI and EXE install. Updates will continue to use the EXE as the EXE is able to update either an existing EXE or MSI installation.

bump

We are currently pushing Snagit 20 MSI and cannot get the 19.1.6 update to uninstall. Has anyone come across this? First install of 19 was an MSI and we applied all the updates as they emerged. We cannot however get the last point update to uninstall.

just adding my two cents - we wont have a need for the EXE if the MSI support is added. the MSI is also the only way to do a customized install (select specific features, disable auto-update, etc)

I'm also interested in only the MSI version as I use an MST to apply a volume license

Giving this one a bump as well. Interested to hear the resolution to this.

@Casey  I agree.  Once the MSI/MST is supported I plan to make the switch.  But in the meantime there are workarounds that allow us to still utilize the benefits of Patch My PC's automation.  Posting those workarounds here are useful to the next admin.  Making square pegs fit in round holes is what we do after all. :-)

@Peter That helps for the license key and I might be able to dig up other transform data and force it via Config Baselines like I do for other apps. My major question is why do that when the Publishing Service already has built in MST support for MSI installs?

If registering with the license key is what you are missing, you can still accomplish this seamlessly with the EXE.  You need to create two files.  One is the RegInfo.ini file you can get from one machine with it registered under C:\ProgramData\TechSmith\Snagit ##,  where the ## is the version year.  The second is a PowerShell script that copies the INI file mentioned to that same folder on the destination device.

$CurrentDirectory = $(pwd).path
Copy-Item -Path $CurrentDirectory\RegInfo.ini -Destination "$env:programdata\TechSmith\Snagit 20" -Force

Then configure your application to use the PS1 in the post script and add the INI file to the additional files.  The app (Snag-it in my case) installs and is registered with no interaction.

@Justin After talking with TechSmith support today, they advise using an MSI if possible because passing MST instructions through an EXE wrapper may not work. What is the blocker on switching this app over to using using the MSI?

@Charles, we were testing it this weekend. The EXE and MSI look very similar from a rules perspective so we are still trying to figure out how we can handle this scenario.

Hello Justin, any update on this? Last time you said you would take care of this asap.

We do not need the EXE based install, just MSI.

MSI only as well for us.

Only need MSI.

We have always used the MSI.  No EXE support needed.

We will take at this as soon as possible. Would anyone here still need support for the EXE based install if we add the MSI?

Ran into this issue today, we use a .mst file created with the Techsmith Deployment Toolkit (which we can now copy to the source folder with the new Additional Files feature, thank you) , but the .exe for Camtasia does not appear to take the TRANSFORMS parameter.