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

Optimize gradually Update Endpoint Upgrade

stvoglio

Hello everybody!

One of our customors has over 3000 clients on Windows 7 placed all over the country. That means that some of the clients have a better Internet connection some of them have a really bad one.  

Our customor inists that we update the AV Subscription manually every time its released. The problem here is that we can do that procedure only on weekends when nobody is working anymore, but we can't wake up all of the computers via WOL. That means that some offices can't nearly work anymore on Monday because some clients are getting the new Subscription that we released on the weekend before. 

Now my question is: 

Is there a way to set up some sort of neighbor cast so clients who are not up to date get their subscription update from some machine in their subnet? Or is there any other solution that you reccommend? 

Edit: We are working with Enterprise Console 5.1

Thank you in advance!

:55846


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

    Hello stvoglio,

    guess the NAS servers have different names at different site so each site would have to have its own policy. If you update all sites on the same weekend it's better not to change the subscription in the policy but to change the subscribed product in the subscription. Say you have two subscriptions, Production and Test. Both are set to SESC 10.3.12. You have two corresponding CIDs on the server. Your updating policies are SiteA, SiteB and so on (pointing to the local NAS but all using the Production subscription), and Test. When 10.4.1 or whatever comes out you change the Test subscription to this product version.The server deploys the new version to the Test CID and the test endpoints update. Once you are finished you just change the product version in the Production subscription. The server will update this CID, the NAS servers will mirror it and the production clients will update with the new version.

    A SUM is just a tool to download updates directly or indirectly from Sophos, verify the validity and integrity, and deploy them to the CID in a structure exepcted by AutoUpdate. AutoUpdate on the endpoints just reads a folder's contents from the update location - whether it's a network share, some removable medium, or a local folder doesn't matter at all. 

    Christian 

    :55868
Reply
  • 0

    Hello stvoglio,

    guess the NAS servers have different names at different site so each site would have to have its own policy. If you update all sites on the same weekend it's better not to change the subscription in the policy but to change the subscribed product in the subscription. Say you have two subscriptions, Production and Test. Both are set to SESC 10.3.12. You have two corresponding CIDs on the server. Your updating policies are SiteA, SiteB and so on (pointing to the local NAS but all using the Production subscription), and Test. When 10.4.1 or whatever comes out you change the Test subscription to this product version.The server deploys the new version to the Test CID and the test endpoints update. Once you are finished you just change the product version in the Production subscription. The server will update this CID, the NAS servers will mirror it and the production clients will update with the new version.

    A SUM is just a tool to download updates directly or indirectly from Sophos, verify the validity and integrity, and deploy them to the CID in a structure exepcted by AutoUpdate. AutoUpdate on the endpoints just reads a folder's contents from the update location - whether it's a network share, some removable medium, or a local folder doesn't matter at all. 

    Christian 

    :55868
Children
No Data