No Matches Found!
Try with a different search term
I am looking for a way to delete the lockdown template file from a device.
Revoking the profile has left the lockdown file on the device, and now it has become impossible to install new lockdown profiles on the device.
Is there any way, either manually or using a script, to remove the lockdown file from a device?
Hi Rick,
Is this device(s) get back online after you delete the profile, and it's already removed from the device(s) Configuration side from MobiControl Webconsole.
For test purpose, you can create a new Folder, without assigning any profile, and then you can move this one test device to this new Folder to monitor whether it will remove the lockdown or not, as there may be any other profile including lockdown on your device's current folder. I hope it helps
Zafer
Hello Zafer,
Yes, the device came online after removing the profile.
I have dragged the device into a folder with no profiles. Everything gets removed correctly (package, feature control, etc.) EXCEPT the lockdown file. The device remains in a lockdown kiosk that shouldn't be present on the device anymore.
Is there any way to reach the kiosk file directly on the device and remove it?
It's strange, I'm just curious, did you have any chance to try:
disable the lockdown (by sending a legacy script such as _adminmode on or from remote control left-top corner and restart the agent or reboot the device whether the lockdown will appear back again?
And how many devices in total you have in this behavior? is it specific to any device OS version or agent version? or is it same for different ones as well?
disable the lockdown (by sending a legacy script such as _adminmode on or from remote control left-top corner and restart the agent or reboot the device whether the lockdown will appear back again?
Yes, the device immediately enters the lockdown kiosk.
And how many devices in total you have in this behavior? is it specific to any device OS version or agent version? or is it same for different ones as well?
There is currently 1 problem device, out of the 3 devices that we are changing to a new lockdown.
The problem device is the only one with MX version '13.1.0.14' (the other 2 are 11.6.0.17).
The agent versions are different for each device, the problem device has the latest: 15.4.6.1013, while the other two are '15.3.0.1006' and '15.3.4.1113'.
The OS versions are the same for all devices
Hi Rick,
To narrow down the possible issue and find out the problem, if you use Android Enterprise, you may try to use 2024 Agent version on this test devices. If not, if there is any newer version than 15.4.6.1013, you can also try this as well.
Otherwise, I'd minimize the variable, i think just in case, it'd be better to un-enroll the device and test with either '15.3.0.1006' and '15.3.4.1113' agent whether to it would work well or not. if it's works well by using one of these agents, if you wish you can also try to upgrade the agent version from other 2 devices that have 11.6.0.17 MX version and check out whether you will face same issue while upgrading to 15.4.6.1013
You can find the agents here :MobiControl Device Agent Downloads | SOTI Docs and you can update the agent version via a file sync rule or importing the agent .apk/pcg file as a package and then using the package under the Profile on MobiControl Webconsole.
Zafer
Hi Rick,
It's abnormal if all everything (package, feature control, etc.) except lockdown profile got removed correctly and the device remained in lockdown kiosk. Please make sure you have a profile with "authentication" payload deployed back to the device to see if the device remains in control and any change(s) in kiosk policies can successfully be made remotely on the device. If so, removing any lockdown template or data files shouldn't be a problem.
Hello Raymond,
There is definitely an authentication profile installed on the device.
I can also remove/add other profiles such as the package profile to the device.
There's been a small change all of a sudden, after the nth attempt. The 'old' lockdown profile has been successfully removed. The problem left is that the 'new' lockdown profile keeps throwing 'Install Failed'. Even though I can see that it was definitely installed .
I can't find anything related to this in the device logs to pinpoint the issue. Would you happen have any idea's?
Hi Rick,
we had the same issue now on one single device (out of thousands).
If it's the same on your side, try following:
1. Assign the lockdown profile to this device again and wait until it's installed
2. Revoke it from the device again (in the configurations tab in device details) - lockdown should be removed
3. Unassign it from this device.
Solved it from our end and currently was the one and only one we have seen this issue on.
Hi Rick,
Thank you for your post on SOTI Pulse, do you still require any assistance with the above issue?
Hopefully, you were able to solve the post by using the above-suggested solutions. If yes, please mark it as "solution".
Please let us know so we can proceed further accordingly.