No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
Good morning all! I have a question in regard to the application permissions for MobiControl. Whenever in Device Owner mode wouldn't Soti be able to grant the needed permissions without any user interaction? We're currently up against the fact that we're deploying a lockdown profile to the devices upon enrollment. Whenever the device is enrolled and the profile is set before anyone grants permissions manually the user won't be able to grant the permissions after the lockdown kicks in place. The user does get the notification that there's a user action pending and after clicking the notification it show the MobiControl page where you can navigate to the setting required but that step is blocked due to the lockdown being active. I find it strange that even in device owner mode and enrolled using Samsung Knox/Android Zero touch the user needs to grant those permissions. We've currently scoped down to just system setting permissions but we'd like to leverage all permissions for the MobiControl app but user actions are definitely blocking us from that.
With the SOTI Apps permissions checked in the add device rule is there a way on Android 10 devices to send a script to auto accept those permissions? I'm enrolling Samsung SM-T307U devices and I am curious if there is any new development on this? Below is a reference to recent thread I read about this same topic for more context. https://discussions.soti.net/thread/permissions-2/
Is there an API that I can use to view what groups have rights to a profile and also update the security rights? I have a need to add a new user group and need to add it to 700+ profiles. Would really like not to have to touch each profile to update the permissions.
Hi, I want to give permission to allow customers to create users but not let them see and edit users of other customers, how do I do this? Hope there is a workaround for this problem. Many thanks!
Hi there, i have again a user-right problem which i want to be solved but get no solution by myself. We use "custom data" and i want our support to be able to see these fields (custom data manager) in device details. I have made a test user which seem to have full access (all boxes are checked for all folders and all permissions) but he can't see these fields. Only if i gave a user "mobicontrol administrator", he can see these fields. I see no difference between those settings. Anyone an idea?
Hi @Soti, I wanted to ask if it is possible to create and manage device group permissions with APIs. The background is that a customer has about 140 folders and he needs now certain permissions in each subfolder for a usergroup. Doing this manually about 140 times would be very time-consuming. Like described here: http://www.soti.net/mc/help/v14.0/en/console/devices/managing/groups/groups.html?hl=permission If someone knows that this is possible could I have an example how to create a device group and give user group permissions for this device group? Many thanks in advance. Best regards, Sven
Hello, In MobiControl since Version 15.1 I cannot longer add Groups in "Edit Permissions" in Profiles, only adding Users is possible. When try to add a Group, the Dialog Windows gets longer, but the space is empty. In MobiControl until version 15.0.1 it is working. I tried that already in Chrome, Firefox, Private mode, always the same non working in MobiControl 15.1.0 and up to 15.1.2. Martin
Hello dear SOTI-community, I want to enforce a lockdown on our Android devices with only two or three apps being offered to the user. Unfortunately, I currently have to enable the settings app as well, because if I update one of our apps (self-programmed app), the device will prompt the user for permissions, which he or she is not allowed to permit if the settings app is not enabled. I am already using a post-install-script, but the commands don't seem to work: afw_set_permission_grant_state com.ignitix.systemone net.soti.mobicontrol.permission.DEVICE_INFO allowafw_set_permission_grant_state com.ignitix.systemone net.soti.mobicontrol.permission.DEVICE_INFO_ELM allowafw_set_permission_grant_state com.ignitix.systemone net.soti.mobicontrol.permission.DEVICE_INFO_AFW allowafw_set_permission_grant_state com.ignitix.systemone net.soti.mobicontrol.permission.GET_DATA allowafw_set_permission_grant_state com.ignitix.systemone net.soti.mobicontrol.permission.GET_DATA_ELM allowafw_set_permission_grant_state com.ignitix.systemone net.soti.mobicontrol.permission.GET_DATA_AFW allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.CAMERA allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.RECORD_AUDIO allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.WRITE_EXTERNAL_STORAGE allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.READ_EXTERNAL_STORAGE allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.CALL_PHONE allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.ACCESS_COURSE_LOCATION allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.ACCESS_FINE_LOCATION allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.RECEIVE_SMS allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.SEND_SMS allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.WRITE_SETTINGS allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.VIBRATE allow;afw_set_permission_grant_state com.ignitix.systemone android.permission.WAKE_LOCK allowafw_set_permission_grant_state com.ignitix.systemone android.permission.ACCESS_WIFI_STATE allowafw_set_permission_grant_state com.ignitix.systemone android.permission.ACCESS_NETWORK_STATE allowafw_set_permission_grant_state com.ignitix.systemone android.permission.ACCESS_FINE_LOCATION allowafw_set_permission_grant_state com.ignitix.systemone android.permission.ACCESS_COARSE_LOCATION allowafw_set_permission_grant_state com.ignitix.systemone android.permission.BLUETOOTH allowafw_set_permission_grant_state com.ignitix.systemone android.permission.BLUETOOTH_ADMIN allowafw_set_permission_grant_state com.ignitix.systemone android.permission.CALL_PHONE allowafw_set_permission_grant_state com.ignitix.systemone android.permission.CHANGE_WIFI_STATE allowafw_set_permission_grant_state com.ignitix.systemone android.permission.FOREGROUND_SERVICE allowafw_set_permission_grant_state com.ignitix.systemone android.permission.GET_ACCOUNTS allowafw_set_permission_grant_state com.ignitix.systemone android.permission.INTERNET allowafw_set_permission_grant_state com.ignitix.systemone android.permission.KILL_BACKGROUND_PROCESSES allowafw_set_permission_grant_state com.ignitix.systemone android.permission.READ_PROFILE allowafw_set_permission_grant_state com.ignitix.systemone android.permission.READ_CONTACTS allowafw_set_permission_grant_state com.ignitix.systemone android.permission.READ_PHONE_STATE allowafw_set_permission_grant_state com.ignitix.systemone android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS allowafw_set_permission_grant_state com.ignitix.systemone android.permission.REQUEST_INSTALL_PACKAGES allowafw_set_permission_grant_state com.ignitix.systemone android.permission.RECEIVE_BOOT_COMPLETED allowafw_set_permission_grant_state com.ignitix.systemone android.permission.VIBRATE allowafw_set_permission_grant_state com.ignitix.systemone android.permission.WAKE_LOCK allowafw_set_permission_grant_state com.ignitix.systemone android.permission.WRITE_SETTINGS allowafw_set_permission_grant_state com.ignitix.systemone android.permission.WRITE_EXTERNAL_STORAGE allowafw_set_permission_grant_state com.ignitix.systemone com.honeywell.provisioner.ACCESS allowafw_set_permission_grant_state com.ignitix.systemone android.permission.NFC allowafw_set_permission_grant_state com.ignitix.systemone android.permission.CAMERA allowafw_set_permission_grant_state com.ignitix.systemone android.permission.RECORD_AUDIO allowafw_set_permission_grant_state com.ignitix.systemone android.permission.FLASHLIGHT allowafw_set_permission_grant_state com.ignitix.systemone com.android.settings/.Settings$AppWriteSettingsActivity allowafw_set_permission_grant_state com.ignitix.systemone com.android.settings.Settings$AppWriteSettingsActivity allowafw_set_permission_grant_state com.ignitix.systemone com.android.browser.permission.READ_HISTORY_BOOKMARKS allowafw_set_permission_grant_state com.ignitix.systemone com.google.android.gms.permission.ACTIVITY_RECOGNITION allowbatteryoptimize allow com.ignitix.systemone Although it should permit practically everything, our Android 7.1.0 devices still want the permission for system setting access and battery optimization from the user. Our Android 8 devices want even more permissions to be sanctioned by the user. Which script command will work properly? Does anyone have any experience regarding this type of problem?
Hello all, we work with soti mobicontrol in version v13.3.0.3454. We have a lot of devices under zebra tc75x android 6 enrolled with android + and mobicontrol client in version -> 13.3.2.1014 Well, I upgrade my device to android 7 but before to start the upgrade (stage now + rule) I uninstall all the app. After Upgrade and reboot device I re install the app (sygic nav / soti surf / …) but I need to accept PERMISSION .. I know I can install apk in silent mode with zebra stage now and a rule of mobicontrol that's work fine. But I've meet some problem when I do this on a large number of device … Perhpas some others solutions exists ? thanks a lot for your suggestions
I am trying to use the SOTI API to update packages in profiles and assign them to devices. Using PUT /profiles/{referenceId}/packages and PUT /profiles/{referenceId}/assignment our user has the "View profiles" and "Manage profiles" permission as well as "View and deploy packages" and "Manage packages" but we get response using Powershell System.Net.WebException: The remote server returned an error: (405) Method Not Allowed.
When I set up a data usage monitor under Rules > Telecom Expense Management, the newer Samsung devices require an elevated permission for the device agent to monitor data usage. This is under device settings which are not accessible as all the devices are heavily locked down, single-use devices. Is there a way to enable the permission en masse through Mobicontrol?
Hello all, we have the server on version : 13.3.0.3454 we have the client on version : 13.6.0 build 1476 we have some device on android 6.0 and we have some new device in android 7.0. We used the zebra TC75x as a device. Actually we have a lock down, in this html page we have some icon. These icons launch some links with soti surf. All works fine with android 6.0 and 7.0. But i have a little problem... My problem is when I installed Soti Surf on android 7.0, at the end of installation when soti surf starts I need to accept some permissions ... In android 6.0 it's not necessary ... I need to installs more than 100 news devices. Is there a way to accept these permissions automatically ? thanks
Using Android Enterprise, we can't see the contacts in the WhatsApp. When you open the app, it asks for the perssions, but you can see the contacts enabled and can't change the option cause is disabled by the MDM. So you can recieve messages but you can't open a new chat with any of your contacts.
Hi all, is there any possibility to select inactive local users which are not connected to MC for 90 days? Afterwards it would be fine to delete these users automatically. Our MC-Version is 13.3.0.3851 Best regards, Marcel
I'm trying to set up my Android Enterprise phone in Kiosk and Lockdown Mode. Kiosk mode is enabled but I get a message "Please give Draw Over Other Apps permission. This permission is needed for Lockdown Profile". Any idea what this is? Can I configure it remotely?
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points.
Highly experienced members with valuable inputs. Should have more than 700 points.
Beginners taking the initiative. Should have more than 500 points.
New contributors starting their journey. Should have more than 250 points.
