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

Deploying SAV 10 best practices

RogueViper

Wonder if anyone can share some insight in how they upgraded their clients to the latest version of Sophos. 

Currently I have upgraded the console to version 5, created a new subscription and share to SAV 10 recommended. Currently endpoints are running 9.5.6. 

I then placed my two desktops and my own server into a special test group. Spent a good 2 weeks using it and going about my daily business. Last week I started adding more XP desktops into the test group and so far today I'm up to 32 from a mixture of departments (total workstations and laptops ~250+)

I'm just trying to be really cautious before going along and upgrading all other desktops and then laptops. I'm going to leave servers until last and then move onto the other office site. 

Do you think I'm being too cautious? I'm just worried that il end up breaking something and causing widespread disruption . 

Mike

:24623


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

    HI,

    The reboot is required but the software will continue to function until you do so, it doesn't have to be done straight away.  The machine will flag the outstanding reboot state in SC until done so.

    There are multiple approaches to upgrade. 

    1. If you just have a single subscription, e.g. "Recommended" and therefore a single distribution point, e.g.:

    \\server\sophosupdate\CIDs\s0000\

    Then all the updating polices would use this "Recommended" subscription.

    So if you change the "Recommended" subscription to SAV 10, SUM will update the above CID \\server\sophosupdate\CIDs\s0000\ with SAV 10 and on next update the clients will upgrade.

    2. Create a second subscription, call it SAV 10 for example.

    This will create you a new distribution location, e.g.

    \\server\sophosupdate\CIDs\s0001\

    You can then just change the updating policy for a few client to use this new subscription.  In the updting policy there is a subscription tab.

    When the clients get their updating policy, on next update,  those clients will update from this new CID and upgrade to 10.

    So 1 is the shotgun approach, 2 is the more measured approach where you can deploy to a few groups at a time.

    Regards,

    Jak

    :25645
Reply
  • 0

    HI,

    The reboot is required but the software will continue to function until you do so, it doesn't have to be done straight away.  The machine will flag the outstanding reboot state in SC until done so.

    There are multiple approaches to upgrade. 

    1. If you just have a single subscription, e.g. "Recommended" and therefore a single distribution point, e.g.:

    \\server\sophosupdate\CIDs\s0000\

    Then all the updating polices would use this "Recommended" subscription.

    So if you change the "Recommended" subscription to SAV 10, SUM will update the above CID \\server\sophosupdate\CIDs\s0000\ with SAV 10 and on next update the clients will upgrade.

    2. Create a second subscription, call it SAV 10 for example.

    This will create you a new distribution location, e.g.

    \\server\sophosupdate\CIDs\s0001\

    You can then just change the updating policy for a few client to use this new subscription.  In the updting policy there is a subscription tab.

    When the clients get their updating policy, on next update,  those clients will update from this new CID and upgrade to 10.

    So 1 is the shotgun approach, 2 is the more measured approach where you can deploy to a few groups at a time.

    Regards,

    Jak

    :25645
Children
No Data