Support for MECM / JamF / ... enterprise configuration.

[olahaye74]

Feature request

Which Nextcloud Version are you currently using: (Server: 33.0.0 client: 33.0.2)

Is your feature request related to a problem? Please describe.
Problem: can't push an enterprise configuration to managed desktop clients. I need to force server name and sync paths to our intreanet nexcloud server and forbid user to change this

Describe the solution you'd like
client configuration stored in registry or Library and pushed with SECM or JamF to the client desktop

Describe alternatives you've considered
due to our security policy, we'll need to stop using nextcloud client on desktop.

Additional context
The most important thing is to have a way to prevent user to change the configuration and have the servername fixed in configuration and sync PATHs relatives to homedire using a variable %HOMEDIR% or ~/ or any other mean.

[i2h3]

With release 33.0.0 and later, the app is sandboxed and stores its preferences in the container ~/Library/Containers/com.nextcloud.desktopclient/Data/Library/Preferences/Nextcloud. Server name and synchronization paths cannot be changed in the user interface after account configuration. Users could still modify the config file but that would also likely break the whole configuration.

I have no experience with MDM solutions and do not know about their capabilities. Can't they handle it like that already? Why and what do we need to change in our software?

[Rello]

Hello @olahaye74,

thank you for that request.
This is coming up from time to time and we will have a look at some point of time, but its not on the top of the list at the moment.
While features like the fixed server url are already available now as part of our enterprise branding feature, not all configuration can be preconfigured. This will need to be investigated in the future

[i2h3]

I will close this as a duplicate of #5497 and quote the request above.

@olahaye74 Please add a thumb up on #5497 to increase its visibility.