Hello Remi

Greetings

Thanks for your post to Soti Central!!

Kindly provide  some other details as mentioned below for checking with our use case.

Device management or enrollment type (Android enterprise (work manage / work profile ) or Android plus) 

 Device manufacturer 

Regards

Hello,
I already mentioned it in my message (Android plus) for the manufacturer it is Unitech, model : PA720
Thank you.

Hi Remi,

Please note that "watchsettings" script command only works on devices from a very very small number of OEM brands on legacy Android+ platform, and virtually not at all for Android-Enterprise platform.

As you are likely be be using OEM specific legacy Android+ device agent on your Android 6.0 device, and the watchsettings script command doesn't work on it, I can dare say your chance of having any script command to deactivate screenlock with "writesecuresetting" is close to zero. 

However, instead of using script command,  I think it is reasonably easy for you  to achieve what you need simply by modifing related parameters (or revoking) the authentication profile payload.

Hello.

The watchsettings command works but does not show a log when we manually set the lock screen to "None" on the device. I was able to test some commands (eg timeout) with writesecuresetting and it works.

These devices are configured with a kiosk template so the idea is of course to do it automatically.

Have you tried the Reset Passcode action ? For Android Classic agent it should work for Android 7 or prior.

Hello.

Unfortunately this action does not work.

Hello Remi

Greetings

Thanks for your reply.

As we know , watchsettings on script usually supported  on Android oem devices  and you must be able to see logs ,  in your case unfortunatley , you are not able to see any log enteries after setting screenlock to none (manually) so i will suggest you to try out the following things if possible.

• Try to send script  resetpassword  and see if it works or  you get anything in logs.
• Try to update the agent of one of your test device to latest one and try to test and see  if again its  not showing anything in log section of device.
• As script behaviour varies in different  devices  so You can also try to confirm if the issue is reproducable on multiple devices of same os and same model. (if it is reproducable , you can also test with different os or may be different model no too from same manufacture.) 

If still this issue is not resolved from your end so might be we need to investigate after getting logs from device end after reproducing issue and also we can test this device in different mobicontrol version  too but for that i will suggest you to create a case with soti To get assistance with this , I would like you to create a support case(click here) or call SOTI Support team(click here).

Also, if any of the  post has helped you in solving your inquiry, I would request you to mark the particular comment as "is solution", so others may benefit from this information.

 Regards

Hello.

I notice that nothing allows to define the type of locking of a device on SOTI.

Thank you for your help

If you don't need any screen lock PERMANENTLY, you don't send any script to set the lock-screen mode to "none". Instead, you can simply revoke any deployed profile with authentication payload that configures user password options.

You can select to disable Lockscreen completely from the Authentication Payload on Android Enterprise profile and User password

Hello,
My case is Android Plus platform not Android Enterprise.
Otherwise yes that would be the solution.

Thanks

It's the same on legacy Android+ platform.  Disabling passcode and deploying an authentication payload with no User-Password -Policy (but with non-null Device Administrator password configured) should solve the problem.   I had done similar things successfully for many tens of device brands/models runnng legacy Android+ device agents for many years long before Android-Enterprise was introducted.  If you failed on your test device, you probably did your test in the wrong way.

I asked Soti the question in a case.
It is not possible to change the lock type on an Android Plus / Classic device with an Authentication profile.

I don't know who in Soti gave you the answer when you opened your case.  Maybe you meant something different when you said changing the lock type on your device, and there was some misunderstanding between different parties.

Your statement "It is not possible to change the lock type on an Android Plus / Classic device with an Authentication profile" is not generally accurate,  as I've just remotely changed the lockscreen type from password to none on my test device running a  v14.4.4 OEM specific Android+ device agent,  just like what I did with many other Android+ devices over the years.   Of course, not all Android+ device agents are alike, and some implement fewer features than others.   To avoid other forum users from being misled by your inaccurate statement,  I need to make a clarification here.