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

    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).

    :45137

    ---

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

  • 0
    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
  • 0

    Since I haven't heard anymore is it safe to say the additional options won't be available for configuring?

    :45627
  • 0

    We are going to it.

    We haven't built it yet, and we aren't ready to commit to delivery for a specific month.

    :45629

    ---

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

  • 0
    bobcook wrote:

    We are going to it.

    We haven't built it yet, and we aren't ready to commit to delivery for a specific month.

    Would it be too much to ask for you to post something in this thread when it's ready and how to go about the process?  I don't know how I would know things are ready without that.  Unless you can advise me otherwise.

    :45631
  • 0
    Carob wrote:

    Would it be too much to ask for you to post something in this thread when it's ready and how to go about the process?  I don't know how I would know things are ready without that.  Unless you can advise me otherwise.

    Sure that is reasonable. When we build & test it we'll schedule it for a release and also post a knowledge base article about how to use it. It will be similar to the current pre-configuration options for updating.

    :45633

    ---

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

  • 0
    bobcook wrote:
    Carob wrote:

    Would it be too much to ask for you to post something in this thread when it's ready and how to go about the process?  I don't know how I would know things are ready without that.  Unless you can advise me otherwise.

    Sure that is reasonable. When we build & test it we'll schedule it for a release and also post a knowledge base article about how to use it. It will be similar to the current pre-configuration options for updating.

    I'm guessing no update on this as of yet?

    :46771
  • 0
    Carob wrote:

    I'm guessing no update on this as of yet?

    Yes, there is no news to share about this yet.

    :46813

    ---

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

  • 0

    I would like to configure the autoupdate options as well (change update interval and update on connection) for the unmanaged client.  Why did Sophos dev team think that no one will want to change their settings?

    :46971
  • 0
    Nutz wrote:

    I would like to configure the autoupdate options as well (change update interval and update on connection) for the unmanaged client.

    To create a standalone installer that contains pre-configured updating preferences please follow this article:
    http://www.sophos.com/en-us/support/knowledgebase/119744.aspx

    :46975

    ---

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

Unfiltered HTML