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
  • With the demise of SUM (bad, bad decision), I am following the instructions in http://www.sophos.com/en-us/support/knowledgebase/119744.aspxto create a standalone installer with built-in updating credentials, I am confident that will work as far as it goes.

    As others have commented here, it does not (yet) allow setting other settings such as don't/do scan network volumes, zips, etc. It would seem the easiest solution to achieve this would be if Sophos allowed using the defaults write command to customise various plist stored settings on the client. This in fact may well already be possible but Sophos should provide some documentation and examples for this if so. There are plenty of Mac management tools to allow managing plist stored settings on clients some of which are free (or almost so), so this approach would be a good compromise.

    However what Sophos should have done a long time ago, is make their Sophos Enterprise Console platform independent. There is absolutely no need for it to be tied solely to (ugh!) Windows Servers. After all you provide clients for all the major operating systems. If it had been written as a web-app with an open-source database backend e.g. MySQL then it would be easy to run on Linux, Unix, or of course Mac OS X. It probably would have even been easier and cheaper to maintain on Windows both for Sophos themselves and their clients.

    I would still prefer at a minimum an updated Sophos Update Manager for Mac (if Sophos will not make Sophos Enterprise Console platform independent). Sophos Cloud does not do what I want even if it eventually turns out to be free which is not yet clear, it looks like an extra cost which is therefore penalising your non-Windows customers. If there is no replacement for SUM then I shall at least be looking for a replacement for Sophos which has a Mac tool like SUM, whether I will find one and eventually drop Sophos is at this point unknown.

    Note: You are making life much harder for non-Windows server customers. Even though it is possible to pre-configure your SAV9 installer (as per the above article), this installer is an 'Application' it is not an installer package, therefore deploying it is not a straight forward process of using a Mac management tool to deploy and run the installer since these tools either expect a package (to run), or an Application which simply gets copied to the Applications folder. We have enough of this hassle with Adobe and even they have seen the error of their ways and produced a tool for making package installers for Enterprise customers. The silly thing is that for a copy of SAV managed by SUM or Enterprise Console you do give a package file, it is the standalone installer (or the home edition which is not relevant) that is the exception. :smileymad:

    :47501
Reply
  • With the demise of SUM (bad, bad decision), I am following the instructions in http://www.sophos.com/en-us/support/knowledgebase/119744.aspxto create a standalone installer with built-in updating credentials, I am confident that will work as far as it goes.

    As others have commented here, it does not (yet) allow setting other settings such as don't/do scan network volumes, zips, etc. It would seem the easiest solution to achieve this would be if Sophos allowed using the defaults write command to customise various plist stored settings on the client. This in fact may well already be possible but Sophos should provide some documentation and examples for this if so. There are plenty of Mac management tools to allow managing plist stored settings on clients some of which are free (or almost so), so this approach would be a good compromise.

    However what Sophos should have done a long time ago, is make their Sophos Enterprise Console platform independent. There is absolutely no need for it to be tied solely to (ugh!) Windows Servers. After all you provide clients for all the major operating systems. If it had been written as a web-app with an open-source database backend e.g. MySQL then it would be easy to run on Linux, Unix, or of course Mac OS X. It probably would have even been easier and cheaper to maintain on Windows both for Sophos themselves and their clients.

    I would still prefer at a minimum an updated Sophos Update Manager for Mac (if Sophos will not make Sophos Enterprise Console platform independent). Sophos Cloud does not do what I want even if it eventually turns out to be free which is not yet clear, it looks like an extra cost which is therefore penalising your non-Windows customers. If there is no replacement for SUM then I shall at least be looking for a replacement for Sophos which has a Mac tool like SUM, whether I will find one and eventually drop Sophos is at this point unknown.

    Note: You are making life much harder for non-Windows server customers. Even though it is possible to pre-configure your SAV9 installer (as per the above article), this installer is an 'Application' it is not an installer package, therefore deploying it is not a straight forward process of using a Mac management tool to deploy and run the installer since these tools either expect a package (to run), or an Application which simply gets copied to the Applications folder. We have enough of this hassle with Adobe and even they have seen the error of their ways and produced a tool for making package installers for Enterprise customers. The silly thing is that for a copy of SAV managed by SUM or Enterprise Console you do give a package file, it is the standalone installer (or the home edition which is not relevant) that is the exception. :smileymad:

    :47501
Children
No Data