msiexec /x {Old-Product-Code-GUID} /qn If your Windows image is 64-bit but you deploy the 32-bit MSI, Snagit will install to C:\Program Files (x86)\ and may have performance issues with high-resolution captures. Solution: Always use the x64 MSI for modern systems. 5.3. Missing VC++ Redistributables The Snagit MSI assumes the required Visual C++ runtimes are present. If not, the install will fail silently. Solution: Pre-deploy the VC++ Redistributable (2015-2022) via your RMM or SCCM before Snagit. 6. Version-Specific Notes (Snagit 2024 and Later) As of Snagit 2024, TechSmith has moved toward a hybrid deployment model . The MSI now requires an activation token rather than a simple license key. This token must be generated from the Volume Licensing Portal and is tied to your organization’s SSO or email domain.
msiexec /i Snagit.msi TRANSFORMS=SnagitLicense.mst /qn /norestart The MSI alone does not store user preferences. Use the Snagit Settings Migration tool to create a .reg file or .xml configuration, then deploy it via Group Policy Preferences or a startup script post-installation. C. Suppressing Reboots Snagit may require a reboot for system integration (e.g., printer drivers or shell extensions). Use: Techsmith Snagit Download Msi
msiexec /i Snagit.msi /qn REBOOT=ReallySuppress For compliance (e.g., software asset management), log every install: msiexec /x {Old-Product-Code-GUID} /qn If your Windows image
Subscribe now to keep reading and get access to the full archive.