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

Opinion on the updater snafu from a Senior Admin

I've been in this business over 30 years, and I have, believe me, gone through Hell with a lot of previous anti-virus products in the past. Sophos was, and still is in my opinion, the best and easiest to administer. So, it's amusing to read some of the posts on the Internet from rookie admins doing a good imitation of a Drama Queen. Knee-jerk reactions won't do you any good when something like this happens. I too, could not get through to Sophos yesterday afternoon. But, I understood that their phone lines were probably overtaxed, so I just waited for them to fix the problem, applied the fixes from other admins I found on the Net, and by the time I went home to a cold supper, things were more or less back to normal.

Now, having said all that, and holding Sophos in such high esteem for so long, I'm as disappointed as anyone over this. I expect, in fact I demand, more from Sophos. If they want to be held up as the gold standard in this business, they'd better review procedures and try to make sure this doesn't happen again. Furthermore, a supreme gesture of good faith would be some sort of discount on their loyal customer's next maintenance contract.

:31353


This thread was automatically locked due to age.
Parents
  • It's not big deal if you administer 500 computers at a central location. I have a footprint of over 20,000 computers, at over 50 locations, in over 600 square miles. 

    The point is, there's absolutely no way any testing was done for an update to IDENTIFY ITSELF as a virus. I don't care if it's happened before, it's not an excuse for laziness and complacency. The fact is, any number of us would be held accountable and to the fire by our colleagues if we let something like this slip through, as we should.

    :31375
Reply
  • It's not big deal if you administer 500 computers at a central location. I have a footprint of over 20,000 computers, at over 50 locations, in over 600 square miles. 

    The point is, there's absolutely no way any testing was done for an update to IDENTIFY ITSELF as a virus. I don't care if it's happened before, it's not an excuse for laziness and complacency. The fact is, any number of us would be held accountable and to the fire by our colleagues if we let something like this slip through, as we should.

    :31375
Children
No Data