Not able to get a batch file to run properly
I've got a script created in my K1000.
Set to use domain admin credentials.
I have a batch file as a dependency but I've tried without it listed. It shouldn't be needed as you will see below.
I have Verify section blank... I have "On Success" section with "Launch \\server\share\setup\mybatch.bat" with params ""
Other sections like Remediation etc are blank.
When I run the script a command prompt window opens for a second, and then closes. In the event log a MSI installer transaction is started and then another event says it is finished. It's like it immediately fails to continue the msi.
The weird thing is, I can log into the pc locally as the same credentials (domain admin) and browse to the \\server\share\setup\mybatch.bat and double click that batch file and it runs just fine and installs the software...
What is the issue?
2 Comments
[ + ] Show comments
-
Similar issue here also. Batch file runs fine if I manually launch it by double clicking on it. When I push it out via KACE in a scripted install under the Verify On Success step it seems to run through the various steps within the batch file too fast without actually installing the software or waiting for each step to complete before moving to the next step. Any Ideas? - anonymous_123518 6 years ago
-
Having this problem as well. One thing I notice is that bat files have to run with elevated permissions in Windows 10. When pushing it as a KACE script, it says it runs, logs as successful, but never runs the batch file. However, locally I can right click, run as administrator, and it runs without any issues. If you figure out a way to run batch files with elevated permissions from a KACE script, I would love to know. - Gary.Cooper 6 years ago
Answers (1)
Please log in to answer
Posted by:
akmagnum
6 years ago
Almost certain it is a "permissions issue".
Try giving "everyone" permissions to the folder to.
See what happens.
Comments:
-
Everyone has full control on the share and all files/folders beneath.
The script is running under domain admin credentials also. - theviking28 6 years ago
