Sounds like you are just wanting to stage the file before executing. I have done this before by using managed scripts. One to copy the file(s) from the server and the second to execute it when required.
If you do want to keep using distribution package (which does allow more control) are you able to post any specifics / script for the batch file being executed without giving away any sensitive info?
The purpose of the batch file is to silently uninstall IE10 from a user's machine (even if they have an IE session in use) without forcing a restart. This will revert back to the previously installed version of IE the next time the user manually reboots his/her machine. Contents of the batch file are as follows:
wusa /uninstall /kb:2718695 /quiet /norestart
Very simple. It works no problem when I manually double-click from the user's machine. However, if I try to execute it through a distribution package, it does not run (despite LANDesk reporting a 'Success' on the scheduled task).
What does your second batch file look like and what version of LANDesk are you currently on? It also sounds like you are creating the second batch file without really needing to. We can copy the original batch file to the machine and execute it in the same task so you don't have to cache the first batch file then call a second batch file to reference the first for the command execution. In your current scenairo we are reporting a success against the batch file being used in the distribution task and not against the batch file that you have cached for which the second batch file is referencing and executing.