Scripting Question

Kace creates an empty dependency directory.

08/22/2016 1917 views
I've created a script to uninstall older versions of Java and install the latest version. I've had success with this script on about 10 PC's on my domain, but a large portion of them have the script fail in execution. 

When I view the log it shows this: 


As you can see it verifies that the dependency directory is created but then fails to find the dependency files i added to the script:


I have UNC'ed into the computers that failed and went to the kace dependency folder (c:\programdata\dell\kace\kbots_cache\packages\kbots) I found the corresponding dependency directory, in this case 1098 that was created, but when i open it neither jre-8u101-windows-x65.exe or even the kace script batch were in there. As I stated before this worked multiple times in testing on my own machine as well as a hand full of other machines on the network.
0 Comments   [ + ] Show comments


All Answers

are you using replication on your k1000?
I have had two different scenario's I have found cause this.

First one is:

your amp.conf file does not have the FQDN of the server in it.
it will say kbox instead of kbox.acme.com in the file

Second one is:

If the machine is pointed to a replication server and you do not have "failover to appliance" checked in the replication settings and the files have not replicated yet that will happen.  You have to either wait for replication to occur or check that box and save for instant results.
Answered 08/22/2016 by: SMal.tmcc
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

View more:


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