error (agent disconnected)
Hello, while running jobs at a site with low bandwidth, if the connection briefly drops, the entire job fails with "error (agent disconnected)" on all the servers in the middle of patching. So at this point, what should I do? Re-run the job? I would think the job continues until the connection restores and KACE reports where it left off instead of just failing the jobs with error (agent disconnected).
Answers (3)
I received an update from KACE. Basically, if the agent loses connection, the job fails. So I have to sit here and keep re-running the job over and over again until all the patches get installed while hoping the connection doesn't disconnect. This is not very productive with remote sites.
The simplest solution would be to have patch schedules running frequently. For example, if you know that computers at a certain location often have this problem then put all those computers on a special patch schedule that runs every few hours.
A more complex solution could be something like a smart label that checks the patch status table to determine if a device encountered "error (agent disconnected)"
Are you using local replication shares? (to prevent devices on that location from having to travel via WAN\MAN\VPN to the main KACE SMA). - Channeler 3 years ago