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

Duplicate unmanaged machines when AD syncs

mgomez

We're experiencing an issue with some machines, after an AD sync occures there is a dupelicate unmanaged machine created.  Even if I delete the unmanaged machine, next AD sync it shows up again.  I found this article that said the bug was fixed in version 4.7 but we are on version 5.2

http://www.sophos.com/en-us/support/knowledgebase/1462/7800/1471/8850/111697.aspx

This is happening with probably 100 machines.

:45097


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

    Hello mgomez,

    some of which are not only doubled but tripled or quadrupled

    some debris is expected to accumulate over time especially if the database has been upgraded over several versions. Also, reimaged or OS upgraded machines might not be considered a match. ...

    duplicate machines have the same machineID

    Hm, usually the problem is only one entry for distinct machines. Same name, same ID - which attributes differ (though this could be more an academic problem). 

    removed from the domain do we need to somehow remove them from Sophos

    The main reason for keeping computers in the background (i.e. only flagged as deleted) is the preservation of their history.

    How would I go about deleting all of these

    Please have a look at Using PurgeDB with Enterprise Console and related articles and threads.

    Looking at your screenshot - I notice that the entry in the synced group has no domain information. Sync should populate the Domain/Workgroup attribute. I assume it is missing for the duplicates and present for the managed ones. But whether or not, I think there's some issue with the sync logic and I suggest you contact Support. While database-deleting the unmanaged (and undomained) entries might solve your problem this behaviour of sync should IMO be investigated.

    Christian

    :45289
Reply
  • 0

    Hello mgomez,

    some of which are not only doubled but tripled or quadrupled

    some debris is expected to accumulate over time especially if the database has been upgraded over several versions. Also, reimaged or OS upgraded machines might not be considered a match. ...

    duplicate machines have the same machineID

    Hm, usually the problem is only one entry for distinct machines. Same name, same ID - which attributes differ (though this could be more an academic problem). 

    removed from the domain do we need to somehow remove them from Sophos

    The main reason for keeping computers in the background (i.e. only flagged as deleted) is the preservation of their history.

    How would I go about deleting all of these

    Please have a look at Using PurgeDB with Enterprise Console and related articles and threads.

    Looking at your screenshot - I notice that the entry in the synced group has no domain information. Sync should populate the Domain/Workgroup attribute. I assume it is missing for the duplicates and present for the managed ones. But whether or not, I think there's some issue with the sync logic and I suggest you contact Support. While database-deleting the unmanaged (and undomained) entries might solve your problem this behaviour of sync should IMO be investigated.

    Christian

    :45289
Children
No Data