Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 62 replies
  • Subscribers 0 subscribers
  • Views 195159 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

SEC 5.2.1 and Sophos for MAC OS X Preview (9.0.3)

QC

Decided to give the Preview of Anti-Virus for Mac OS X, version 9.0.3 a try. Chose an old MacBook (running 10.4) as guinea pig. After assigning the alternate policy updating failed with a rather vacuous Error: Could not update Sophos-Anti-Virus at .... Update failed. No indication of the nature or the error and surprisingly no indication of the update location used. 

Now, the error was not unexpected - 9.0.x requires MAC OS X 10.6 minimum but perhaps a more meaningful message could be issued. Anyway I checked the update location and found that it named ESCOSXL as source folder - obviously indicating the changed requirements (though I can't figure out what the L stands for :smileyhappy:).

Admittedly pre-10.6 versions should be rare by now (I've found two 10.5 installations still in use out of about 100). But the folder name change will affect unmanaged or occasionally off-site clients (yes, Cloud is the answer :smileywink:). I've found no reference though (I'd have expected this in the Release Notes). Even as it is Preview you should be required to discover this important information on your own.

Christian   

:43783


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

    So now it's "you hope you can address them"?  In an earlier post Bob had said this stuff was going to be done.  There was just no time frame.  I, along with the rest of my colleagues, have been waiting for this for about at least a year.  I would like to know what I am supposed to tell our clients.  As of now we don't have a truely viable option to supply to them.  Needless to say, those above me are concerned that our contract will not be renewed when the time comes.  Not only because of this situation but another open case that I have that has gone unresolved for 5 months and counting.

    You are probably taking Darren's comments a little too literally. To be fair to him, he hasn't always been the Mac endpoint product manager so he is getting up to speed.

    We still intend to evolve our approach and tools for deployment to meet your needs as well as others. Not committing to a timeline isn't the same as not doing it.

    :48602

    ---

    Bob Cook (bob.cook@sophos.com) Director, Software Development

Reply
  • 0
    Carob wrote:

    So now it's "you hope you can address them"?  In an earlier post Bob had said this stuff was going to be done.  There was just no time frame.  I, along with the rest of my colleagues, have been waiting for this for about at least a year.  I would like to know what I am supposed to tell our clients.  As of now we don't have a truely viable option to supply to them.  Needless to say, those above me are concerned that our contract will not be renewed when the time comes.  Not only because of this situation but another open case that I have that has gone unresolved for 5 months and counting.

    You are probably taking Darren's comments a little too literally. To be fair to him, he hasn't always been the Mac endpoint product manager so he is getting up to speed.

    We still intend to evolve our approach and tools for deployment to meet your needs as well as others. Not committing to a timeline isn't the same as not doing it.

    :48602

    ---

    Bob Cook (bob.cook@sophos.com) Director, Software Development

Children
No Data
Unfiltered HTML