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

    Hi Christian,

    Thanks for the reply, much appreciate the open communication.

    I would have expected "managed endpoints" to receive their updating policy automatically, especially with the "group path" installer feature. The concept is: configure the .mpkg installer w/ the group path config file, deploy the .mpkg with whatever software management tools or processses you already use, and (like magic) those Mac installs will end up getting the correct updating policy based on their group in the SEC console.

    We provided the feature to pre-configure updating credentials only to standalone installers, as those endpoints would not recieve an updating policy (no SEC or Cloud console).

    Can you explain how your deployments are set up? Maybe I'm missing something important.

    :44623

    ---

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

Reply
  • 0

    Hi Christian,

    Thanks for the reply, much appreciate the open communication.

    I would have expected "managed endpoints" to receive their updating policy automatically, especially with the "group path" installer feature. The concept is: configure the .mpkg installer w/ the group path config file, deploy the .mpkg with whatever software management tools or processses you already use, and (like magic) those Mac installs will end up getting the correct updating policy based on their group in the SEC console.

    We provided the feature to pre-configure updating credentials only to standalone installers, as those endpoints would not recieve an updating policy (no SEC or Cloud console).

    Can you explain how your deployments are set up? Maybe I'm missing something important.

    :44623

    ---

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

Children
No Data
Unfiltered HTML