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)

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
  • Hello Bob,

    right now SEC (5.2.1) gives me a somewhat confusing alert:

    Software subscription 'Alternate Recommended (S001)' contains version Retiring - The Preview release of SAV for Mac is ending. For OS X 10.9 (Mavericks) support please subscribe to 9 Recommended of platform MAC OS X 10.4+. This version is nearing retirement. Your subscription will be automatically upgraded.

    Ok, I understand that the Preview is about to be retired. But there's no 9 Recommended to subscribe to (yet). Furthermore the minimum platform for 9.0.x is MAC OS X 10.6. Naturally you can't put all the intricacies on a single line. I think a reference to a knowledgebase article would be necessary.

    Just occurred to me that the name change might have the effect that Macs might be cut off from updates without anyone noticing for some time. Admittedly this would happen only under certain circumstances:

    • the subscription is automatically upgraded to version 9
    • the version 8 folder (ESCOSX) is not removed (as far as I know SEC doesn't do this)
    • the Macs are "temporarily unmanaged" (e.g. because they are off-site) and therefore not informed of the name change

    The Macs will continue to successfully check the update location known to them (ESCOSX) but won't find any threat detection data updates. Of course, an endpoint (and its user) can't detect a "stale CID" for some time. 

    Christian

    :44545
Reply
  • Hello Bob,

    right now SEC (5.2.1) gives me a somewhat confusing alert:

    Software subscription 'Alternate Recommended (S001)' contains version Retiring - The Preview release of SAV for Mac is ending. For OS X 10.9 (Mavericks) support please subscribe to 9 Recommended of platform MAC OS X 10.4+. This version is nearing retirement. Your subscription will be automatically upgraded.

    Ok, I understand that the Preview is about to be retired. But there's no 9 Recommended to subscribe to (yet). Furthermore the minimum platform for 9.0.x is MAC OS X 10.6. Naturally you can't put all the intricacies on a single line. I think a reference to a knowledgebase article would be necessary.

    Just occurred to me that the name change might have the effect that Macs might be cut off from updates without anyone noticing for some time. Admittedly this would happen only under certain circumstances:

    • the subscription is automatically upgraded to version 9
    • the version 8 folder (ESCOSX) is not removed (as far as I know SEC doesn't do this)
    • the Macs are "temporarily unmanaged" (e.g. because they are off-site) and therefore not informed of the name change

    The Macs will continue to successfully check the update location known to them (ESCOSX) but won't find any threat detection data updates. Of course, an endpoint (and its user) can't detect a "stale CID" for some time. 

    Christian

    :44545
Children
No Data