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
  • Hi guys,

    You might have noticed I deleted my previous post re: this issue, I deleted it so it wouldn't become confusing. We have decided it is less painful to stay the course e.g. the CID name will remain as "ESCOSXL" for version 9.

    The implications of this:

    (1) if you are using file-based CIDs with SEC, moving from v8 to v9 will work fine, your SEC console will send the right pat the endpoint during the policy change to use the v9 subscription


    (2) if you are updating from Sophos directly then you are also ok (our servers know what to give to your v8 or v9 endpoint)

    (3) if you have configured updating via your own servers (HTTP or otherwise), you may need to implement changes for v9 packages, depending on your customized configuration

    Post questions here if you got them, I'll answer them the best I can.

    :44309

    ---

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

Reply
  • Hi guys,

    You might have noticed I deleted my previous post re: this issue, I deleted it so it wouldn't become confusing. We have decided it is less painful to stay the course e.g. the CID name will remain as "ESCOSXL" for version 9.

    The implications of this:

    (1) if you are using file-based CIDs with SEC, moving from v8 to v9 will work fine, your SEC console will send the right pat the endpoint during the policy change to use the v9 subscription


    (2) if you are updating from Sophos directly then you are also ok (our servers know what to give to your v8 or v9 endpoint)

    (3) if you have configured updating via your own servers (HTTP or otherwise), you may need to implement changes for v9 packages, depending on your customized configuration

    Post questions here if you got them, I'll answer them the best I can.

    :44309

    ---

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

Children
No Data