I use a similar approach with the ldprovisioning.exe. I found that provisioning cannot really be set as a "policy" unless the machine is turned on when you hit "start now" during your scheduled template. If the machine was off then the provisioning template would just stay in a pending state forever. So my workaround was to copy the ldprovisioning files to the c:\drive and then when i had a provisioning template scheduled, I would force the connection by calling ldprovisioning.exe.
This worked great for installing software during a deployment during first log on.
however instead of copying the files from the core server, i booted off a winpe provisioning pxe job and then copied the files that were downloaded from the core which ended up in x:\ldprovision.
Hopefully future update to provisioning will help us out better so we dont have to use these workarounds.