You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know why, but every time a client installs a new TeamViewer package, the app is opened afterwards. Is there a way to change that behaviour? Our employees are wondering whats happening when the app opens and suspect some kind of malicious remote control operation....
The text was updated successfully, but these errors were encountered:
Hi @opus-nbo - It looks like that's included in TeamViewer's installer process. I used Suspicious Package to search for open and found this line that looks relevant in a script in the LauncherFull component package.
Sometimes vendors build in logic that can be taken advantage of to prevent user-facing app launches. It would take some digging to determine whether such logic exists here.
TeamVIewer appears to have some documentation available for using "silent" install mode, but I'm not sure whether that omits the app launch or not. Might be worth testing.
There is logic built into the installer for this functionality. You have to create a file at a particular location that is referenced during the functions section, called by the postinstall script.
In there, under the restartService() function there is a check to see if /tmp/tvonlystartservice exists, if it does the installer will not open the application post-installation.
Simply, create the file before the installer is called; not sure if the contents of the path matter but "1" seems to work fine. echo "1" > /tmp/tvonlystartservice
Legacy
For clients installing older versions of TeamViewer, this path used to be /tmp/tvPath. This path would have to contain the correct path for client installation as the variable was referenced elsewhere within the installation scripts. echo "/Applications" > /tmp/tvPath
Some documentation for this behaviour can be found here.
I don't know why, but every time a client installs a new TeamViewer package, the app is opened afterwards. Is there a way to change that behaviour? Our employees are wondering whats happening when the app opens and suspect some kind of malicious remote control operation....
The text was updated successfully, but these errors were encountered: