The unlock command by definition is to force the device to exit the lockscreen without the need to input the correct password.  I can't see any similarity or relation with remote control session.

An administrator can still freely, at any time desired, send an "unlock" device action from the web-console or run the unlock script command in the command shell of a legacy non-html5 remote-control session to make the device exit the lockscreen.   If that is supported and an unlock script command is automatically sent whenever a remote-control session is started, I believe there will then be security concern, especially when the remote session is forced closed due to poor network connection/bandwidth.

I am not aware of, and do not thnk there is any real need to have, any script to be run AUTOMATICALLY whenever a remote-control session is started.    

What are your trying to get with this?
I mean, if it's a fully managed device you should know the pin. And as raymond already said, the unlock command will remove the pin, not just temporarily unlock the device and has to be set after your session again to not have an unlocked device afterwords.

Hi Patrick,

Thank you for posting on SOTI Pulse! 

This does not seem to be an implemented feature within MobiControl to start a remote connection and have the device exit the lock screen automatically. 

What would be the use case for this? Perhaps you can raise a feature request with us if this is a major concern.

Kind regards,

Technical Support Specialist | SOTI | +1 905.624.9828 | SOTI.net lDiscussion Forum | Log a Case Online l Facebook l LinkedIn l Twitter 

Hi Patrick,

I have marked the relevant post as solution. If this post did not assist you in resolving the issue and you have additional questions, please do not hesitate to reach out.

Kind regards,

Technical Support Specialist | SOTI | +1 905.624.9828 | SOTI.net lDiscussion Forum | Log a Case Online l Facebook l LinkedIn l Twitter