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:

    Carob wrote:

    You're talking about a client version 9.2, right?  If so I guess I'm confused.  Is a new tool built into the client then instead of being something stand-alone?

    Also, if I remember correctly, the command line tool still only allowed certain things to be configured and not all being requested (by myself and others it seemed), is that right?

    When there is a KBA on the subject would you post the number/link here?


    Yes version 9.2 of the Mac agent (client). All the different version numbers across different products can get confusing, sorry.

    The pre-configuration will require that you get a copy of the stand-alone installer and run a command-line tool from Terminal. That command-line tool is embedded within the stand-alone installer application. Its the same model / "style" as we provide for pre-configuring the Update settings as described in KBA 119744.

    The settings that can be pre-configured for On-Access Scanning include the ability to specify whether scanning will be on or off. If on, other settings are available too:

    • archive scanning
    • network volume scanning
    • file or directory path to exclude (can add multiple items)
    • automatic cleanup
    • action if automatic disinfect fails (nothing, move, delete)
    • destination directory for moved threats

    That pretty much covers the settings available in the On-Access Scanning preferences panel.

    I'll be sure to post something to this thread when the software and KBA are available, and of course it will be in the release notes.


    I guess I'm still confused.  If it will be required to get a copy of the stand-alone installer then how does needing to have version 9.2 of the client come into play?

    How about setting Primary and Secondary Update Locations (including the ability to leave the Secondary location blank) and update interval times?

    I guess I'll just wait to see your post when everything is ready and read through it at that time.

    :51282
Reply

  • bobcook wrote:

    Carob wrote:

    You're talking about a client version 9.2, right?  If so I guess I'm confused.  Is a new tool built into the client then instead of being something stand-alone?

    Also, if I remember correctly, the command line tool still only allowed certain things to be configured and not all being requested (by myself and others it seemed), is that right?

    When there is a KBA on the subject would you post the number/link here?


    Yes version 9.2 of the Mac agent (client). All the different version numbers across different products can get confusing, sorry.

    The pre-configuration will require that you get a copy of the stand-alone installer and run a command-line tool from Terminal. That command-line tool is embedded within the stand-alone installer application. Its the same model / "style" as we provide for pre-configuring the Update settings as described in KBA 119744.

    The settings that can be pre-configured for On-Access Scanning include the ability to specify whether scanning will be on or off. If on, other settings are available too:

    • archive scanning
    • network volume scanning
    • file or directory path to exclude (can add multiple items)
    • automatic cleanup
    • action if automatic disinfect fails (nothing, move, delete)
    • destination directory for moved threats

    That pretty much covers the settings available in the On-Access Scanning preferences panel.

    I'll be sure to post something to this thread when the software and KBA are available, and of course it will be in the release notes.


    I guess I'm still confused.  If it will be required to get a copy of the stand-alone installer then how does needing to have version 9.2 of the client come into play?

    How about setting Primary and Secondary Update Locations (including the ability to leave the Secondary location blank) and update interval times?

    I guess I'll just wait to see your post when everything is ready and read through it at that time.

    :51282
Children
No Data