KACE Product Support Question

K1000 - Why wont my script deliver the package when I use "Run As"?

09/01/2015 1511 views

I have a script that requires elevated privileges to install. It runs perfectly when I double click on the file as my account has admin rights.

I created an on-line script in KACE, using the system account. Package deploys to C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots\ and tries to execute, but fails due to not sufficient privileges. I adjust the on-line script to "Run As", enter my account and password.  Steps seem to run, KACE shows completed and message box pops up. But no package is delivered to C:\ProgramData\Dell\KACE\kbots_cache\packages\kbots.

Any suggestions, advice, criticism, would be greatly appreciated as I am about ready to jump out the window. 

2 Comments   [ + ] Show comments


  • This content is currently hidden from public view.
    Reason: Removed by member request For more information, visit our FAQ's.
  • You can also use the PSExec command from the Sysinternals Suite to open a command prompt as system and see if the command runs manually that way. What does the script do?
  • Using PSExec worked with the script that I wrote. Installed correctly. But does not install using Kace.
    • Can you share the script?
      • call msiexec.exe /i "ATT_Connect_Participant.msi" /q /l* "C:/drivers/ATTv9.log" TRANSFORMS="ATT_Connect_Participant_ALL.mst"

All Answers

When using RunAs, and bearing in mind that the system account has no domain rights so cannot validate a domain account, you need to use a local account.
Answered 09/03/2015 by: EdT
Red Belt

Don't be a Stranger!

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

Sign up! or login


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