Hi Joao,

From what you explained, you set the PIN from SOTI?

As far as i know, SOTI can only enforce the PIN policy, as for the PIN number/pattern, it's down to the user to set it.

If you set the schedule, what i had in mind is :

If the PIN already set first time (by the user) when the device enrolled, the schedule task won't enforce the user the set the new PIN.

Thanks & regards,

Randy Saputra

There's currently no possibility to get such an error message.

As our experience, every user always "never" has reset the pin... but they do.

I think i wouldn't go the way for every 2 hours because the device will be then locked everytime it's executed.

And if the device is still locked, next time the device has to be unlocked 2 times instead.

We do this once every day during night, so you don't effect the work of your users and it's taking some kind of "learning effect" because they see everyday the old pin again and will stop to change it.

But i don't know why your devices are offline only because of Pin. Did your devices somekind of reboot, so the pin is needed for data connection?

As the device is shared by users, they have a standard PIN.

The issue is the user receives the device and after some time already working, it locks and the standard pin is not accepted any longer.

Our support team resets it to a standard pin and the end user may continue to work.

The issue is to really identify if the end user has changed it or something else has. As the effect is the PIN is changed and no connection after it (when support could help them), we would like to track down what has changed the PIN and avoid it.

We have also other 2600 Samsung device, but A10S, that PIN is changed only by Script from our team.

Hi Rafael, we have realized the Lock Screen and set the change twice a day.

Tks for the tip.