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 and Mac OSX AD duplication

 Howdy gents,

I'mn stuck in a bit of a predicament, and wondered if anyone had some sound advice for me.  We recently migrated a lot of machines from a number of seperate consoles on our network to a single unified console (SEC 4.5.0.9).  Some of these older consoles did not support Mac machines, so i have no reference for my issue.  The guy who co-ordinated it all had no clue as far as mac's were concerned, got the windows ones working a charm and has now gone on leave, leaving me to figure out our problem.

We have a number of Mac machines that are bound to our domain.  For example, let's say the AD name is called Mac001.  in the Mac system preferences, in the sharing area, the name is set to reflects the user's name, for ease of use with Apple Remote Desktop , for example the sharing name is "My iMac".  Ok, with me so far?  In SEC, which is synchronised with the AD environment, I can see the AD name of Mac001, which is currently unmanaged.  Remove old version, I install Sophos from CID (7.2.7), and instead of picking up my AD name, it uses the sharing name.  I now have a still unmanaged mac called Mac001 and SEC has created a Mac in the unassigned folder called "My iMac".  Has anybody come across this before?  it's dirving me crazy.  We have a single mac, out of hundreds, that seems to have picked up the AD name properly (eg in AD it's called Mac002, sharing name is "Your iMac" and it only has one account in SEC in the AD container where it should be with a display name of "Your iMac").

I'm tearing my hair out.  Any ideas?  Somebody must have had this problem before.

:13781


This thread was automatically locked due to age.
Parents
  • Ben,

    We were able to figure out a working solution after a few weeks of correspondence, I'll post it here so hopefully it can help you too.  As long as your Macs are running Snow Leopard you should be able do this, it couldn't work with our test group of Lion machines because they no longer use Samba sharing.

    What to do

    Macs use the WORKGROUP value by default.
    It's set in the smb.conf file:-

    /etc/smb.conf

    There is a global workgroup parameter that can be set in here that will be used when reporting the machine back to SEC. By default this is not configured so will always be WORKGROUP. If you add the following entry to the global parameters this will resolve the issue:-

    workgroup = domainname

    where domainname is the name of the domain you want to use

    A restart of RMS will send a new status message with this new workgroup name:-

    cd /Library/LaunchDaemons/
    sudo launchctl unload com.sophos.managementagent.plist com.sophos.messagerouter.plist
    sudo launchctl load com.sophos.messagerouter.plist com.sophos.managementagent.plist

    Try that method on your machines, it has been working for the few Macs that we have in AD.

    Good Luck!

    Tim

    :16543
Reply
  • Ben,

    We were able to figure out a working solution after a few weeks of correspondence, I'll post it here so hopefully it can help you too.  As long as your Macs are running Snow Leopard you should be able do this, it couldn't work with our test group of Lion machines because they no longer use Samba sharing.

    What to do

    Macs use the WORKGROUP value by default.
    It's set in the smb.conf file:-

    /etc/smb.conf

    There is a global workgroup parameter that can be set in here that will be used when reporting the machine back to SEC. By default this is not configured so will always be WORKGROUP. If you add the following entry to the global parameters this will resolve the issue:-

    workgroup = domainname

    where domainname is the name of the domain you want to use

    A restart of RMS will send a new status message with this new workgroup name:-

    cd /Library/LaunchDaemons/
    sudo launchctl unload com.sophos.managementagent.plist com.sophos.messagerouter.plist
    sudo launchctl load com.sophos.messagerouter.plist com.sophos.managementagent.plist

    Try that method on your machines, it has been working for the few Macs that we have in AD.

    Good Luck!

    Tim

    :16543
Children
No Data