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

    I can confirm that this works with 9.2.2 Preview with the stand alone installation, but how do we implement this with our centrally managed clients?

    I need to be able to pre-assign a group AND pre-assign a temporary update policy to each Mac (and Windows box) I install Sophos on.   

     After the installation is completed and update to our server is successful, the machine does not show up in the enterprise console.  I am assuming that this is intended because the installer is stand alone, but it highlights the need for this functionality in the managed installer because without it, the clients won't get a scan policy which we need. 

    :54389
Reply
  • 0

    I can confirm that this works with 9.2.2 Preview with the stand alone installation, but how do we implement this with our centrally managed clients?

    I need to be able to pre-assign a group AND pre-assign a temporary update policy to each Mac (and Windows box) I install Sophos on.   

     After the installation is completed and update to our server is successful, the machine does not show up in the enterprise console.  I am assuming that this is intended because the installer is stand alone, but it highlights the need for this functionality in the managed installer because without it, the clients won't get a scan policy which we need. 

    :54389
Children
No Data