Deploy Snagit using SCCM [Enterprise Deployment Guide]
In this post I will cover the steps to deploy Snagit using SCCM. The steps are very much similar to deploying camtasia using SCCM. If you talk about image capture tool, Snagit stands out from rest of the softwares. Snagit 2018 is the only screen capture software with built-in advanced image editing and screen recording. Not only it is easy to use but it also features great tools to edit the captured images. Snagit is owned by Techsmith and you can read about Snagit features here.
When you deploy any paid software, you are most worried about licensing. You cannot pass the key to users. This is not recommended as they might use it for personal use. Using Techsmith deployment tool, you can customize Snagit installation. In addition you can also specify the license info. This tool works only with Techsmith products.
Customize Snagit using Techsmith Deployment Tool
Snagit is usually available for download as executable file. However Snagit is also available as msi installer for enterprise deployments. You download the .msi installer and customize it using deployment tool. Techsmith deployment tool is available for download here.
Download the tool and run as administrator. On the Welcome page, click Open MSI Package. Open the Snagit msi installer. I noticed that there are more options to customize Snagit.
Under General Options, you can specify username and software key. You can also specify custom installation path.
Under Disable Snagit Settings, there are many features that you can disable.
You can also customize features that are installed.
Create a transform file and close the tool. You will notice that you now have a batch file, mst file and Snagit msi installer file. We will use all the three to deploy Snagit using SCCM.
Deploy Snagit using SCCM [Enterprise Deployment Guide]
We will take a look at steps to deploy Snagit using SCCM. Launch configuration manager console. Right click Applications and click Create Application. Choose Manually specify the application the application information.
In the next step, specify information about the application. Add a new deployment type and click Manually specify the deployment type information. Click Next.
Specify the content location. Choose the batch file as install program. Your uninstall command will be msiexec /x {product ID} /qn. Click Next.
Let’s add a detection method. Choose Windows Installer as Setting Type. Click Browse and select Snagit msi file. The product code gets populated automatically. Click OK and complete the remaining steps.
The application is packaged now. Distribute the content to DP. Deploy the content to desired device collection.
On the client machine, launch software center. Select Snagit app and click Install. The installation should work fine.
Most of all in my lab setup, I have tested the app uninstall and it works well.
Hi -I’ve followed and tried this multiple times. I get 0x653(1619) error once it downloaded to the client machine. I’ve tried many different options and configuration but they did not resolved the error.
My goal for this customization is to embed the software key so no users action needed once completed.
I tested the msi deployment without customization alone and it worked but of course software key is needed when launched.
any suggestions is helpful.
thanks!
I get this same error.
I do not run it as a script. I use the msi selection under applications. Creating the MST file allows you to put in your product key so the end users do not have to when the launch the program.
msiexec /i “snagit.msi” TRANSFORMS=”snagit_2020.mst”