Why do some of my dependency batch files fail to run correctly through kace but run with no problems when ran manually from the local dependency directory?
The script logs show that the dependency batch file was executed (under the Activity Log) and the Output Log shows that it ran as the System. I even enabled redirection within a test dependency batch file, where the standard output and error output from each command is written to a new text file at the root of the c: drive. Those output text files don't show any errors that may be the reason that I didn't get the desired result from the batch file within kscript.
Like I said, when the kscript "runs", I see that it didn't do what it was supposed to do so I go to the local dependency directory of the kscript and run the batch file manually and it works perfectly. It's not the kscript configuration and it's not the code in the batch file.
Sometimes certain kscripts work and then sometimes those same kscripts don't fully work.
Is this a bug?
Is this a UAC issue in Windows 7 where the system account doesn't have privileges to execute certain commands? I also have the same issue in Windows XP, but less often.
Also, I'm not trying to access network shares within batch files or kscripts. I've had issues in the past accessing network shares when running as my domain\user account within Online Kscripts, needless to say that I have permission to access those shares.
Answers (2)
I have had issues with this as well with certain commands. I've usually found I can pick the script apart and narrow it down to one line that the KACE simply does not want to run.
One thing I did find that isn't readily documented is that when you do an online shell script, you need to change the script file name extension appropriately. The default is a bash script.
In order to test if the script runs as system you can use PSExec to open a command prompt as system. That will help eliminate one factor in your problem.
