Using the Detect function on KACE 5.4 for scanning Desktops and Laptops for Patches takes a lot of bandwith on the WAN connections, how to prevent this ?
Hello all,
I get complaints from users that the WAN connection slows down at certain times...looking at this, it turns out that this at the same time KACE is doing a "detect" run (for MS Security Patches) on PC's, on a remote location.
I get PC's that, within a 15 min period, push 15-32Mb across the WAN connection (which is only 4 mb) between itself and the KACE 1000.
Having mulitple Pc's (10 - 20 within a 15 min period) doing this, kills the WAN bandwith...
I don't understand why it takes 16-32Mb of data to scan a PC on installed patches ? Or at least..., I would assume this is what is done/happening ?
Should the agent not collect this locally and send the result towards the KACE during sync's instead...preventing this load on the WAN connections in the first place ?
Note: just talking about detecting....not patching itself which i do using a replication share on that remote site.
Any idears ? I am searching for this subject, but it almost always about patching, not the detection phase and how that works/best way to go about....
Answers (2)
I have 26 locations with T1's and I'm not seeing this slowdown. Do you have replication points at each location?
Yes, that is, I disabled all of them, but one for now, as users complained to much about this.
I am around the 30 location here...not all have a replication point as yet, but for a 'detection run only' I would not expect is uses replication points (only at patching time it would) ?
I turned it off all togheter, and turned on just one location for now....and at the moment the detect runs start (10:15AM) is see this traffic starting....and people start complaining....after about 1.5 hour the run ends...end all is back to normal on the WAN connection...