Clock Alarms - Set & Lock

Solved

Hello!  Trying to find the best way to make alarms work, and would love if anyone has any insight on what has worked (or doesn't).

The goal:  Android Device is used by a Supervisor for a Security Shift.  We want to set various alarms and reminders at certain times (i.e. Verify all officers clocked in at whatever time, Check certain site for whatever, Start fueling vehicles).  However, we DON'T want these alarms to be accessed by the user and altered, silenced, or otherwise changed.

- The included clock app on the phone allows a schedule to be set, but I'm unsure the best way to lock it from being changed by someone other than the Admin.

- Using SOTI's send message feature, is there a way to set those messages to be automated (and it's not on the device itself for anyone to mess with...).

- Any other ideas that might work well?

3 years ago
Android
ANSWERS
RC
Raymond Chan Diamond Contributor
3 years ago

You can use "Task Scheduler" profile payload that deploys pre-pushed MobiControl script having both "ring_device" and "showmessagebox" commands  to give audible alarm & display alarm-type message at the required time/time-interval.

Solution
CS

Thank you!
I definitely think that's the best way -- that way I can assign the profile to a different device as needed, we have all the loggin ability that we'd like, and it keeps it seperate.
Thank you Mr. Chan!

RC
Raymond Chan Diamond Contributor
3 years ago

In addition, if the "Task Scheduler" payload  is kept in a  dedicated  profile with no other payload,  you can choose to use custom attribute(s) or other device properties as filter to get the policy deployed to relevant sets of devices.

CS

Interestingly enough, I am consistently getting an error that "Device Configuration Failed - Failed to Download Script Files".

In the Configuration Profiles on the devices they are listed as "Pending Install" - Forcing doesn't change it.

The profile details are also showing "Pending Install" to the devices assigned.

The created profile is an Android - Work Managed profile (consistent with my other profiles).

Using MobiControl 15.5.0.1021 - and the profile is stuck pending install on 2 different devices (Samsung S22, and Doogee S61)

CS

SOLVED!

One of my scripts has a ":" in the name, which put it in the .cmd file name (which I'm assuming was the cause of the digital coronary....)

As soon as I re-did it and took it out, everying pushed just fine on all devices.

Mission accomplished.

RC
Raymond Chan Diamond Contributor
2 years ago

It's good to hear that the solution works for you eventually.

To play on the safe side, I myself only use standard alphanumeric characters and underscore for naming  any of my .cmd script files., and totally avoid using space or any special characters.