Hi Bastox,
Do you have any *.log files from a provisioning attempt? I've seen a couple instances of this message but typically it occurs around the CTOS action. If your machine is in WinPE, check for them at X:\Ldprovision. If your machine is in Windows (not WinPE), check for the logs at C:\Ldprovision. If this directory does not exist, please open your Provisioning template to edit, click on 'Options' on the left hand column, and uncheck 'Remove client provisioning folder'. Next run the provisioning task again and the ldprovision directory should be created and remain after the test. If you can post the *.log files we can take a look and see if something stands out.
Also, what version of Core are you working with?