Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 10291 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

Computer ending up in "Unassigned" group but is in a correct OU?

Dajull

Hi!

Im having problem with a computer that keeps beeing placed in the "Unassigned" group. It's in the correct OU.

I've tryed to delete it from Sophos Enterprise Console and syncing with AD but no diffrence. 

I am running version: 4.7.0

Best regards!

Daniel

:22887


This thread was automatically locked due to age.
Parents
  • 0

    Hello Daniel,

    What determines if a computer goes in the unassigned group?

    Perhaps it is easier to answer when is a computer ("automatically") put into a specific group?: If setup.exe is run with the -G switch specifying a group the computer requests to be put into this group upon connecting (i.e. when the RMS logs on) - and if the group exists it is put there. Also Import from AD and synchronization put the computer in the corresponding group upon detection. Otherwise (either when Discover is used or a previously unknown computer connects without requesting a (valid) group) the computer goes to Unassigned.

    When a computer connects SEC tries to determine if the computer is already known (I'll spare you the details) and if SEC (thinks it) has found a match that is deleted (note that here this means it exists in the database with the deleted flag but is invisible in the console) it undeletes it. As the ComputerGroupMapping is not changed the computer then "re-appears" in its former group.

    This does not necessarily help you with your problem. I think that 4.7 corrected (most of) the problems which previously existed with AD sync. Please check if the problem computer has the expected attributes (name, OS and domain) and also whether SAV is reported as being installed or not when it appears in Unassigned. Make sure that it's the only one in the database with this name (perhaps save the output of the query) - after that delete it (Sophos is already installed I assume). Please tell us what happens then.  

    Christian

    :22957
Reply
  • 0

    Hello Daniel,

    What determines if a computer goes in the unassigned group?

    Perhaps it is easier to answer when is a computer ("automatically") put into a specific group?: If setup.exe is run with the -G switch specifying a group the computer requests to be put into this group upon connecting (i.e. when the RMS logs on) - and if the group exists it is put there. Also Import from AD and synchronization put the computer in the corresponding group upon detection. Otherwise (either when Discover is used or a previously unknown computer connects without requesting a (valid) group) the computer goes to Unassigned.

    When a computer connects SEC tries to determine if the computer is already known (I'll spare you the details) and if SEC (thinks it) has found a match that is deleted (note that here this means it exists in the database with the deleted flag but is invisible in the console) it undeletes it. As the ComputerGroupMapping is not changed the computer then "re-appears" in its former group.

    This does not necessarily help you with your problem. I think that 4.7 corrected (most of) the problems which previously existed with AD sync. Please check if the problem computer has the expected attributes (name, OS and domain) and also whether SAV is reported as being installed or not when it appears in Unassigned. Make sure that it's the only one in the database with this name (perhaps save the output of the query) - after that delete it (Sophos is already installed I assume). Please tell us what happens then.  

    Christian

    :22957
Children
No Data