Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 36 replies
  • Subscribers 1 subscriber
  • Views 105122 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

Mac OS - pre-configuring Autoupdate

QC

We have quite a number of Macs (not surprising at a university) but no official Mac support. Nevertheless we offer Sophos for Macs (in a downloadable .zip archive).  

When Sophos is installed on a Mac on our network it connects to the management server from where it gets the update policy (the CIDs contain the correct mrinit.conf for RMS to work). Of course this does not work if the Mac is used at home. For windows PCs putting sauconf.xml placed in the appropriate directory does the trick. There are some articles in the knowledgebase but usually a Mac is required with which you can configure the CID (if I understand correctly). I believe no magic is actually involved and the configuration is stored somewhere in a .plist file (XML format). I suspect that the catalogues are involved and configcid.exe does not support a CID for OSX.

Or is there a "simple" way to pre-configure autoupdate (even if it's unsupported)? sau.plist looks suspicous  :smileywink:

Christian

:518


This thread was automatically locked due to age.
Parents
  • 0

    Works a treat! Thanks Bob.

    Added "cd /path/to/installer/directory" into my script and it works fine! 

    I will do some additional testing with a removal prior to install, as it is somewhat hit or miss if I install over the existing software (as one "might" expect. :) )

    If using a competent deployment tool with scripted installation, we can ignore the notes about being prompted for credentials, as the script should be run as root by default. 

    The instructions on the KBA 14179 are clear and informative. 

    Thanks again!

    :54239
Reply
  • 0

    Works a treat! Thanks Bob.

    Added "cd /path/to/installer/directory" into my script and it works fine! 

    I will do some additional testing with a removal prior to install, as it is somewhat hit or miss if I install over the existing software (as one "might" expect. :) )

    If using a competent deployment tool with scripted installation, we can ignore the notes about being prompted for credentials, as the script should be run as root by default. 

    The instructions on the KBA 14179 are clear and informative. 

    Thanks again!

    :54239
Children
No Data