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

    Long list of questions! Hopefully the answers make sense.

    Version 8 will run on OS X 10.9 "Mavericks" but we aren't going to provide support e.g. if your users have a problem, our support team is going to ask to have them upgraded to v9. The technical issue will be that our kext is not codesigned with the new Apple kernel extension signing process, so its likely the user is getting complaints (pop-up warnings) from the system.

    The "Pre-configured updating" feature was intended to release with 9.0.3 but didn't make it, so we had to retract the KBA. This feature is intended to allow an administrator to pre-configure their updating credentials for users which are using the standalone installation package (the variant that is umanaged). Its designed to allow you to customize the installer directly, then you can distribute this installer using any mechanism you already use. You'll need the standalone installers in 9.0.5 to have this feature working as intended.

    Also available in 9.0.5 will be the ability to specify the initial SEC group path for the .mpkg installer from a SEC CID. This feature is intended to allow you to pre-configure the group path such that Mac endpoints should immediately be placed into the correct group as soon as they are installed. This only applies to the SEC-managed version.

    Hope that helps.

    :44583

    ---

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

Reply
  • 0

    Hi Christian,

    Long list of questions! Hopefully the answers make sense.

    Version 8 will run on OS X 10.9 "Mavericks" but we aren't going to provide support e.g. if your users have a problem, our support team is going to ask to have them upgraded to v9. The technical issue will be that our kext is not codesigned with the new Apple kernel extension signing process, so its likely the user is getting complaints (pop-up warnings) from the system.

    The "Pre-configured updating" feature was intended to release with 9.0.3 but didn't make it, so we had to retract the KBA. This feature is intended to allow an administrator to pre-configure their updating credentials for users which are using the standalone installation package (the variant that is umanaged). Its designed to allow you to customize the installer directly, then you can distribute this installer using any mechanism you already use. You'll need the standalone installers in 9.0.5 to have this feature working as intended.

    Also available in 9.0.5 will be the ability to specify the initial SEC group path for the .mpkg installer from a SEC CID. This feature is intended to allow you to pre-configure the group path such that Mac endpoints should immediately be placed into the correct group as soon as they are installed. This only applies to the SEC-managed version.

    Hope that helps.

    :44583

    ---

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

Children
No Data
Unfiltered HTML