KACE Product Support Question

After 6.3 Update, Noticing machines under a single ORG appears to be stalled in check-in.

03/13/2015 2722 views
Hi guys,

Wondering if anyone has any thoughts on this - I recently upgraded our K1000 to version 6.3. The agents out in the field are a mix of 6.0 and 6.2 agents (have not deployed 6.3 agent anywhere yet due to reported performance issues). 

However, I'm noticing via the System Dashboard the kbot is consuming about 94-96% usage. When I look in the agent status, I see over 80 machines for a single org have the following:


They have been running well over 30 minutes - and I think they are just timing out eventually. Other than this, the KACE box appears to be running fine and agents are updating - although slower (I imagine because of the building queue). 

Anyone else running into this? Haven't rebooted yet - not sure if a service is to blame or what. 
3 Comments   [ + ] Show comments


  • Do you mean you have multiple orgs and seeing the issue only on one of them? We are running into the same issue but we have multiple orgs and it is only having issues on the main org.
  • Hi Pudenznl15 - after digging into this for a few hours, we discovered that we had a script that was hanging immediately after the server upgrade. Stopping this script and re-creating it in 6.3 solved our issue.

    Check your scripts - you may need to re-create one. Hope this helps!
  • We are having a lot of issues with agent check-ins as well along with issues with scripts hanging.

Be the first to answer this question

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