KACE Product Support

I'm referring specifically to running batch files from the task section of a script.  I have an install script that is really just a small batch file and it keeps failing even when it shows as a success.

I'm having some K1000 scripting issues where the script will push the dependencies, but then fail to run them and still count it as a "run success."

Here's what I've done so far.  First, I broke the single batch file up into separate files to segregate the commands and make sure they weren't tripping over each other.  In the very first one, I put a few taskkill lines to end the processes of the application I'm trying to update.  If I select "wait for completion" on this one then the script just fails outright and logs it as a run failure and, from what I can tell, rarely actually runs that batch file.  I specifically routed the standard out and error to a text file for each line to see if it ran.  Sometimes it does, sometimes it doesn't.  But the script will never succeed if I mark any of the batch files as "wait for completion."

So the alternative is to not do that, which usually results in kbox copying over all the dependencies and then marking it as a run success without running any/all of the dependencies.

This is all done as the local system account.  None of the batch files are trying to touch anything but the local machine.  For the life of me, I cannot figure out why they often fail to even run.