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

    Hello Bob,

    [Edit name="Where are my manners?"]

    thanks for the update (or rather: replacement), Bob. It's probably less confusing with only the "effective" reply, nevertheless it is not as clear to me (which might be my fault though) as I'd wish.

    [/Edit]

    (1) [...] will send the right path

    (2) [...] our servers know what to give to your v8 or v9 endpoint

    At the moment I don't see how (1) can send the right path, it might work with (2) and SDDM as mechanism. Right path meaning that 10.5 clients will still get v8. SEC would have to download and deploy two product versions for one subscription (i.e. both v8 and v9 for Recommended) unless the product is split and 10.5- and 10.6+ are treated as different platforms.

    (1) if you are using file-based CIDs with SEC [...]  console will send the right path

    (3) [...] via your own servers (HTTP or otherwise), you may need to implement changes for v9 packages

    Maybe I'm dense - I don't quite get it, perhaps it's the via your own servers I'm failing to understand. As long as you are using managed policies SEC will append the partial path CIDs\counter\productfolder - and as it has to be there in the source you'll likely not publish/copy at the productfolder level.

    Christian

    :44325
Reply
  • 0

    Hello Bob,

    [Edit name="Where are my manners?"]

    thanks for the update (or rather: replacement), Bob. It's probably less confusing with only the "effective" reply, nevertheless it is not as clear to me (which might be my fault though) as I'd wish.

    [/Edit]

    (1) [...] will send the right path

    (2) [...] our servers know what to give to your v8 or v9 endpoint

    At the moment I don't see how (1) can send the right path, it might work with (2) and SDDM as mechanism. Right path meaning that 10.5 clients will still get v8. SEC would have to download and deploy two product versions for one subscription (i.e. both v8 and v9 for Recommended) unless the product is split and 10.5- and 10.6+ are treated as different platforms.

    (1) if you are using file-based CIDs with SEC [...]  console will send the right path

    (3) [...] via your own servers (HTTP or otherwise), you may need to implement changes for v9 packages

    Maybe I'm dense - I don't quite get it, perhaps it's the via your own servers I'm failing to understand. As long as you are using managed policies SEC will append the partial path CIDs\counter\productfolder - and as it has to be there in the source you'll likely not publish/copy at the productfolder level.

    Christian

    :44325
Children
No Data
Unfiltered HTML