Page 1 of 1

[Solved] Thin client shutdown after having started in remote management

Posted: 20 Sep 2018, 14:14
by forstera
Hello all,

I probably made a mistake in my config file because my clients stop just after being started.

The thin client automatically connect to a windows multipoint server (school classroom) and I first had the following line in my file.
run_command=while true; do xfreerdp /v:IP-server /cert-ignore /u:student /d:multipoint /p:student /load-balance-info:"tsv://VMResource.1.Students" /f; done
but I wanted the computer to shutdown when the user was disconnecting from the server. With the command here above they were re-connecting automatically.

So i changed that line with the following :
run_command=xfreerdp /v:IP-Server /cert-ignore /u:student/usb /d:SRV-MULTIPOINT /p:student/load-balance-info:"tsv://VMResource.1.Students" /f; halt
but now computers just shutdown after having started.

so, I'm wondering what I should do solve my problem, maybe this ?
run_command=while true; do xfreerdp /v:IP-Server /cert-ignore /u:student/usb /d:SRV-MULTIPOINT /p:student/load-balance-info:"tsv://VMResource.1.Students" /f; done ; halt
Per advance, thanks for your help

Thin client shutdown after having started in remote management

Posted: 20 Sep 2018, 14:41
by fanthom
This command is fine:

Code: Select all

run_command=xfreerdp /v:IP-Server /cert-ignore /u:student/usb /d:SRV-MULTIPOINT /p:student/load-balance-info:"tsv://VMResource.1.Students" /f; halt
it tells the system to halt when first command finishes its execution.

I believe the kiosk client cant connect to your RDP server and thats why the kiosk shuts down immediately.

Thin client shutdown after having started in remote management

Posted: 20 Sep 2018, 14:51
by forstera
Ok, thanks very much for the informations ;)