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:

    Hi Carob,

    You will need version 9.2 of the stand-alone client installer software. The command line tool to pre-configure the On-Access Scanning is only available inside the installer starting with that version. The installer for version 9.1 only includes the tool required to pre-configure the Update settings, as described in KBA.

    The feature to pre-configure the Update settings already allows you to configure the primary and secondary locations. It might already do what you want (you aren't required to It doesn't have the ability to specify the update frequency though. The default is an hour. I recall the default setting in SEC is more frequent, something five or ten minutes. Just curious to understand your requirement so if we make changes it will actually make things better for you.

    Hope that helps.


    Oh.  Now I understand.  I thought you meant that the SEC client was somehow used to create the installer.

    Yes, I believe the SEC default update time is either 2 or 5 minutes.  Something crazy frequent.  When I'm configuring at stand-alone setup for someone here I tend to set the update to about 4 hrs or so.  People don't like Sophos checking very often because the systems take a pretty good hit should updates be available.  Our Managed clients are about half that though.

    Whether the abilities of the 9.2 client to create the installer package will really work for our needs or not remains to be seen.  When the product is available, and I see that notice here, I will check it out and read the KBA you provide.  I guess then we will see.

    :51296
Reply

  • bobcook wrote:

    Hi Carob,

    You will need version 9.2 of the stand-alone client installer software. The command line tool to pre-configure the On-Access Scanning is only available inside the installer starting with that version. The installer for version 9.1 only includes the tool required to pre-configure the Update settings, as described in KBA.

    The feature to pre-configure the Update settings already allows you to configure the primary and secondary locations. It might already do what you want (you aren't required to It doesn't have the ability to specify the update frequency though. The default is an hour. I recall the default setting in SEC is more frequent, something five or ten minutes. Just curious to understand your requirement so if we make changes it will actually make things better for you.

    Hope that helps.


    Oh.  Now I understand.  I thought you meant that the SEC client was somehow used to create the installer.

    Yes, I believe the SEC default update time is either 2 or 5 minutes.  Something crazy frequent.  When I'm configuring at stand-alone setup for someone here I tend to set the update to about 4 hrs or so.  People don't like Sophos checking very often because the systems take a pretty good hit should updates be available.  Our Managed clients are about half that though.

    Whether the abilities of the 9.2 client to create the installer package will really work for our needs or not remains to be seen.  When the product is available, and I see that notice here, I will check it out and read the KBA you provide.  I guess then we will see.

    :51296
Children
No Data