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

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

    If you run the tools without any arguments you get an informational listing with supported options. Here is what I got:

    CreateOnAccessPreconfig [-option {value} ...]

        the following options can be specified:

            '-AutoLaunch'         on-access scanning (YES = on, NO = off)

            '-InArchives'         archive scanning (YES = on, NO = off)

            '-NetworkVolumes'     network volume scanning (YES = on, NO = off)

            '-ExcludedItem'       file or directory path to exclude

            '-EnableDisinfect'    automatic cleanup (YES = on, NO = off)

            '-NonDisinfectAction  action if automatic disinfect fails (N = none, D = delete, M = move)

            '-NonDisinfectFolder  destination directory for moved threats

    CreateUpdatePreconfig [-option {value} ...]

        the following options can be specified:

            '-PrimaryServerUserName'        primary server user name

            '-PrimaryServerPassword'        primary server password

            '-PrimaryServerType'            primary server type : 0=Sophos, 1=Company Webserver, 2=Network Volume

            '-PrimaryServerURL'             primary server location

            '-SecondaryServerUserName'      secondary server user name

            '-SecondaryServerPassword'      secondary server password

            '-SecondaryServerType'          secondary server type : 0=Sophos, 1=Company Webserver, 2=Network Volume

            '-SecondaryServerURL'           secondary server location

            '-PrimaryServerProxy'           primary proxy type 0=system, 1=user defined, 2=none

            '-PrimaryServerProxyURL'        primary proxy URL

            '-PrimaryServerProxyPort'       primary proxy port

            '-PrimaryServerProxyUserName'   primary proxy user name

            '-PrimaryServerProxyPassword'   primary proxy password

            '-SecondaryServerProxy'         secondary proxy type 0=system, 1=user defined, 2=none

            '-SecondaryServerProxyURL'      secondary proxy URL

            '-SecondaryServerProxyPort'     secondary proxy port

            '-SecondaryServerProxyUserName' secondary proxy user name

            '-SecondaryServerProxyPassword' secondary proxy password

    The updates for KBAs are in the pipeline.

    Note that there is a problem with the CreateUpdatePreconfig tool when specifying PrimaryServerProxy or SecondaryServerProxy keys (these keys were added in this release for that tool) and I don't recommend using them yet. Other options are fine. If you really, really need those keys there is a workaround that requires editing the pre-configuration plist file (change the type from string to integer).

    Hope that preliminary information is enough until the KBAs are ready.

    :54189
Reply
  • Hi Tim,

    If you run the tools without any arguments you get an informational listing with supported options. Here is what I got:

    CreateOnAccessPreconfig [-option {value} ...]

        the following options can be specified:

            '-AutoLaunch'         on-access scanning (YES = on, NO = off)

            '-InArchives'         archive scanning (YES = on, NO = off)

            '-NetworkVolumes'     network volume scanning (YES = on, NO = off)

            '-ExcludedItem'       file or directory path to exclude

            '-EnableDisinfect'    automatic cleanup (YES = on, NO = off)

            '-NonDisinfectAction  action if automatic disinfect fails (N = none, D = delete, M = move)

            '-NonDisinfectFolder  destination directory for moved threats

    CreateUpdatePreconfig [-option {value} ...]

        the following options can be specified:

            '-PrimaryServerUserName'        primary server user name

            '-PrimaryServerPassword'        primary server password

            '-PrimaryServerType'            primary server type : 0=Sophos, 1=Company Webserver, 2=Network Volume

            '-PrimaryServerURL'             primary server location

            '-SecondaryServerUserName'      secondary server user name

            '-SecondaryServerPassword'      secondary server password

            '-SecondaryServerType'          secondary server type : 0=Sophos, 1=Company Webserver, 2=Network Volume

            '-SecondaryServerURL'           secondary server location

            '-PrimaryServerProxy'           primary proxy type 0=system, 1=user defined, 2=none

            '-PrimaryServerProxyURL'        primary proxy URL

            '-PrimaryServerProxyPort'       primary proxy port

            '-PrimaryServerProxyUserName'   primary proxy user name

            '-PrimaryServerProxyPassword'   primary proxy password

            '-SecondaryServerProxy'         secondary proxy type 0=system, 1=user defined, 2=none

            '-SecondaryServerProxyURL'      secondary proxy URL

            '-SecondaryServerProxyPort'     secondary proxy port

            '-SecondaryServerProxyUserName' secondary proxy user name

            '-SecondaryServerProxyPassword' secondary proxy password

    The updates for KBAs are in the pipeline.

    Note that there is a problem with the CreateUpdatePreconfig tool when specifying PrimaryServerProxy or SecondaryServerProxy keys (these keys were added in this release for that tool) and I don't recommend using them yet. Other options are fine. If you really, really need those keys there is a workaround that requires editing the pre-configuration plist file (change the type from string to integer).

    Hope that preliminary information is enough until the KBAs are ready.

    :54189
Children
No Data