Kaseya Community

Patch Scan Bandwidth Issues

  • Hey all!

    First off, DISCLAIMER: Not a version 5.0 issue! We've watched as the rest of you guys have reported the issues from afar, but recent growth at our company has really pushed our bandwidth through the roof!

    We noticed on the event logs that each machine while doing its patch scans will push a 4MB file to the KServer that parses which patches are installed on each machine. During the night we REALLY notice a slowdown when trying to connect from home to managed machines through Kaseya due to the amount of bandwidth.

    Here's where the questions come into play (btw, we're on a 8 down, 2 up connection experiencing this issue)

    1) We do patch scans and patching every night, is that best practice? Or is it best to do it once/twice per week?

    2) Is there a good way to try and minimize the bandwidth from this particular aspect? (an onsite server that does the reporting....and I can hear the WSUS server guys chiming in already). The desired effect is to try and keep this managed through Kaseya but to minimize bandwidth as much as possible.

    3) Do you guys notice the same thing happening on your systems?

    4) If you've gotten around this issue, how have you done it?

    As always, any advice is greatly appreciated!

    Big SmileSmile

    Legacy Forum Name: Patch Scan Bandwidth Issues,
    Legacy Posted By Username: papaschnay
  • Go to the Scripts tab, make sure you have selected, and then click on Distribution in the left hand frame.

    The top histogram will be for your Automatic Patch Updates.

    You'll find that you probably have to get a more even distribution which you can do by setting the time window and clicking Distribute.

    I did the same thing to myself in the early days and spreading things out a bit really makes a differance.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: misolutions.com
  • How big of a window do you usually give Patch Scans on your setup? I believe we have currently a 4 hour window for approximately 1500 machines....do we need to allocate more time for this?

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: papaschnay
  • We do our patch scans for workstations from 9-5pm and servers 24 hours. We regularly use the script distribution to spread out the times for patch scans.

    You can use the bandwidth limit on the agent tab to minimize impact from patch data uploads / downloads. We limit our machines to 32kB so we don't overload our bandwidth here.

    You are going to need a good amount of bandwidth if you keep growing. I remember when we were at 1500 machines we had 2 T1's bonded. Once we got to 3000 machines we were really pegging our bandwidth so we upgraded to a 15Mb fiber connection through Yipes. Now at 6500 machines we regularly use 4-7Mb during peak times just for Kaseya traffic.

    Hope that helps,
    bobp

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: bob.penland@kaseya.com
  • I never noticed the bandwidth throttle setting, we have that disabled for everyone across the board! EekRed Faced

    So far it sounds like the following 2 steps should be implemented:

    1) Expand the time window that we're giving our patch scans across all networks
    2) Possibly enable the bandwidth throttle setting for 32kbps for each machine to try and not kill the bandwidth

    Do you guys still do patch scans every day? Or do you do something like a "black friday" approach where patches are applied on one day every week?

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: papaschnay
  • We do them every day still. This gives us to most flexibility to release updates.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: bob.penland@kaseya.com
  • Does bandwidth throttling have any sort of adverse affect on any other scripts/remote control/etc??

    Does anyone that use this setting have any feedback? Or is this something that's ONLY used for Patch Mgmt?

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: papaschnay
  • We have a bit over 2000 clients and for desktops we do patching from 12am to 4am, patch scans from 6am to 11:30pm and maintenance runs from 12:30am to 4:30am everyday. We do all that on servers once a week over the weekends. All our files for maintenance are kept up to date with file distribution so they don't take any bandwidth after the initial download. Also most files we use within scripts over 1-2mb are pulled from our ftp server which is on a seperate internet line. Though our server does get a little overwhelmed at night as pending alerts start to pile up and slowly clear out when patching is complete, we luckly don't experience any bandwidth issues yet. We are currently on a single T1 line.

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: cbnny
  • papaschnay
    Does bandwidth throttling have any sort of adverse affect on any other scripts/remote control/etc??

    Does anyone that use this setting have any feedback? Or is this something that's ONLY used for Patch Mgmt?


    Any more feedback on this question?

    Legacy Forum Name: General Discussion,
    Legacy Posted By Username: papaschnay