Android App Preconfiguration and Autoconnect

[prononext]

Is there any way to preconfigure the Android MeshCentral App to push it through a Mobile Device Management with following settings?

1. Set MeshCentral Server Address
2. Auto Connect to MeshCentral Server
3. Auto Accept Streming + Recording
4. Configure User Consent

That would be really nice.

[Ylianst]

Not right now, but I have never used a Mobile Device Management software. If you know of a way this is typically done? let me know, I can look at adding support for it.

[silversword411]

You might be able to glean useful info from here on MDM

https://github.com/flyve-mdm/android-mdm-agent

[prononext]

I was thinking about a finished apk inside Meshcentral. Inside that APK the server and other settings are already set. Of course there are a ton of plugins to use. But for MDM normally the MDMs base API needs to be integrated into the non-system-app, in which you want to change settings. So preconfigured API would be much nicer and easier to update.

As for flyve mdm, its quite outdated, tried several times to get in contact with no success.

[si458]

you cant at the moment do alot of the things you want from the google play store or APK.
BUT you can hardcode the URL, if you build/built the APK yourself and distribute it yourself,
link below to the lines you need to change
https://github.com/Ylianst/MeshCentralAndroidAgent/blob/main/app/src/main/java/com/meshcentral/agent/MainActivity.kt#L40-L44

[Rocket78]

Hi, I just want to dig up this issue as there is a seemingly easy possibility (by the looks of it, sorry if I overstep I'am not an Android developer) to provide managed configuration options for your app: https://developer.android.com/work/managed-configurations

We also use a MDM (AppTec360) which then shows these configurable options like this (its from MS365 CoPilot):

Would be great to have an option for the connect string. When I could configure it there it would be pushed to the device belonging to the profile upon installation of the app. It even works afterwards if the app is already installed/deployed and the options are configured later on to the profile.