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

  • CheltCollege wrote:
    • Update server addresses (which is addressed in the latest version, sans proxy settings)

    Very curious to hear why you'd manage proxy settings for endpoints that are outside your own network. Sounds like users take these systems offsite, which I'd expect makes your own proxy servers unreachable. We didn't include the ability to set the proxy settings because we figured it was not useful.


    CheltCollege wrote:

    • Manage on access scanning (in archives/compressed files, but not network volumes)
    • Manage cleanup of infected files (delete infected files)
    • Display a custom desktop alert warning when a threat has been detected (explanation below)
    • E-mail a specified address when threats are detected for logging/tracking purposes.

    Thanks for this list. Its pretty extensive but not unrealistic. Please understand that we aren't going to create a separate tool to manage all possible settings. So although we may offer ways to pre-configure many or even all of these settings, we aren't going to guarantee your users can't change them. That is what Enterprise Console and Sophos Cloud are for.

    :48604

    ---

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

Reply

  • CheltCollege wrote:
    • Update server addresses (which is addressed in the latest version, sans proxy settings)

    Very curious to hear why you'd manage proxy settings for endpoints that are outside your own network. Sounds like users take these systems offsite, which I'd expect makes your own proxy servers unreachable. We didn't include the ability to set the proxy settings because we figured it was not useful.


    CheltCollege wrote:

    • Manage on access scanning (in archives/compressed files, but not network volumes)
    • Manage cleanup of infected files (delete infected files)
    • Display a custom desktop alert warning when a threat has been detected (explanation below)
    • E-mail a specified address when threats are detected for logging/tracking purposes.

    Thanks for this list. Its pretty extensive but not unrealistic. Please understand that we aren't going to create a separate tool to manage all possible settings. So although we may offer ways to pre-configure many or even all of these settings, we aren't going to guarantee your users can't change them. That is what Enterprise Console and Sophos Cloud are for.

    :48604

    ---

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

Children
No Data