Disable Lock Screen Shortcuts
Thank you for your post, please try below script if your device is enrolled as Android Plus.
writesecuresetting –sys lock_screen_shortcut VALUE:0
Please let me know if this works for you.
Technical Support | SOTI Inc. |1.905.624.9828 | firstname.lastname@example.org | www.soti.net |
What are the active MDM API's reported by your device agent?
What about the version and build number of your devce agent?
Thank you JV. I should have a tester one again in a few days.
What I had found odd was I could not send the old script to the devices. However That script (mine posted above) was built as a package and then into its own profile. I found that if I revoked the profile and unrevoked the same profile it would work.
Right now the Agent Version is : 184.108.40.2069
Mobi Version on this server is: 220.127.116.113 (Yea it is behind, but this cluster controls devices that are pushed away from any Corp network due to payments) So I have to get 3 different groups to all agree. Sometimes easier said than done.
Agent API's reporting:
Based on the agent version of your Android+ Samsung device agent, I believe it should support your mentioned script commands well.
From the perspective of script command support, the MobiControl server version is unlikely to be significant. The device agent version as well as the device firmware are the determining factors. So don't worry too much about the server version being behind. However, if you consistently have problem with the command when sending it interactively with "send script" action, but not in ALL other script deployment approaches (e.g. pre-/post-script in .pcg package or file-sync-rules, geofence alert rule, out-of-contact profile, scheduled task profile, etc.), then you might need to confirm with Soti support team if your server version of v18.104.22.1683 really have the problem you mentioned, and whether a server upgrade is needed accordingly.
Thanks Raymond. Now we have run into where the OS10 devices are not enrolling. So we figure we have other issues now. Maybe they are somehow linked... or maybe they are not. So we have a current case open with SOTI.