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

    I don't think you can ever be too cautious and your approach seems to be a good one. I'm always amazed when someone says I rolled out software to thousands of production machines and now nothing works.  Did you try one first? :)

    It certianly does no harm to "pilot" a new major verison in each part of the business; typically there is no major rush to be on the latest unless policy demands a new feature or you've left it so late that it's about to be retired.  To "truly" test all possible software users may have and how they really use it in a test environment can be unrealistic so to, for the want of a better word, pick on a few clients accross the business makes great sense.  Ideally these user would be the more techical who would recognise problems such as performance changes, etc.  Maybe even give them a short course to better educate them on the software,  these can then always be the guinea pigs for future rollouts , just don't call them guinea pigs, they may not like it.

    Regards,

    Jak

    :24663
Reply
  • 0

    HI RogueViper,

    I don't think you can ever be too cautious and your approach seems to be a good one. I'm always amazed when someone says I rolled out software to thousands of production machines and now nothing works.  Did you try one first? :)

    It certianly does no harm to "pilot" a new major verison in each part of the business; typically there is no major rush to be on the latest unless policy demands a new feature or you've left it so late that it's about to be retired.  To "truly" test all possible software users may have and how they really use it in a test environment can be unrealistic so to, for the want of a better word, pick on a few clients accross the business makes great sense.  Ideally these user would be the more techical who would recognise problems such as performance changes, etc.  Maybe even give them a short course to better educate them on the software,  these can then always be the guinea pigs for future rollouts , just don't call them guinea pigs, they may not like it.

    Regards,

    Jak

    :24663
Children
No Data