Techsmith capture silent install

  • 2
  • Problem
  • Updated 3 days ago
Needed silent switch for EXE file or MSI installer for Techsmith Capture installation package
Photo of San

San

  • 2 Posts
  • 1 Reply Like

Posted 3 weeks ago

  • 2
Photo of Paul Middlin

Paul Middlin, Employee

  • 1322 Posts
  • 334 Reply Likes
This is not yet officially supported (we do want to support deployment properly), but adding these switches should work:
--silent --acceptEULA

I say it is not supported because we have not been testing this regularly yet, and we may change it in the future based on feedback for how we should support deployment.
Photo of San

San

  • 2 Posts
  • 1 Reply Like
Thank you Paul for these details, It works fine. Could you please let me know Uninstaller switch as well for this? Much appreciated 
Photo of akhtar.hussein

akhtar.hussein

  • 1 Post
  • 0 Reply Likes
Do you have a uninstall command to uninstall capture silently?
Photo of xerxes2985

xerxes2985

  • 2 Posts
  • 1 Reply Like
Paul,

The switches mentioned do not work for install. It still pops up the EULA box to accept. Additionally, the program defaults to installing in the user's appdata folder (user based install), and doesn't offer any options to install into the Program Files directory. Do you have a help document with the installer switches for the EXE? 

I would recommend creating an MSI installer for those who need to deploy it in an enterprise setting (just as you all offer Snagit and Camtasia MSI). The current installer works perfect for a home user though.
Photo of Paul Middlin

Paul Middlin, Employee

  • 1306 Posts
  • 331 Reply Likes
I do agree that a tested, documented enterprise install process with MSI would be best. However, we have not yet tested this as I mentioned earlier. We will document this when it is supported.

While I have you... 
we currently install in user space, as you say, so that it can be installed and updated by the user without a need for admin privileges. It also allows it to auto-update regularly. Can I ask why you might want to install in Program Files? Thanks!
Photo of xerxes2985

xerxes2985

  • 2 Posts
  • 1 Reply Like
Paul,

I have found that managing user-installed applications can be cumbersome, and difficult from a technical standpoint to troubleshoot issues that could arise. Also in the case of a computer lab, offering a program like Capture to the device, rather than per-user (as users still have to sign into Capture to use it), is much easier to manage and ensure it gets updated per device than per user (example: user occasionally uses the program every few months, and a critical vulnerability occurs).

However, if the user install can be configured for “all users” or to “install on user login” natively, that would be just as good as installing into program files. One example of something like this is the Teams MSI, which installs per user, as they login.
Photo of IT Support

IT Support

  • 1 Post
  • 4 Reply Likes
We are also looking at switching to TechSmith Capture instead of Jing.  It is an issue for us that  the application installs in user space without admin credentials required.  We also strongly prefer applications that have a working silent installer and uninstaller.  We do not want users to be able to install or update applications as it is a signification security risk and a support nightmare.  The Jing .msi could easily be deployed and removed via AD and many other methods.  The new setup.exe is not as versatile. 
(Edited)
Photo of Mike Bound

Mike Bound

  • 1 Post
  • 0 Reply Likes
For corporate invironments, installer needs to install into Program Files, and user to run program from Program Files.
Also needs to be silent/scriptable to be able to deploy it.
There needs to be a way for corporates to do the above two things.
If users could download and install anything they want, (such as Techsmith capture as it currently sounds like it is) be ready to be cryto-lockered.
Cryto locking can only be defended against by application white listing techs. Such as Windows SRP.
To see this problem, search on Teams and Program Files. See IT admins screaming at Microsoft to sort there Teams installer out so it installs into, and runs from program files.
Note we do our own custom install of Teams that both installs and runs from Program Files to sort this issue of programs trying to run in users appdata. Teams msi is not good BTW (referring to comment above), as user can't run from appdata.
Note Google Chrome tried this, running in appdata. They changed it and gone back to running in Program Files as it used to be, because of this sort of stuff.

I hope clear and helps Techsmith with direction on installer and running location.
And I luv Jing. So hope we'll be able to run the replacment product :)
If I can't figure out how to get it to run out of Program Files, (using the default NTFS file permissions of user read rights), then won't be able to use it.
(Edited)