No Matches Found!
Try with a different search term
We have Samsung M20 devices
We have applied factory reset and safe boot restricted profile
it was working fine until the device get the latest android update.
after the update now even we revoke the profile from console the factory reset not enable.
even it is not enable when switch to the Administrator mode from MC agent.
and there are some other issue. I noticed in the API info field on the device information in MC console its only shows Remote view and work managed.
Did you try to restart the agent via script?
_resetfailedrcdetectionflagrestartagent
I will try your script.
but I tried "identify_activity" script.. that also not recognized. the issues are only coming for android 11 updated devices.
So a working devie updated to A11 has this issue. How about newly enrolled A11 devices, so A11 directly from the start?
It very looks like something to investigate with Soti in a case.
even for new android device getting the issue.
Several support cases have opened. actually there are few customers around here.
but the support team keep saying that this is because of the samsung has removed their knox APIs from their low end devices thats why this kind of issues coming and there are no solution or work around from soti.
some customer getting kiosk mode related issues, some getting script related issues.
problem is even the reset profile revoked the factory reset not available.
there is another customer that block device settings using manual blacklist script. now they cant access the settings when they need because the manual blacklist cannot off using the script.
Hi Ruwan,
Thank you for your post on SOTI Central.
I have discussed about this issue internally. This is the known issue for Samsung OS11.
Before Android 11 some Samsung devices were reporting that they support Samsung KNOX API, from Android 11 they stopped doing so.
Clients who had Disable Factory Reset DFC enabled on Android 10 (and before) had this restriction enabled using Samsung KNOX API.
After upgrade to Android 11 these devices stopped reporting Samsung KNOX API so Agent cannot use it to revoke the restriction - instead Agent using Google EMM API which is not interchangeable with Samsung KNOX.
As a result, clients are left with this restriction applied with KNOX API.
There is a Jira ticket MCMR-28945 regarding this issue which has a workaround for it. Please kindly log a case with Support and mention this Jira number.
Kind Regards,