Please give details about your problem(s) and what you mean by "restarting" your kiosk.  Is any key stuck? The whole screen hanged or corrupted? or What?

Could you solve your problem by restarting (cold or warm reboot) the whole device instead?

What do you expect with your so-called restarting, and why you think restarting can solve your problem?

Thierry - There is a script that will allow you to restart the agent, but like Raymond has mentioned, please give us a bit more detail regarding your situation and what you want to accomplish. 

Restarting the agent script: restartagent

Dear Soti,

I now use the script:

writeprivateprofstring Kiosk useFullscreen 1
restart agent

We do this because otherwise the screen of our tablets (Samsung Active 2 and Samsung Tab S3) cannot be operated properly. The top of the screen does not rule on touch. After the execution of this script, the Mobicontrol agent is restarted. After the restart of Agent, the kiosk screen is displayed again. As a result, a menu item in the kiosk screen no longer starts automatically. Perhaps this will start if I also restart the kiosk screen after the agent restart?

The inability to operate the screen keeps coming back. The script provided by Soti unfortunately only works temporarily.

I hope you can help?

I'm not from Soti.

I don't know exactly what you meant when you said "The top of the screen does not rule on touch".  I have tested over 50 different Samsung phone/tablet models in the last few years and virtually never have any problem with many tens of kiosk we wanted to set. 

Whatever your problem is, it may be caused by one or more of the following:

- improper mode and options set in your kiosk mode configuration in your profile

- conflicting feature control and/or application run-control policies

- improper html/CSS template or javascript

- bugs in the app that has been launched

- bug(s) in your device firmware and device agent

etc.

In any case, I don't think sending a script to your device is a viable solution if the device keeps on having the same problem again, as you can't have an administrator sending such script to a device via the console every time a device end-user reports the problem on his/her device.

As you have not given answers to most of the questions asked, maybe it's better for you to open an official support ticket with Soti so that they can possibly perform a remote session and see what your actual problem is.