-
Notifications
You must be signed in to change notification settings - Fork 705
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
Auto Install Rocket.Chat Client on All Windows PCs #970
Comments
Feature request for the desktop client. Please open an issue if there isn't one already on that repo: https://github.com/rocketchat/rocket.chat.electron/issues |
Hello, Thanks and greetings. |
I agree that this feature is needed. We want to use this in an enterprise, and so we need to be able to install the product headlessly through domain GPOs. I think an MSI is probably the only supported installer type for domain GPO. |
Forgive my ignorance, but does the MSI option replace flawlessly some options of the EXE setup? AFAIK some command-line flags will not be available. |
An MSI can fully replace an EXE. You create the GUI for MSI, and name each field in the UI. MSI has a built in headless mode that will use default values for all options on the GUI, or default options can be over-ridden on the command line by specifying the field name. |
To be honest, we have to think more about it. I believe we have to fully support enterprise setups and our dependency on |
same here, would love to see this feature |
Hello, Very kind regards. Ale |
I hope the MSI will be there soon. It would make our job as sysadmin a lot easier. |
Rocket.Chat Version: Version 2.6.1
Running Instances: MongoDB V3.2.9
DB Replicaset OpLog:
Node Version: v0.10.26
Please add a setup (.msi) with group policy object (GPO) for Windows Domain Controller to auto install Rocket.Chat client on all Windows PCs in a company network. And it would be cool when the .msi file could be installed for all users (not only one user or admin on a pc)-
The text was updated successfully, but these errors were encountered: