There are few logs that you can look at in order to help troubleshoot this.
First, on the core server side there is a log that gets created:
Prov_schedule_exe.log (In the Log subfolder under LDMAIN)
Then the client side, before the template ends, there will be a C:\LDProvision folder (if in Windows) or X:\LDProvision (If in WinPE).
Within this folder there will be an LDProvision.log and also some handler logs.
LDProvision.exe is the main process that runs the Provisioning template, and then it hands various work off to handlers.
These handlers all have logs associated with them. The name of the log is the same as the handler file name, which typically reflects the Action name.
This document details the handlers and their logs files: http://community.landesk.com/support/docs/DOC-29699
So in your case of a Distribute Software action failing, we would want to see the following handler log:
In addition \LDCLIENT\DATA\SDCLIENT*.log from the client can be useful in troubleshooting this issue.
Just to confirm. The template works fine without the package, but when you include the package is it just the package that fails or the entire template? I want to clarify just in case.
MarXtar Ltd/MarXtar Corporation
LANDesk Expert Solution Provider
The One-Stop Shop for LANDesk Enhancements
Update - New Stand-Alone State Notifier Console for Service Desk Operators
Update - State Notifier now detects machine and user Idle states
Update - WoW & State Notifier now integrate for even more functionality