Just in case someone else runs into this... The executehandler.exe was missing from the \\<coreserver>\ldlogon\provisioning\windows directory. This can happen if ldprovision.exe is launched locally on the server from that location (not Chis's doing). When ldprovision exits it tries to clean up after itself. If you have a need to launch ldprovison.exe locally on the core, copy it into a seperate directory. It will copy over any needed files as it runs and will usually clean up afterwards.
New to LANDesk and using the ldprovision.exe to install a large sequence of software with several reboots.
I start the "ldprovision.exe" from the "ldlogon\provisioning\windows"
I am suffering from the fact that al my handler.exe are being deleted from this share.
So I am very happy to find this message.
So using it directly from the server is not the best idea...
But what is the best approach?
How am i supposed to start "ldprovision.exe" process on my clients ( winXp/Win7 ).
Thanks for the help.
You can copy ldprovision.exe from the core to the workstation and place it into it's own directory, then launch it. This will allow you to select the template and any needed handler files will be copied down to the directory with ldprovision.exe in it.
You can also schedule this template from the console. Right-click on the template and select "Schedule".
This will create a scheduled task with that template. Drag your targets to the task and start it up. This will automate the creation of the ldprovision directory on your client and start the provisioning task.