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 installation / .msi support for rocket.chat windows app #3421
Comments
I go along with this! I'd would be great to define a server during installation. |
Closed by: RocketChat/Rocket.Chat.Electron#208 @frasercarter |
Thanks for the silent switch. Still it would be great to get .msi installer packages directly from the download page. |
It appears this may have been regressed in 2.2.0. I'm no longer able to install silently, and it installs to the user's appdata\programs directory instead of to C:\Program Files(x86) now. |
Silent installation works in my case with /S parameter, but the client is installed to the user's local AppData Dir: C:\Users\myuser\AppData\Local\Programs\rocketchat\Rocket.Chat+.exe |
Just completed our Windows 10 RocketChat deployment, used a GPO which ran the "rocketchat-setup-2.8.0.exe /S" command at user login. I assume when deploying patches down the road we'll have to run the ""C:\Users[user]\AppData\Local\Programs\rocketchat\Uninstall Rocket.Chat+.exe" /currentuser" command followed by "rocketchat-setup-2.9.0.exe /S" at login to update existing RocketChat installs. Please consider making an MSI installer which allows for installing in Program Files, over the long run it'll be much easier to patch and deploy. Being able to specify the rocketchat server at install time would also be a major time saver. |
This seems to be an issue with Electron rather than the server itself. If this is still a problem please open a new Issue in the Electron here https://github.com/RocketChat/Rocket.Chat.Electron |
@rocket-cat close |
Feature Request for an .exe that supports /silent switches, or .msi support to cater for business/enterprise rollouts.
The text was updated successfully, but these errors were encountered: