Hi,Currently when an android device needs to be setup for unattended access, a human (probably) needs to manually add an unattended server URL to the ScreenConnect app UI, the app will communicate and get the full URI it will use from there on to connect to the relay server and store them in its shared prefs in AccessClientLaunchParametersUri

This is at least as best as I understand it.

When trying to deploy to thousands of devices in a centrally controlled manner (think EMM, Android for Work) though, this human interaction is simply not an option.

Is there a way to configure/deploy the ScreenConnect App unattended access functionality with no human interaction so it can be used in Corporate/COSU setup's ?

For example, is there an intent that can be used to configure the ScreenConnect app for unattended mode (Access), setup the URI, that can be launched from a DPC application after its installation?

Or can the shared prefs be created with WRITE_SETTINGS so they can be edited?

The unattended Android client is still in its infancy and we're looking for more features to add. We haven't done anything to specifically address these kinds of larger scale rollouts mainly because we're not sure what would help best. I strongly recommend adding your suggestions to our Product Feedback Portal.

You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.