/build/static/layout/Breadcrumb_cap_w.png

Running a batch file after copy to local machine

I am trying to copy and uncompress a folder using the below online kscript. The copy and creation of the folder works fine however launching the .bat file does not work.

If more info is needed please let me know.

Rich


1 Comment   [ + ] Show comment
  • I've added the correct path however it doesn't appear to even get to the Remediation part. The activity log ends at unzipping and nothing after that. - studio196 9 years ago

Answers (3)

Answer Summary:
Posted by: vjaneczko 9 years ago
9th Degree Black Belt
0

You'll need to use CMD.EXE from the Windows System folder.

Posted by: Michael4732 9 years ago
Purple Belt
0

Why are you using cmd.exe? Why not just use the "Run a batch file" option and enter the contents of your script in there?

Posted by: dugullett 9 years ago
Red Belt
0

So remediation will only run if your verify fails. Look at it as how do you want to remediate this first step not being there. Your verify is looking for your ZIP file that you uploaded as a dependency. So that verify will always be successful, and then unzip. It will never move to the remediate since it was successful.

I'm not sure exacltly what your .bat is doing, but you may want to try something like this.

Verify: Look for a file or registry key that you .bat is copying.

Success: Log message. .bat already ran (or something similiar)

Remediation: Launch $(KACE_DEPENDENCY_DIR)\CPUU_Update.bat (still uploading you ZIP as a dependency)

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ