It always happens again, that a client stays active in the provisioning task, but when I look trough the Provisioning history all actions are done.
I checked the ldprovision.log and it seems, the client lost connection after a reboot (it's not at the end from the template). After several tries of calling the webservice, the log ended. BUT ca. five minutes after the last entry in the log, I can see he has done the further actions. The executefilehandler.log shows me that he executed the last action.
In the picture you can see all action are checked successful and I saw, he ran the last actions. So why ended the provisioning logs and why is this client still active. Had anyone else to do with such a behavior?