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

  • bobcook wrote:

    Preference files are always stored in /Library/Preferences and are always prefixed with com.sophos.

    Do you have a support case open for the on-access scanning issue? Definitely want to ensure it is getting addressed.

    Re: the pre-configuration, sounds like your requirements would be covered if we supported pre-configuration of the on-access settings (on/off, the handling of archives and network volumes, and the threat handling).


    I think I may have found the files that were the holdovers from the "managed" install but they weren't the com.sophos files.

    One of the open cases I have does include the on-access scanning issue.  That is supposedly being looked at.

    If the other options were supported in pre-configuration, yes, that would probably solve the issues.  But, from what I understand, they arent.

    :45229
Reply

  • bobcook wrote:

    Preference files are always stored in /Library/Preferences and are always prefixed with com.sophos.

    Do you have a support case open for the on-access scanning issue? Definitely want to ensure it is getting addressed.

    Re: the pre-configuration, sounds like your requirements would be covered if we supported pre-configuration of the on-access settings (on/off, the handling of archives and network volumes, and the threat handling).


    I think I may have found the files that were the holdovers from the "managed" install but they weren't the com.sophos files.

    One of the open cases I have does include the on-access scanning issue.  That is supposedly being looked at.

    If the other options were supported in pre-configuration, yes, that would probably solve the issues.  But, from what I understand, they arent.

    :45229
Children
No Data