What causes the Error (agent disconnected) errors while patching?

I recently upgraded my K1000 server to version 10.0.290 to resolve an issue related to the KACE agents not connecting to the server on new installs ofWindows 10 feature update 1903 . Since then, I've had problems with KACE not attempting to patch unless the agent on the end clients is version 10.0.113. After working to upgrade my network so that everyone will be using 10.0.113, I am still frequently seeing devices fail to patch and give the error status "Error (agent disconnected". Does anyone know what this error means and what can be done to keep it from happening when I am trying to patch my network?

3 Comments   [ + ] Show comments
  • We have been having this exact same issue since the update to 10.0.290. My own computer is completely unable to receive any patches or scripts or managed installs even though it is clearly checking in to the SMA. Any time I try to run a patch schedule on my computer (I'm using mine as a guinea pig, but this is happening on hundreds of other devices as well) it inevitably fails with the "Error (agent disconnected)" status. So far I have not found anything useful in the logs, but I will update here if that changes. - sjbosler 3 years ago
  • I also have experienced this for the first time this morning. First time running patches with the new server and client. Server version 10.0.290 and agent version 10.0.113. In the kagent.log I can see that the agent downloaded and installed the patches and the user was prompted for a restart and snoozed. Then I can see that the user finally chose to restart, the computer restarted, and the agent sent a status 0 back to the server. I don't see any communication errors. The next thing that happened on the agent was the scheduled detection that ran this morning.

    Question for anyone who has experienced this: Does the status stay stuck like this forever or does it ultimately change to completed? - k1knnja 3 years ago
  • I have the same thing happening. My clients error out quickly. Some have to VPN back in after a reboot and it won't continue to patch. It just ends in Error. I also have IT folks that are docked when patching starts then undock to go to a meeting with their laptop and it errors immediately. Is there a timeout value that can be set to give folks a little time before ending in error? This is taking so much extra time to manually try to catch these folks to deploy patches again... and watch and possibly re-deploy after a reboot again.. - jrkeister26 2 years ago

Answers (1)

Posted by: Nico_K 3 years ago
Red Belt

these are the typical issues when an agent does not reach the appliance.
This can be: 
- shut down the client
- change the network (from cabled to WLAN or WWAN)
- overused connections (switches etc)

Go into one system which has this issue and review the agent logs and the system logs what happened.

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