Any solution, if  exists, depends very much on how the app of interest is designed or implemented. 

If it has related AppConfig compliant option(s) to disable downloading/writing files to internal directory, then you should be able to enable/disable such option from your MobiControl web-console.

If the app has no such options or does not support AppConfig at all, then maybe you can check if disabling related  file-access permission(s) of the app in the App Manager tab of the device's Setting achieve the results that you want without affecting other operations of the apps.   If such app-permission change(s) can be found, then you can try using MobiControl script commands (e.g. "afw_set_permission_grant_state", etc.) to see if the required app permission change(s) can be remotely made on your targeted devices.   If so, you more or less get your solution. Please note that such tests need to be performed for each each brand-model/firmware version combination before deployment.   Also, if your devices do not have lockdown-menu Such tests need to be performed for each each brand-model/firmware version combination. /application-run-control policy to stop device end-user from manually making changes in device's Settings, then you may consider adding a schedule task profile policy to enforce the required app permission changes at regular  interval (e..g every 2 or 5 minutes).

Hi Carmadi,

Thank you for posting on SOTI Pulse! 

Did Raymond's response help with your question? 

Kind regards,

Technical Support Specialist | SOTI | +1 905.624.9828 | SOTI.net lDiscussion Forum | Log a Case Online l Facebook l LinkedIn l Twitter