Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 1 subscriber
  • Views 9075 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

Create a detailed Updating Policy schedule?

Kalrand

Is there a way to configure a detailed schedule for the Updating Policy, to schedule a group of endpoints to update once an hour on the hour then another group 15-30min apart?

I'm currently working for a company that has many different branches that connects to a central location. The SEC, version 5.2.0.644, is at the central location and manages the endpoints for all the 30 branches. Each branch consists of roughly 3-7 endpoints. What I would like to do is configure the Updating Policy per branch to only update once an hour at a certain time then allow another branch to update later as not to congest the network. The reason this has come about is an update was triggered by reasons yet unknown that caused most endpoints to update and bring the network to a crawl, many of them requiring a reboot and some of those are DFS servers but that is a different issue altogether.

Any help would be greatly appreciated, thank you.

- Kalrand

:50088


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

    Hello,

    It's not really possible,  you can only schedule the frequency of the update checks.

    These checks start based on when the Sophos AutoUpdate service starts, i.e the computer starts up, 5 minutes after the service starts the first update check is performed and then x minutes thereafter as defined in policy.

    If the ultimate aim to reduce bandwidth, some options would be:

    1. Push a CID to each site. All clients would then update from a local location, downsite being, you need a computer that is on to receive the updates and host them for the other clients.  Also this way not be that firewall friendly.

    2. Install a "child" Sophos Update Manager at each site, this can pull updates from the central location, this can be over HTTP or UNC.  This is probably more firewall friendly but again would require a client to be on.

    3. Install a caching proxy at the sites, so the first client that fetches the files causes the files to be cached so local clients pull from the proxy for most of the updates.

    Regards,

    Jak

    :50090
Reply
  • 0

    Hello,

    It's not really possible,  you can only schedule the frequency of the update checks.

    These checks start based on when the Sophos AutoUpdate service starts, i.e the computer starts up, 5 minutes after the service starts the first update check is performed and then x minutes thereafter as defined in policy.

    If the ultimate aim to reduce bandwidth, some options would be:

    1. Push a CID to each site. All clients would then update from a local location, downsite being, you need a computer that is on to receive the updates and host them for the other clients.  Also this way not be that firewall friendly.

    2. Install a "child" Sophos Update Manager at each site, this can pull updates from the central location, this can be over HTTP or UNC.  This is probably more firewall friendly but again would require a client to be on.

    3. Install a caching proxy at the sites, so the first client that fetches the files causes the files to be cached so local clients pull from the proxy for most of the updates.

    Regards,

    Jak

    :50090
Children
No Data