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

    bobcook wrote:

    jelockwood wrote:

    After automatically installing SAV 9.2.2 as part of my DeployStudio / Munki build process I am finding that when I first login to a freshly minted Yosemite Mac I get a dialog box appearing from Keychain Migrator asking for the password for the Sophos keychain. I of course have no idea what that password would be as it is used and created by Sophos. I therefore have to click cancel and then the login proceeds and completes normally. Sophos seems to run ok after this and the message does not seem to reoccur on subsequent logins.

    Anyone else seeing this?

    I'm keen to hear more about this, its weird and unexpected. Definitely never seen it myself nor have we had it happen in our testing, but I can't say we would necessarily have the same endpoint configuration as you'd be running. Anything non-standard in your deployments that we should be trying?

    I may have a bit more information on this. As previously mentioned I am installing Sophos from an automated system when not logged in as a user. When I log in afterwards - for the first time then the above message appears.

    It now appears that the trigger for this is logging in for a user for the first time even if the user account already exists. Normally if you are logging in for the first time then the users home directory does not yet exist along with the users Library folder, Preferences folder and login.keychain

    I think it is the absense of these at the login stage that causes the Sophos message. Now while these files will be unavoidably missing at this first login stage I still do not see why this should upset Sophos because supposedly Sophos uses its own keychain file in the /Library/Keychains folder rather than the users own personal keychain file.

    I have now see this happen with two types of user account - a local admin account created before installing Sophos but never logged in to until after Sophos is installed and hence at that point has not created a home directory, and secondly a network login account with a 'portable home directory' which when first logged in to will create a local home directory for that network login account. This second account was not an admin level user. In both cases the commonality is the absense of a home directory at the time of the first login and this then causes the message to appear. Subsequent logins with the same accounts do not cause the message to reoccur because by then the home directory exists.

    It would appear Sophos is trying to access or create something in the users home directory before the home directory has finished being created.

    A possible simple way to test would be to login as a local admin user, create a second user account, make sure the home directory for the second account does not yet exist and if it does delete it, then try logging in to the second user account which should then at that point have no existing home directory.

    :54603
Reply
  • 0

    bobcook wrote:

    jelockwood wrote:

    After automatically installing SAV 9.2.2 as part of my DeployStudio / Munki build process I am finding that when I first login to a freshly minted Yosemite Mac I get a dialog box appearing from Keychain Migrator asking for the password for the Sophos keychain. I of course have no idea what that password would be as it is used and created by Sophos. I therefore have to click cancel and then the login proceeds and completes normally. Sophos seems to run ok after this and the message does not seem to reoccur on subsequent logins.

    Anyone else seeing this?

    I'm keen to hear more about this, its weird and unexpected. Definitely never seen it myself nor have we had it happen in our testing, but I can't say we would necessarily have the same endpoint configuration as you'd be running. Anything non-standard in your deployments that we should be trying?

    I may have a bit more information on this. As previously mentioned I am installing Sophos from an automated system when not logged in as a user. When I log in afterwards - for the first time then the above message appears.

    It now appears that the trigger for this is logging in for a user for the first time even if the user account already exists. Normally if you are logging in for the first time then the users home directory does not yet exist along with the users Library folder, Preferences folder and login.keychain

    I think it is the absense of these at the login stage that causes the Sophos message. Now while these files will be unavoidably missing at this first login stage I still do not see why this should upset Sophos because supposedly Sophos uses its own keychain file in the /Library/Keychains folder rather than the users own personal keychain file.

    I have now see this happen with two types of user account - a local admin account created before installing Sophos but never logged in to until after Sophos is installed and hence at that point has not created a home directory, and secondly a network login account with a 'portable home directory' which when first logged in to will create a local home directory for that network login account. This second account was not an admin level user. In both cases the commonality is the absense of a home directory at the time of the first login and this then causes the message to appear. Subsequent logins with the same accounts do not cause the message to reoccur because by then the home directory exists.

    It would appear Sophos is trying to access or create something in the users home directory before the home directory has finished being created.

    A possible simple way to test would be to login as a local admin user, create a second user account, make sure the home directory for the second account does not yet exist and if it does delete it, then try logging in to the second user account which should then at that point have no existing home directory.

    :54603
Children
No Data