/build/static/layout/Breadcrumb_cap_w.png

KACE scripting

I'm using a script to deploy/provision Intel Vpro.  In order to do that, I need to run EMAAgent.exe in the same directoy with it's accompanying file, EMAAgent.msh.   

In my script, I put these 2 files as dependencies (see screenshot).  In the script, I launch the .exe file with the correct parameters.  It launches successfully, but it does not provision.  I'm guessing it's not seeing that extra file, the .msh.  I assumed that because I was lauching it from the KACE dependency directory (Launch $(KACE_DEPENDENCY_DIR) \EMAAgent.exe with params -fullinstall”), it would be able to see the .msh file existing in that same directory.


Can someone please confirm?  Any advice on how best to accomplish this?



Thank you


0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: Mashby1 1 month ago
Purple Belt
0

Top Answer

It is not as simple as taking out the extra space? Try $KACE_DEPENDENCY_DIR\EMAgent.exe
Weird that it would still install though if that was the issue. 
Another trick I have used when a file is required to be in the same location is zip it up and extract locally and run from there. For example:


the first verify step:
Unzip 
$(KACE_DEPENDENCY_DIR)\EMAgent.zip to C:\Temp”  *** If the "scripting" user can write there or somewhere else it can

then your launch step On Success.

I have not worked with Vpro specifically but some exe are just a PIA in my experience. Double check that running NOT in Kace works, incase it is an issue with the config file itself. 



Comments:
  • I like the idea of unzipping in that location. I will give that one a try. Thanks - CSVNinja 1 month ago
 
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