Disable Lock Screen Shortcuts

Disable Lock Screen Shortcuts

Good Evening. I am running Samsung Tab A 8.0. All are Android+ ELM enrollments. Now we had and issue with a ROOT cert because some of these upgraded to OS10 and the server was running SHA1 and not SHA256. So we got SOTI on the phone really quick they got that all straightened up. Then.. We started hearing whispers that something done today broke the script:

writesecureprofstring  DeviceFeature 

DisableLockScreenShortcuts 1

 

apply featurecontrol

 

Now if I rerun on a TAB running 8.1.0 the script will do as it is expected to do. However if I send that same script to a TAB running OS9 then I got a return of: DisableLockScreenShortcuts unsupported.   Did the command change from 8.1 to 9?

7 Answers

Order By:   Standard | Newest | Votes
JVMOD@SOTI | posted this 26 August 2020

Hello Jason,

 

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.

 

Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |

  • 0
  • 0
Raymond Chan | posted this 27 August 2020

What are the active MDM API's reported by your device agent?

What about the version and build number of your devce agent? 

  • 0
  • 0
Jason Klotz | posted this 27 August 2020

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.

 

Very Strange.

  • 1
  • 0
Jason Klotz | posted this 27 August 2020

Hello Raymond,

 

Right now the Agent Version is : 14.2.2.1079

Mobi Version on this server is: 14.1.6.1113  (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:  

SamsungMdmV57, Samsung RC v1, 839
 
 
Thanks,
 
Jason

 

  • 0
  • 0
Raymond Chan | posted this 29 August 2020

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 v14.1.6.1113 really have the problem you mentioned, and whether a server upgrade is needed accordingly.

 

 

 

 

  • 0
  • 0
Jason Klotz | posted this 03 September 2020

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.

  • 0
  • 0
Jason Klotz | posted this 03 September 2020

JVMOD - The above script did not work in this instance.

  • 0
  • 0

Give us your feedback
Give us your feedback
Feedback