/build/static/layout/Breadcrumb_cap_w.png
02/22/2019 116 views

We've been having inconsistent issues where scripts being ran will abort mid way and not proceed to the next step if a machine's AMP connection is interrupted in any way. The step currently being ran will usually finish but anything after it will not be ran. I've also seen this behavior to cause downloads for MI's/Software Packages to abort mid way.  The script log for this task will show as "running" Indefinitely if this occurs.


I've tried looking through the Konea and Agent logs but they do not seem to contain anything useful in relation to the processing of scripts and download of software packages. I don't see any specific commentary in the log about the AMP agent losing it's connection but I do see the commentary when the AMP agent reconnects later on.


This issue will occur 100% of the time if a script involves any sort of network adapter state changes such as Installing VPN client software that has a Virtual Adapter or updating a NIC driver.  It also occurs at random, likely due to network traffic communication issues? Is there a step that can be used to mitigate this in scripts that involve changing a network adapter state, aside from not having KACE wait for it to finish? Additionally, is there any advanced, debugging options that can be enabled for the agents when we are encountering unusual agent related behavior?

0 Comments   [ + ] Show comments

Comments


There are no answers at this time