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

Assigning Mac endpoint running 9.0.5 to defined management group

bruienne

Following this KB: http://www.sophos.com/en-us/support/knowledgebase/119791.aspx I am not able to successfully have a newly added endpoint automatically be added to the desired group. Has anyone tried this yet and/or have any luck making it work? Our setup is pretty basic with a top level group being the desired target. Not sure if having a dash in the name has any negative effect but I'm targeting "\[SERVERNAME]\Test-Clients". No endpoints show up in that group automatically when installing using a modified 9.0.5 MPKG, as directed by aforementioned KB.

Attached is the grouppath.plist file, I sanitized the actual server name. Had to add .txt for the attachment to be accepted.

Thanks,

Pepijn.

:45995


This thread was automatically locked due to age.
  • 0

    Hello Pepijn,

    I have not yet done it but I assume it will work. Now it might be a typo but in your post you give the path as \[SERVERNAME]\Test-Clients whereas the screenshot shows <string>\[MYSERVER]\Test-Client</string>. Using the plural for the group name would be logical, so ...

    Christian   

    :45999
  • 0

    You're right, that was a typo on my part, the name in the plist is the name of the group on the SEC side. It just doesn't seem to be taking effect once the client install completes. I tried both logging out and rebooting after installation but the preferences I expect to be set based on the group policy are not changed. The endpoint is also not added to the group. I'm digging through client-side logs to see if there's any mention of the Group Path setting being picked up and applied/sent to the SEC.

    :46011
  • 0

    Having just upgraded SEC to 5.2.1 it seems like it needed one more reboot to come to its senses. Technical term, I know.

    This is now working as expected and I can see the client sending a request to the SEC management server for the group path that is configured in the plist. After about 15-20 seconds (on average) the client is placed in the group and its attached policies are soon after picked up by the client. One note about the auto update policy is that even though the settings came through correctly I had to reboot the client to have it actually use the settings instead of having the "Autoupdate settings not configured" message in the menu bar item and greying out the "Update Now" option. My work is done here.

    :46019