SOTI Pulse Logo

Android : Launch-able SOTI Script shortcut on SOTI Lockdown

Solved
BR
Ben Ragland
Zebra (OVS) - Manhattan Associates

Hi there, I am wondering if anyone has successfully placed a SOTI script on the SOTI Lockdown utility on MobiControl 13.4.

I have attempted to accomplish this but delivering a script file to the desired device then reference that file in the Lockdown config but when tapping on the created hyperlink, it either doesn't have any response or states the file is incorrect. My script kills an app then starts it when executed. I have validated the script syntax by sending it manually to the device.

The Device Script Commands seems to imply this is possible based on the attached screenshot but I would like more clarification on what the file extension of the script file being delivered needs to be and which initialization method I need to use specific to scripts. (Launch://, File://, etc)

lockdown script scripting
Edited 7 years ago
Android
ANSWERS
BR
Ben Ragland
7 years ago

I got this working as Raymond and Matt suggested.

With Zebra MX/Android, you must specify the Lockdown shortcut as "script://%sdcard%/posti.cmd".

The Lockdown shortcut is calling the posti.cmd script being delivered to the sdcard directory via package. I simply used the default destination path to deliver this "%sdcard%\"

It seems I have gotten used to leaving out the % in most of my use with ADB and SOTI scripting.

Much thanks for the assistance!

Solution
RC
Raymond Chan Diamond Contributor
7 years ago (edited 7 years ago)

Hi Ben,  based on what I did from a few years ago, you can use

     script://your_script_file_path/your_script_filename.cmd

The default filename extension is .cmd, but I think anything will do.  The tricky part is to reference the path to your script file on your device brand/model, which might have a different file hierarchy for different device brand/model.  However,  all Android devices have the default "download" directory in the on-board Flash, which should be easily referenced with MobiControl macro  %sdcard%/Download.  Please note that  the macro %sdcard% here does not refer to external add-on SD-card, which might be referenced with another macro, %removablesdcard%, for some device brands/models in Mobicontrol v13.3.0.3851+ & v14.0.2+ according to the latest Soti online info. 

So, if you have a script abc.cmd in the default "Download" directory,  you should have the following for your lockdown menu item:

  script://%sdcard%/Download/abc.cmd

 Some devices/firmware/webview engine might use/interpret  \ as path delimiter.  Please verify on each device model you are using.   

MD
Matt Dermody Diamond Contributor
7 years ago

Your screenshot was cut off @Ben! Just kidding its listed in the 12.x documentation, not the 13.

BR
Ben Ragland
7 years ago

I'll give these suggestions a shot later today.

I have already tried delivering a .cmd script to a device while using the script:// method but maybe I had something wrong.  

JM
John Maye
3 years ago

I have been trying to get this to work for me. I am beginning to wonder if this type of just isn't supported for my devices or agent...  I am running MobiControl Version: 15.4.1.4828  - Agent Version 15.1.2.1075

TC72 handhelds OS: 8.1.0

my .cmd script file consist of the following syntax:    kill_application virtualwarehouse.virtualwarehouse

So I can run this from a remote session through MobiControl exactly as shown above but executing it through kiosk (lockdown mode) does absolutely nothing. 

Here is the path:  script://%sdcard%/Download/killvirtualwarehouse.cmd

I am looking at either an incorrect call of the script or just a flat out incompatibility.  Also want to highlight that I have absolutely toyed with the delimiter variation where I've found that what I am using (backslash) should be the correct option seeing that forward slash alone errors out in execution from the lockdown screen.  Let me know what you think!  Appreciate you.    (sorry I couldn't upload any screenshots for some reason)

JM
John Maye
3 years ago

It appears I made a mistake and posted my question as an answer.  Raymond are you able to see my initial post to this topic on February 4th 2022?

Similar Discussions