Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 1 reply
  • Subscribers 1 subscriber
  • Views 3391 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Randomnization

acidburn

In Sophos endpoint protection, is there a feature that randomnize when clients check in? We experienced some network issue where it appeared that all clients were checking in at the same time. Is there a feature that would allow randomnization so that clients do not all check in at the same time?

:53885


This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    It should be random as the update interval is based off when the Sophos AutoUpdate service starts.  As this service will initally start with the computer and then the checks to the distribution point will be every x minutes thereafter (as specified in policy).

    That being said, I can see the scenario where the clients are checking the CID every 10 minutes, with nothing to do.  SUM then updates the CID.  Within 10 minutes, all client are essentially going to be pulling from the CID.  For a single IDE update it would probably go unoticed.  If howerver there was a 50MB update for all clients, there is a good chance that for that 10 minute window a good proportion will be downloading at the same time just due to the time it takes for a client to fetch the files.

    Increasing the update interval might help, as might creating multiple distribution points with multiple SUMs, with a view to get the distribution points "Closer" to the clients, to minimise "time to download", and/or have the different SUMs update at different schedules.

    Regards,

    Jak

    :53887
Reply
  • 0

    Hi,

    It should be random as the update interval is based off when the Sophos AutoUpdate service starts.  As this service will initally start with the computer and then the checks to the distribution point will be every x minutes thereafter (as specified in policy).

    That being said, I can see the scenario where the clients are checking the CID every 10 minutes, with nothing to do.  SUM then updates the CID.  Within 10 minutes, all client are essentially going to be pulling from the CID.  For a single IDE update it would probably go unoticed.  If howerver there was a 50MB update for all clients, there is a good chance that for that 10 minute window a good proportion will be downloading at the same time just due to the time it takes for a client to fetch the files.

    Increasing the update interval might help, as might creating multiple distribution points with multiple SUMs, with a view to get the distribution points "Closer" to the clients, to minimise "time to download", and/or have the different SUMs update at different schedules.

    Regards,

    Jak

    :53887
Children
No Data