/bundles/itninjaweb/img/Breadcrumb_cap_w.png

I created a Kace script to install software. I tried doing it 2 ways:

1. A script to install a managed installation

2. A script that "Launches a program" by copying an executable to $(KACE_DEPENDENCY_DIR) after uploading an executable as a dependency

The reason I'm using a script is because I need to perform multiple tasks however this is the first task I'm trying. If I run the managed install manually from "Distribution" it works perfectly. When I run the manual install through the script and when I run the script with the "Launch a program" the script starts because the "User" is notified by a pop up box, after that nothing happens however the "Run Now Status" shows the script as successful. I also see that when I run "Launch a program" script the executable does get copied down to C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots\"script number".

I'm not sure how to troubleshoot this issue. I have no idea why this isn't working. Please help.

5 Comments   [ - ] Hide Comments

Comments

  • Can you let us know what script you are attempting to run? It sounds like an issue with the script itself.
  • Hey thanks for the response. If I understand what you are asking you are thinking I'm trying to run a pre-written script. That is not the case. I'm trying to use Kace scripting to run a managed install or run an executable. FYI I've tried with 2 different executables to make sure it wasn't an issue with the executable. Does this make sense?
    • I pick up that it's a custom script, but It sounds like there is a fault in the script itself. Can you paste the log for us?
  • Forgive me here but which log? Are you looking for the log from the PC in inventory like this or one of the text logs I can pull from the PC?

    Output Log
    Running as SYSTEM

    Activity Log
    verify - on_verify_success
    verify - on_verify_failure

    Debug Log
    Running kbot: runkbot 142 1521135961
    KBotScript::LogScriptInfo - Start
    id=142 name=Install Deacom Local version=1521135961 type=policy
    execute disconnected=false logged_off=true
    execute events
    KBotScript::LogScriptInfo - Finish
    KBotScript::LogScriptInfo - Start
    id=142 name=Install Deacom Local version=1521135961 type=policy
    execute disconnected=false logged_off=true
    execute events
    KBotScript::LogScriptInfo - Finish
    KBotScriptManager::CleanupDependencies - clean up dependencies in kbot directory C:\ProgramData\Dell\KACE\kbots_cache\\packages\kbots\142\
    CleanupDependencies: file Deacom.Local.Installer.exe is part of the dependency list, keep the file
  • Can anyone help?
  • I got the first part working by removing "Create a message window" and "Destroy a message window". They were present before and after the installation. I'm not sure why they caused a problem but once I removed them the install ran.
    • IF you're still having trouble, can you post the full xml of the script? (Click "Edit XML" button right above "Dependencies" and below "Schedule")
      • I think I'm ok for the moment but thanks for replying. I'll post again if I need help.
Please log in to comment

There are no answers at this time
Answer this question or Comment on this question for clarity

Answers

Admin Script Editor
Admin Script Editor is an integrated scripting environment available free here at ITNinja

Share