Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 4 subscribers
  • Views 20458 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 computers in enterprise console

SteveG

Hi

I have noticed a strange behavior in enterprise console when searching for computers it sometimes creates a duplicate computer entry that already exists in the console when importing from AD.

Seems strange this is happening as I would think that the computer names should be unique since the console seems to use them to identify machines and duplicates should not be allowable.

is there a fix for this behaviour?

:7219


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

    Some of the entries do appear to have been ones that were deleted in the past

    Not going into details here - I'd remove the deleted computers from the database and try again to see whether it makes a difference.  

    sqlcmd -E -S .\SOPHOS -d SOPHOS45 -Q "DELETE FROM ComputersAndDeletedComputers WHERE deleted=1"

    (note: .\SOPHOS is the database instance).

    BTW: is this 4.5.0 or 4.5.1? 

    Christian

    :7237
  • 0 in reply to QC
    Does this command also work for the enterprise console 5.2.2? I know the database name is different. I also have duplicated names in the console.
  • 0 in reply to ICTPhotonis

    Hello ICTPhotonis,

    database name has changed, correct, design and logic are for all practical purposes the same. Did you read that manipulating the database directly is unsupported (though over the years I have not yet managed to kill mine this way).

    Christian

  • 0 in reply to ICTPhotonis
    What is the OS of the duplicated computers? I've seen an issue before where the Mac was sending in different workgroup/domain names throwing off the folding logic.

    Name, Domain/Workgroup name and the RMS MessageSystem address are the 3 values that make up the logic. For example, to prevent a new machine being created each time a status message or event comes in, the management service needs to try and map the message details with an existing computer record (computerid) in the database. Looking at the stored procedures, the RMS message system address is checked first as that should be unique to the computer. So it should be able to lookup the the computer id from the message system address, e.g. Router$computer1:5555. If no match it made, the domain name and computer name are taken in combination as in theory in a domain, all computers in the same domain should have a unique name. Lastly the name in isolation is used. In each case a computerid is trying to be looked up. If no results are found then a new computer record is created.
Reply
  • 0 in reply to ICTPhotonis
    What is the OS of the duplicated computers? I've seen an issue before where the Mac was sending in different workgroup/domain names throwing off the folding logic.

    Name, Domain/Workgroup name and the RMS MessageSystem address are the 3 values that make up the logic. For example, to prevent a new machine being created each time a status message or event comes in, the management service needs to try and map the message details with an existing computer record (computerid) in the database. Looking at the stored procedures, the RMS message system address is checked first as that should be unique to the computer. So it should be able to lookup the the computer id from the message system address, e.g. Router$computer1:5555. If no match it made, the domain name and computer name are taken in combination as in theory in a domain, all computers in the same domain should have a unique name. Lastly the name in isolation is used. In each case a computerid is trying to be looked up. If no results are found then a new computer record is created.
Children
No Data
Unfiltered HTML