Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Silent install/uninstall flags #2797

Closed
1 task done
Senectus opened this issue Oct 18, 2018 · 4 comments
Closed
1 task done

Silent install/uninstall flags #2797

Senectus opened this issue Oct 18, 2018 · 4 comments

Comments

@Senectus
Copy link

Senectus commented Oct 18, 2018

  • I have searched open and closed issues for duplicates

Bug description

I'm trying to deploy this via SCCM or GP within our Org and I'd like to do this silently (including uninstall)
Please provide a series of flags so that it can be installed and not auto launch after installation, and be uninstalled silently as well.

Platform info

Signal version:

1.16.3

Operating System:

win10 1803

@Senectus
Copy link
Author

A friend of mine pointed out this is already there.
Signalexename.exe /S (it is caps sensitive on the flag)
Does exactly what I'm after for the install.

for uninstall this also works:
"%LocalAppData%\Programs\signal-desktop\Uninstall Signal.exe" /S

@scottnonnenberg-signal
Copy link
Contributor

@Senectus Do your users have enough permissions to keep the app up to date? It will pop up with offers to try to update itself as soon as a new version is released. And it will continue to pop up until the update actually happens.

@Senectus
Copy link
Author

should have, will have to test that. thanks for the heads up.

@gsmitheidw
Copy link

Just to add to this, the silent flag isn't very well documented. I would also have expected the setup executable to accept a /? to give a list of install modification criteria (even if it is only one currently?) but it unexpectedly starts the installation.

A wiki on github might be a good idea for documenting some of these less typical features. This issue also relates to
4690 in that both of these are typcally required in tandem on multi-user systems Windows 10 Multisession in AVD, Terminal Servers, student classroom labs etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants